Rails console vs server differences on production server

Question

Having deployed a very basic Rails 3.2.3 trial site to a "production" server (not really in production, thankfully!) with RVM Ruby 1.9.3-p194, I find the following to be true, of the commands listed here: ``` ╔══════════════════════════════════════╤═══╗ ║ command issued │OK?║ ╟──────────────────────────────────────┼───╢ ║ bundle exec rails console │ N ║ ║ bundle exec rails console production │ Y ║ ║ bundle exec rails server │ Y ║ ║ bundle exec rails server production │ N ║ ╚══════════════════════════════════════╧═══╝ ``` My first question: is this expected? (I would have thought the pattern in the right column should be N-Y-N-Y.) More info: `bundle exec rails console` fails for the understandable reason that the sqlite3 gem is not installed on the server. However, `bundle exec rails server production` fails with a much less understandable trace: ``` $ bundle exec rails server production Exiting /home/spkspike/www/spike.sampablokuper.com/releases/20120530134819/vendor/ruby/1.9.1/gems/r…

Accepted Answer

Don't you want to be starting the server in production mode using the production environment?

```
rails server -e production
```

The syntax difference between rails console environment and rails server -e environment is a bit of a PITA

Rails console vs server differences on production server

Solution

Problem