Modified Ruby Version in Step 9, and added Step 10 to remove 'pry-byebug' gem which depends on Ruby 2.0#296
Merged
Conversation
…bug' gem which depends on Ruby 2.0
Collaborator
|
A note would be good - as well as a link to a bug/forum thread of something about 2.0 support. |
Contributor
Author
|
ok i think i will rephrase and include the background and links.. |
Collaborator
|
Give me the word when it's ready to merge. |
Contributor
Author
|
Yup, I added the link to the bug and issue #294. Should be good for now. thanks! |
swanson
pushed a commit
that referenced
this pull request
Jan 7, 2014
Modified Ruby Version in Step 9, and added Step 10 to remove 'pry-byebug' gem which depends on Ruby 2.0
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Referencing #294.
Updated the Ruby version in Step 9.
Added Step 10 to remove the 'pry-byebug' gem which depends on Ruby 2.0. Opted for this as it seems the most straight-forward and easiest change. Maybe I should add a note indicating that this is only for OpenShift production deployment, or is this fine?