Add automated deployment with backups and rollback #33
Conversation
This file contains hidden or 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
Pull Request Test Coverage Report for Build 18950451090Details
💛 - Coveralls |
jnation3406
reviewed
Oct 23, 2025
Collaborator
jnation3406
left a comment
jnation3406
left a comment
There was a problem hiding this comment.
This looks basically the same as the frontend PR I reviewed, so all the same comments I made on that one apply to this one as well.
- Use heredoc for SSH key and env file creation (more secure) - Change production trigger from branch push to tag push - Add version tracking with .deployed_version file - Update backup/rollback to include version information Addresses feedback from PR review.
Collaborator
Author
Thanks for the heads up I've updated the workflow to:
Still working on the docker improvement |
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.
Added the secrets and variables to GitHub and created the
.ymlfile to achieve automatic deployment. I added backup creation and rollbacks in case of deploy-failure. It also considers the correct backend deploy order given that frontend and backend share the same docker-compose network.