search

phusion / passenger

A fast and robust web server and application server for Ruby, Python and Node.js
https://www.phusionpassenger.com/
MIT License
5.01k stars 548 forks source link

RailsEnv production ignored, RAILS_ENV = 'production' ignored, ENV['RAILS_ENV'] = 'production' ignored #210

Closed FooBarWidget closed 10 years ago

FooBarWidget commented 10 years ago

From gdonald on July 25, 2008 17:00:12

I have a Rails app running under mod_rails that seems to only want to run in development mode. It writes errors to log/development.log and only uses the development: entry from my database.yml. It seems to work ok, just a bit slow, and connected to the wrong database.

I tried adding

RailsEnv production

to my vhost entry and I restarted Apache, but it doesn't change anything. The app is still in development mode.

I tried adding RAILS_ENV = 'production' to my config/environment.rb but it doesn't change anything. If I do <%= RAILS_ENV %> in a view, indeed it says "production", but the app is still running in development mode.

I tried adding ENV['RAILS_ENV'] = 'production' to my config/environment.rb but it doesn't change anything either.

tmp/restart.txt never gets deleted. The app always shows me visible changes without restarting Apache or retouching tmp/restart.txt.

Not sure if it's relevant, but I'm using RailsBaseURI to share a vhost url on this app. I have other mod_rails apps that do not share a vhost URL and do not use RailsBaseURI that do not have this issue.

Original issue: http://code.google.com/p/phusion-passenger/issues/detail?id=109

FooBarWidget commented 10 years ago

From gdonald on July 30, 2008 08:17:45

Also, I will mention, this is the same app associate with this bug: https://code.google.com/p/phusion-passenger/issues/detail?id=110

FooBarWidget commented 10 years ago

From lolindrath on August 11, 2008 12:45:40

I had the same sort of problem.

When I had RailsAllowModRewrite on the base address (i.e. http://localhost/ showed that it was in 'production'. When I visited any any url underneath that (i.e. http://localhost/login' showed that it was in development mode. If I turned off RailsAllowModRewrite it behaved properly.

FooBarWidget commented 10 years ago

From honglilai on August 11, 2008 12:49:26

Do you have multiple virtual hosts that point to the same Rails application document root?

FooBarWidget commented 10 years ago

From gdonald on August 28, 2008 13:39:33

No. In this particular setup, this is one Apache vhost pointing at one Rails app.

Are you testing on a 64-bit machine? That seems to stand out with regards to my many working (32-bit) mod_rails setups.

FooBarWidget commented 10 years ago

From gdonald on February 13, 2009 13:15:38

6 months have passed, any word on 64-bit support?

FooBarWidget commented 10 years ago

From gdonald on February 18, 2009 11:22:01

For me this issue is now resolved.

FooBarWidget commented 10 years ago

From honglilai on February 18, 2009 11:45:15

Status: Fixed

FooBarWidget commented 10 years ago

From mattias.arro on May 21, 2010 12:01:36

gdonald, how did it get resolved? I am having exactly the same problem and would appreciate some guidlines. I even did a fresh install of Apache+Passenger, still no luck.

FooBarWidget commented 10 years ago

From mattias.arro on May 21, 2010 12:13:21

Ah, my problem was config.ru file in RAILS_ROOT. Renamed it to config.ru.bak.

Sorry for double post, but maybe this helps someone.

FooBarWidget commented 10 years ago

From bmishkin on June 06, 2010 10:29:13

Removing / renaming config.ru also fixed this issue for me. Passenger would always start a vhost in production mode even if RailsEnv was set properly.

This only came up when I upgraded from passenger v0.8.10 to 0.8.14.