Closed royzinn closed 10 years ago
Thank you for pointing out this issue. I need to add exception handling to Rails Composer so no one can build an app using Rails 4.0, as it is not supported.
You will have no problem following the tutorial if you use Rails 4.1. In fact the tutorial clearly indicates Rails 4.1 is required. In you are using RVM, simply create a gemset containing Rails 4.1.
Hi Again, Thanks for the quick reply and just a minor clarification: you wrote that "...so no one can build an app using Rails 4.0...". It seems like it's done automatically by the composer (setting the rails version) or is it relying on the current rails version installed and then creates the app with that version? (if i'm not clear, i'm asking whether I can "control" the composer to generate this app with Rails 4.1)
Thanks again, Roy
Rails Composer uses the version of Rails that's available in your current environment. Rails Composer cannot set or change the Rails version. You get what you start with.
Today I've updated Rails Composer so it will raise an error if you start with anything other than Rails 4.1.
Rails 4.1 is the current Rails version. Rails Composer is used to build starter apps; there's no reason (as far as I can see) to use it to start an application for an outdated version of Rails.
As I suspected :-), will update the current installed Rails and rerun, Great, Thanks
Hi, When using the Rails Composer option, it creates a rails 4.0.2 app without the config/secrets.yml file which makes some of the generators to fail. There's a mismatch between cloning and using the composer and hence it's a bit confusing as the tutorial doesn't describe the flow when cloning (it lacks many of the composer options...)
Thanks, Roy