Setup capistrano for deployments #228
Open
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
The current deployment process doesn't give us many options for rollbacks, and could have issues if the server was restarted during the deployment. Most rails apps that aren't containerised tend to be deployed with Capistrano [1]. Capistrano lets us all the same user, and manage deployment access by giving people access to the deploy user by adding their ssh public key. We should be able to move towards that being a sudo-less enterprise, but qless may make that difficult.
tom93
reviewed
Dec 30, 2023
Comment on lines
+6
to
+7
| # server "train.nzoi.org.nz", user: "cap_deploy", roles: %w[app db web] | ||
| server "faketrain", user: "cap_deploy", roles: %w[app db web] |
There was a problem hiding this comment.
Is this just from debugging?
There was a problem hiding this comment.
yeah, this needs some decisions - we could use a new user, or make some changes to the existing deploy user, and i wanted to make sure that if this got accidentally merged it couldn't do any damage.
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.
The current deployment process doesn't give us many options for
rollbacks, and could have issues if the server was restarted during the
deployment. Most rails apps that aren't containerised tend to be
deployed with Capistrano [1].
Capistrano lets us all the same user, and manage deployment access by
giving people access to the deploy user by adding their ssh public key.
We should be able to move towards that being a sudo-less enterprise, but
qless may make that difficult.