feat(l1,l2): ansible rework for deploying ethrex on servers. #5663
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We want a single way to handle Ethrex automated deployments.
This PR aims to close the ansible-dev-deps PR.
Description
This PR adds two Ansible playbooks: one for development and one for standard deploys.
Development deploy
The development playbook is run with
It provisions all required dependencies and leaves the server in a ready-to-use dev state with:
Standard deploy
The deploy playbook is run with
It performs a similar setup but runs Ethrex and Lighthouse as systemd services instead of tmux sessions.
In both playbooks, the Lighthouse version can be changed via the
lighthouse_versionvariable in the YAML files. The deploy playbook also allows changing the Ethrex version throughethrex_versionAny changes or suggestions to make the deployment easier are more than welcome.