Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Passenger 3.0.0 ignored RailsEnv
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Simone Carletti  
View profile  
 More options Oct 26 2010, 7:51 am
From: Simone Carletti <wep...@gmail.com>
Date: Tue, 26 Oct 2010 04:51:53 -0700 (PDT)
Local: Tues, Oct 26 2010 7:51 am
Subject: Re: Passenger 3.0.0 ignored RailsEnv
Nevermind, I just read this thread.
http://groups.google.com/group/phusion-passenger/browse_thread/thread...

I would suggest to update the documentation.
http://www.modrails.com/documentation/Users%20guide%20Apache.html#rai...
It should state the RailsEnv is now about Rails 2.

-- Simone

On Oct 26, 1:48 pm, Simone Carletti <wep...@gmail.com> wrote:

> I upgraded from Passenger 2.x to Passenger 3.0.0 and now Passenger
> seems to ignore the RailsEnv directive.
> My staging application is now running the production environment.

> Here's the configuration

>     <VirtualHost *:80>

>       ServerAdmin webmaster@...
>       ServerName  staging.....com

>       DocumentRoot /var/.../staging/public

>       ErrorLog  /var/.../error.log
>       CustomLog /var/.../access.log combined

>       RailsEnv staging

>       <Location "/">
>         AuthName "Private Area"
>         AuthType Basic
>         AuthUserFile /var/.../.htpasswd
>         Require valid-user
>       </Location>

>     </VirtualHost>


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.