Home/ Questions/Q 3323282
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T23:17:01+00:00

Using Rails 3.0.1, Apache 2.2.9, and Passenger 3.0.0 on Debian. For some mysterious reason,

  • 0

Using Rails 3.0.1, Apache 2.2.9, and Passenger 3.0.0 on Debian.

For some mysterious reason, the Rails app is coming up in the development environment. I’ve double-checked the Apache configuration, the VirtualHost files, and so forth, and there are zero instances of “RailsEnv” or “RAILS_ENV” either in /etc/apache2 or in the app directory itself.

Worse, even if I do put a “RailsEnv production” line into the Directory block in the VirtualHost file, it makes absolutely no difference, and the app still comes up in the development environment.

Nothing interesting is logged if I set PassengerLogLevel to 1.

Any help either with what the problem is, or at least a course of action to identify the problem, would be greatly appreciated.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    That’s because with config.ru your app is detected as a Rack app, not a Rails app, and thus you need to set RackEnv instead of RailsEnv. A “Rails” app refers to a “Rails 1 or 2” app. Rails 3 apps are considered to be Rack apps.

    • 0