CODEWITHSUNDEEP
ruby-on-rails-3capistranopassenger
simonmorley
simonmorley

Reputation: 2804

Rails Reporting Wrong Environment in Multi-stage Setup

Using capistrano 2.12.0, capistrano-ext 1.2.1, Rails 3.2.7 and Phusion Passenger 3.0.15.

For no logical reason, my 'playground' server has started reporting that it's actually running in development mode.

I've reinstalled things, restarted apache etc but am still stuck.

Don't really want to hardcode as I've got a production environment to think about.

In my apache conf. I've set

RailsEnv playground

There's a gist of my deploy.rb file here

Capistrano is sending to the correct location etc. so I think it's rails or passenger rather than cap.

What else can I do to get this going properly??

---- EDIT ----

I've just tested with Unicorn and it's also reporting that it's running in development mode.

Starting unicorn with the following:

 unicorn -E playground -l 8000

Upvotes: 0

Views: 391

Answers (1)

simonmorley
simonmorley

Reputation: 2804

After much experimentation, I found the root cause to be a line in one of my models:

 - if Rails.env = 'development'

Obviously, this should have been a '==' not a single one.

Upvotes: 1

Related Questions