-
Notifications
You must be signed in to change notification settings - Fork 340
rails console uses spring in deployment mode #605
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
Comments
Any update on this issue, I am having the similar issue with Rails 6.0.3 |
me too |
+1 |
Can you verify if the srping gem is not being installed in production? If it is this seems like a bundler issue, not spring. |
In rails 6.1.3.1 this is still a problem. In my Gemfile, spring and spring-watcher-listen (and listen) are within The first time I fired up I gem uninstalled spring and spring-watcher-listen and attempted started the console in production. Rails console simply would not start because of the missing spring gems which it should not be attempting to load given the environment settings in the Gemfile and my command line launch.
|
Try updating your bin stubs. I think for me my binstub was old or stale. By updating it added a check to make sure that Spring only loaded in development or testing environments which resolved the issue for me. |
Hi
I have rails 6 app deployed using:
bundle install --deployment --without=development test --quiet --path=... --gemfile=.../build/Gemfile
yet, running the rails console:
uses spring, yet spring is defined in the development section of Gemfile, not production.
why is this so?
The text was updated successfully, but these errors were encountered: