I'm trying to run the rails (4.1.2) console
rails c RAILS_ENV=test And I'm getting this:
> config.eager_load is set to nil. Please update your > config/environments/*.rb files accordingly: > > * development - set it to false * test - set it to false (unless > you use a tool that preloads your test environment) * production - > set it to true > > /Users/xxxxxx/.rvm/gems/ruby-2.2.2/gems/activerecord-4.1.12/lib/active_record/connection_adapters/connection_specification.rb:257:in > `resolve_symbol_connection': 'RAILS_ENV=test' database is not > configured. Available: ["development", "test", "production"] > (ActiveRecord::AdapterNotSpecified) Yet in my test.rb I have config.eager_load = false and my database.yml is ok (I ran rake db:schema:load RAILS_ENV=test without issues.
How can I solve this?
You need to declare the env before you run the commands:
RAILS_ENV=test bundle exec rails c I get the same output on my computer:
> bundle exec rails c RAILS_ENV=test ian@Ians-MacBook-Pro config.eager_load is set to nil. Please update your config/environments/*.rb files accordingly: * development - set it to false * test - set it to false (unless you use a tool that preloads your test environment) * production - set it to true but when I run as suggested:
> RAILS_ENV=test bundle exec rails c ian@Ians-MacBook-Pro Loading test environment (Rails 4.2.3)
Needs to set
config.eager_load = false for config/environments/development.rb and test.rb or = true for production.rb (as default)
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With