deploy.sh allow non root with sudo to execute and zero down time on update.sh (kinda) #5
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
thanks for the tutorial lee! on previous commit, this script shows how to deploy using root user, but for some cases we want to disable root login and give another user sudo privileges to do deployment, i logged in with custom user and with previous command it will throw error like 'permission denied', this update works on my deployment. *sorrybadenglish:v
MalikAbdCom
changed the title
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.
thanks for the tutorial lee!
on previous commit, this script shows how to deploy using root user, but for some cases we want to disable root login and give another user sudo privileges to do deployment, i logged in with custom user and with previous command it will throw error like 'permission denied', this update works on my deployment.
also when updating, update.sh take the docker image down first then building the new one, which there will be no running website during building new image, updated update.sh will have zero down time deploymen (kinda) and if new container is fail, it will exit without taking the old image down *sorrybadenglish:v