rails console on production uses spring

[visibletrap]

I have been using spring since rails 4.1 released and I really like it. Yesterday we found that there's spring processes running on our production servers. We traced down and found that spring was started when we used rails console with command bundle exec rails console production. We don't want it to be used on production.

Regards your comment on this at rails/rails#12958 (comment)

It's already handled by the fact that spring is in the development group of the gemfile. So it's not installed on the server. If it's not installed, the binstub just bypasses spring and runs the underlying command.

What we have experienced is different, spring is installed on our production servers even though it's in :development group.

I'm curious, do you expect us to run bundle install with --without development on production servers? We haven't had need for --without development parameter. We have been using only bundle install --deployment so far.

Maybe we should update the documentation for this?

[rafaelfranca]

Yes. It is expected that you run bundle install --without development test on production. Could you submit a pull request to update the documentation?

[visibletrap]

sure. I'll do that

[jonleighton]

Closing this. Please send a PR when you're ready.

[visibletrap]

Sorry for the delay. I have created a PR #337

[jeremy]

This is too error-prone for just a blurb in the docs. Nobody should end up with sprung processes in production when doing a typical bundle install.

Other possibilities include checking for a ~/.spring file or env var to indicate that we're in a dev environment and expect to get sprung.

[jonleighton]

I think we could just make spring throw an error (or perhaps warning) if it's booted into the production env, indicating that it should be in the development gemfile group and therefore not installed on production.

[varchar]

Yes, its too easy to mess up the production env as the this currently works

[amw]

Also, I sometimes run rails c production or rails c staging on my dev machine (which has spring installed) and I would not want these processes to use spring. I would like them to run clean, as in production, reloading config files each time they start.

[squaresurf]

Spring should listen to the gem groups before loading. Requiring bundle install to be run in a non standard fashion is not a fix in my opinion.

I had to add DISABLE_SPRING=1 to my production environment to fix this which feels more like a hack than a fix.