config/application.yml does not exist when creating app with Rails Composer

[thom801]

https://github.com/thom801/rails-stripe-membership-saas/edit/master/README.textile#configuration-file

The configuration file at config/application.yml does not exist. The readme makes it sound like it should exist already. Should it exist by default or do I need to create it?

[DanielKehoe]

Is there a file application.example.yml? If not, you can copy the file from: https://github.com/RailsApps/rails-stripe-membership-saas/blob/master/config/application.yml

I'll investigate why the file is not created by Rails Composer. Thanks for bringing the issue to my attention.

[ghost]

Same issue happened with me today also. I ran composer twice and each time it did not create the application.yml file. I guess its ok to just copy there? Would anything else be missing from the gem? And .gitignore does not list the file there either.

[thom801]

Thanks for looking into it @DanielKehoe. I will take a look around and see if I notice anything suspicious.

[ghost]

I ran composer yesterday for the "Twitter Bootstrap, Devise, CanCan" app and it worked there. But not today twice when I ran the Stripe Membership Saas app.

On Feb 15, 2013, at 2:50 PM, Thom Allen notifications@github.com wrote:

Thanks for looking into it @DanielKehoe. I will take a look around and see if I notice anything suspicious.

— Reply to this email directly or view it on GitHub.

[tmock12]

application.yml file should not be created by the composer. Only the application.example.yml. You should then use the example to create your own application.yml (basically just fill in the keys)

[DanielKehoe]

Rails Composer copies the file from this repo but I hadn't checked the file into the repo. My oversight. I've added the file. It's just there for convenience since the application.example.yml file is also there.

[ghost]

I've run the Composer selection #2 of "membership/subscription/saas" three times now. It still does not create the application.yml file. Not only that but it is not creating any Controllers/views or any models.

[DanielKehoe]

Just to make sure, I ran

rails new rails-stripe-membership-saas -m https://raw.github.com/RailsApps/rails-composer/master/composer.rb -T

just now and it generated a working application with an application.yml file.

Anything I can do to help you diagnose the issue further?

[ghost]

Hmmm, what should I look for? Everything installs fine but files just aren't there. What would prevent that?

Mark

Sent from my iPhone

On Feb 16, 2013, at 5:53 PM, Daniel Kehoe notifications@github.com wrote:

Just to make sure, I ran

rails new rails-stripe-membership-saas -m https://raw.github.com/RailsApps/rails-composer/master/composer.rb -T just now and it generated a working application with an application.yml file.

Anything I can do do to help you diagnose the issue further?

— Reply to this email directly or view it on GitHub.

[DanielKehoe]

Let's see a copy of the output from the console when you run

rails new rails-stripe-membership-saas -m https://raw.github.com/RailsApps/rails-composer/master/composer.rb -T

[thom801]

I just ran it and application.yml is there now. My output is in gist since its really long: https://gist.github.com/thom801/86600efd42a172afe097

[ghost]

It's here https://gist.github.com/101South/05216081ddb73527e651

I changed the name of the new app to "lost-members"

On Feb 16, 2013, at 6:18 PM, Daniel Kehoe notifications@github.com wrote:

Let's see a copy of the output from the console when you run

rails new rails-stripe-membership-saas -m https://raw.github.com/RailsApps/rails-composer/master/composer.rb -T — Reply to this email directly or view it on GitHub.

[DanielKehoe]

Try:

gem uninstall multi_json -v 1.5.0
gem install  multi_json

And run it again.

See the article for troubleshooting details: http://railsapps.github.com/rails-error-you-have-already-activated.html

To avoid this issue entirely, I recommend creating a new rvm gemset, then gem install rails, then run Rails Composer to build the app.

[ghost]

Wow, can't believe I missed that in there. Yes that did it. Big difference. Thanks Daniel. Can't wait to start working on this!!

On Feb 16, 2013, at 7:39 PM, Daniel Kehoe notifications@github.com wrote:

Try:

gem uninstall multi_json -v 1.5.0 gem install multi_json And run it again.

See the article for troubleshooting details: http://railsapps.github.com/rails-error-you-have-already-activated.html

To avoid this issue entirely, I recommend creating a new rvm gemset, then gem install rails, then run Rails Composer to build the app.

— Reply to this email directly or view it on GitHub.

[DanielKehoe]

Glad you got it working. Let me know if other issues arise.