RailsEnv under 3.0.0.pre3

[Lee Henson]

Hi

I'm just trying out Passenger for the first time and I'm having
trouble with RailsEnv. I've got a newly generated rails 3 app
installed on my server (served with apache 2), and I wanted to check
everything was hooked up correctly by using the rails/info/properties
link. Since that doesn't work in the production environment, I've
tried setting "RailsEnv development" in my vhost, but it does not have
any affect. If i rename config.ru to config.ru.tmp, it does then serve
rails/info/properties correctly.

What am I doing wrong? Oh, and it's Ruby 1.9.2 via RVM too. :)

Cheers
Lee

[Hongli Lai]

On Thu, Sep 23, 2010 at 8:14 PM, Lee Henson <lee.m....@gmail.com> wrote:
> Hi
>
> I'm just trying out Passenger for the first time and I'm having
> trouble with RailsEnv. I've got a newly generated rails 3 app
> installed on my server (served with apache 2), and I wanted to check
> everything was hooked up correctly by using the rails/info/properties
> link. Since that doesn't work in the production environment, I've
> tried setting "RailsEnv development" in my vhost, but it does not have
> any affect. If i rename config.ru to config.ru.tmp, it does then serve
> rails/info/properties correctly.

RackEnv, not RailsEnv. Rails 3 apps are recognized as Rack apps.

Think "Rails" in the context of Phusion Passenger as "Rails 2".

--
Phusion | The Computer Science Company

Web: http://www.phusion.nl/
E-mail: in...@phusion.nl
Chamber of commerce no: 08173483 (The Netherlands)

[Lee Henson]

Dammit, just marked myself out as a right noob there didn't I?

Yep, that works great now. :)

Cheers!

On Sep 23, 8:25 pm, Hongli Lai <hon...@phusion.nl> wrote:

> On Thu, Sep 23, 2010 at 8:14 PM, Lee Henson <lee.m.hen...@gmail.com> wrote:
> > Hi
>
> > I'm just trying out Passenger for the first time and I'm having
> > trouble with RailsEnv. I've got a newly generated rails 3 app
> > installed on my server (served with apache 2), and I wanted to check
> > everything was hooked up correctly by using the rails/info/properties
> > link. Since that doesn't work in the production environment, I've
> > tried setting "RailsEnv development" in my vhost, but it does not have
> > any affect. If i rename config.ru to config.ru.tmp, it does then serve
> > rails/info/properties correctly.
>
> RackEnv, not RailsEnv. Rails 3 apps are recognized as Rack apps.
>
> Think "Rails" in the context of Phusion Passenger as "Rails 2".
>
> --
> Phusion | The Computer Science Company
>
> Web:http://www.phusion.nl/

> E-mail: i...@phusion.nl

[cactis]

Thanks, it works!!

On 9月24日, 上午3時25分, Hongli Lai <hon...@phusion.nl> wrote:

> On Thu, Sep 23, 2010 at 8:14 PM, Lee Henson <lee.m.hen...@gmail.com> wrote:
> > Hi
>
> > I'm just trying out Passenger for the first time and I'm having
> > trouble with RailsEnv. I've got a newly generated rails 3 app
> > installed on my server (served with apache 2), and I wanted to check
> > everything was hooked up correctly by using the rails/info/properties
> > link. Since that doesn't work in the production environment, I've
> > tried setting "RailsEnv development" in my vhost, but it does not have
> > any affect. If i rename config.ru to config.ru.tmp, it does then serve
> > rails/info/properties correctly.
>
> RackEnv, not RailsEnv. Rails 3 apps are recognized as Rack apps.
>
> Think "Rails" in the context of Phusion Passenger as "Rails 2".
>
> --
> Phusion | The Computer Science Company
>
> Web:http://www.phusion.nl/

> E-mail: i...@phusion.nl