This repository was archived by the owner on Jul 4, 2022. It is now read-only.
Enhancements - #5
Open
ilude wants to merge 8 commits into
Open
Conversation
added 8 commits
January 1, 2016 10:46
Author
|
Oh, one note I forgot to add: its all backward compatible, none of this should break any existing config/gitploy.rb. |
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
I have added a few minor enhancements:
updated spec_helper.rb to avoid depercation warnings from older rspec syntax.
added an echo command to print out messages while deploying
added a -f | --force option to the command line to allow git push --force when deploying
Occasionally the deploy server gets itself out of sync with origin/master, usually because of a team member who does something odd with their git repo. This allows saving the step of logging into the production server to sort it out.
4 added the newrelic_deployment_marker.
Yes its syntactic sugar. But its optional and handy to have the syntax built in.
5.updated the README.markdown documentation
Including an example of how to set RAILS_ENV when doing deployments to staging vs production