Streamline node deployment

[Mirko-von-Leipzig]

See previous discussion for some history and context. In particular, this issue is derived from this comment:

What to improve

• Faucet webpage should determine server to callback to, currently has localhost hardcoded for fetching metadata and tokens.
• Document requirements of the host server e.g. systemd and its config files, nginx setup and configuration.
• Automate deployment for testnet and devnet. There are a variety of options here:
  • Manual deployment using scripts
  • cron jobs on the host server monitoring releases and automatically updating
  • Using github actions. This is probably the most automatic way, but I haven't used this myself so I'm unsure how complicated this might be. Or whether its worth it.
  • Regardless of what we use though, we will want the option of doing this manually as well for special circumstances. This might actually make github actions attractive as you can manually trigger a workflow from any commit/branch.
• Testnet should be deployed on each new release.
• Devnet should be deployed on each push to the next branch.

Whatever scripts or workflows are used should be extensively documented so that an operator or dev can understand what is going on in an emergency.

[bobbinth]

I think once we have the relatively simple scripts developed, we can ask the DevOps team to help us with the automation.

cc @Dominik1999 and @phklive.

[Dominik1999]

Jup, @BrucePolygon is already on this. I think the infrastructure is now set up. Maybe @Mirko-von-Leipzig can work directly with @BrucePolygon to get it done?

[Mirko-von-Leipzig]

I suspect it might be better if we don't separate the init commands from the github infrastructure file. The commands are minimal and do have some coupling with settings like working directory, binary location of the systemd files.

I suggest we begin by first having it all in the github file. It might be more obvious what we want to move out, if anything.

[bobbinth]

I don't have a strong opinion here - but I am curious if we could improve the init commands somehow so that in case when we are installing from crates.io, we wouldn't need to get anything from the GitHub repo.

[Mirko-von-Leipzig]

I don't have a strong opinion here - but I am curious if we could improve the init commands somehow so that in case when we are installing from crates.io, we wouldn't need to get anything from the GitHub repo.

I'll check that out once the devops issue is figured out. There are also other options if we're pursuing simplicity.