-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gemfile
: syntax error, unexpected tIDENTIFIER, expecting keyword_end - "https://github.com/
#260
Comments
The "Updating origin Permission denied (publickey)" problem was solved by fixing my SSH key for GitHub. (I don't know how or when that got broken. I thought it was working.) I checked on GitHub and found my Rails app finally got pushed. Rails apps I previously created with Rails Composer initialized empty repositories on GitHub somehow. (I don't know how if the SSH key was broken.) The Gemfile-parsing error is still there. |
Apparently the problem (Gemfile parsing) does not exist for the combination of ruby-2.3.0 and rails-4.2.6. |
I'm still having this problem with the combination of ruby-2.3.3 and rails 5.0.1. I'll try ruby-2.3.0 and rails-4.2.6. and see if I can reproduce the "absence" of the error in that case. |
@pconrad I'll be watching your progress because it seems that when I use ruby-2.3.0 and rails-4.2.6 and choose the "confirmable" option for Devise I run into a problem with the "confirm!" method, which has been deprecated. |
@tomelam Thanks for bringing this to my attention. Rails 5.0.1 broke Rails Composer. Made a small change to the regex that cleans up comments in the Gemfile and it is now fixed with RailsApps/rails_apps_composer@1e247ce. |
@DanielKehoe Thanks for your monumental, faithful work on the example apps, books, and tutorials. |
This happens whether I say y or n to the 'Create a GitHub repository?' option question. When Rails Composer subsequently runs 'bundle install', an error occurs.
The text was updated successfully, but these errors were encountered: