You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it does also generate bin/spring which has some checking logic, so maybe that's the expected behavior and the readme just needs to be updated
if !defined?(Spring)
......
i'm noticing this because i'm running into the problem where
i have spring in development in Gemfile
running something like RAILS_ENV=test rails db:migrate still gives me the Please, set config.cache_classes to false in config/environments/test.rb message
so i'm not sure what is the correct way to not use spring in my local test environment (i think something is happening like, the gem gets installed locally, isn't in the bundle, but the binstub is loading it outside of the logic of bundler?)
The text was updated successfully, but these errors were encountered:
thanks for a great project!
The docs say this command
bundle exec spring binstub --all
should produce this:But that's not what i'm seeing in my rails 6.1 app
it simply produced this in bin/rails and bin/rake
#!/usr/bin/env ruby +load File.expand_path("spring", __dir__)
it does also generate bin/spring which has some checking logic, so maybe that's the expected behavior and the readme just needs to be updated
i'm noticing this because i'm running into the problem where
development
in GemfileRAILS_ENV=test rails db:migrate
still gives me thePlease, set config.cache_classes to false in config/environments/test.rb
messageso i'm not sure what is the correct way to not use spring in my local test environment (i think something is happening like, the gem gets installed locally, isn't in the bundle, but the binstub is loading it outside of the logic of bundler?)
The text was updated successfully, but these errors were encountered: