Jiajia Wang wrote in post #1166961:
> I'm running into a very weird rails server problem.
>
> I started a rails application in production mode with `rails s -e
> produciton` and got some db errors when visiting the site.
>
> Then I realised that it loaded development database not production
> database.
>
> To confirm that, I removed development db config from database.yml.
>
> Then I got
> $ bundle exec rails s -e production
> Digest::Digest is deprecated; use Digest
> => Booting Thin
> => Rails 4.1.6 application starting in production on http://0.0.0.0:3000
> => Run `rails server -h` for more startup options
> => Notice: server is listening on all interfaces (0.0.0.0). Consider
> using 127.0.0.1 (--binding option)
> => Ctrl-C to shutdown server
> Digest::Digest is deprecated; use Digest
> Exiting
>
/home/ubuntu/.rbenv/versions/2.1.4/lib/ruby/gems/2.1.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/connection_specification.rb:257:in
> `resolve_symbol_connection': 'development' database is not configured.
> Available: ["production", "test"] (ActiveRecord::AdapterNotSpecified)
>
> What happened here?
Figured out what the problem was.
Found this line in initializers/session_store.rb
ActiveRecord::SessionStore::Session.establish_connection(:development)
Removing it and changing session store to use :cookie_store solved the
problem.
--
Posted via http://www.ruby-forum.com/.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/ceba453ce7de4622200cf27a5d52549b%40ruby-forum.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment