feat(sidecar): quick deployment script with systemctl #176
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a secondary way for us to deploy the Bolt sidecar on our dev machine, through
the combination of Tailscale SSH and Systemctl.
The deployment for node operators remains unchanged. To deploy to the dev machine, the following is required:
./bolt-sidecar/.env.devfile with the required variables for the dev environmentArmed with these, one can simply use the
just deploy-sidecar-devrecipe to live-reload the service,instead of having to wait 20 minutes for the new docker build to finish.
Furthermore, we can see the logs with
just logs-sidecar-devand stop it withjust stop-sidecar-dev.