Phusion Passenger Discussions Google Group

Re: [phusion-passenger] Re: Multiple applications each bundle their own version of Rack

2010-01-08T00:16:58Z

On Thu, Jan 7, 2010 at 10:41 PM, Mislav Marohnić
I will take note of this. Seems like something we will want to tackle
some time in the future.

Re: [phusion-passenger] Re: Multiple applications each bundle their own version of Rack

2010-01-07T21:41:16Z

But as I said, this can be only be accomplished per-server, not per-app,
making it a severly limited solution.

Re: [phusion-passenger] Re: Multiple applications each bundle their own version of Rack

2010-01-07T21:35:48Z

I'm thinking about depending on bundler, or maybe taking over its DSL
implementation. Don't need more than that.

Re: [phusion-passenger] Re: Multiple applications each bundle their own version of Rack

2010-01-07T21:34:31Z

SetEnv environment data is passed to Phusion Passenger during a
request. But the Ruby spawn server is started during Apache startup,
before the first request comes in, therefore there's no good way to
pass SetEnv data like that.
At this time it's already possible by writing a Ruby wrapper script.

Re: Multiple applications each bundle their own version of Rack

2010-01-07T20:15:50Z

Another question: any idea why my "SetEnv RUBYOPT" hack didn't work?
It's great that you intend to support Bundler out-of-the-box, but I'd
still like the feature with which I can set a script to load
immediately after the ruby interpreter has started. This is to support
other LOAD_PATH tools alternative to Bundler.

Re: Multiple applications each bundle their own version of Rack

2010-01-07T20:13:34Z

Then you need to vendor Bundler? Or you will eval Gemfile in a scope
where only `bundle_path` is defined (to capture the path)?
People are using "vendor/bundler_gems" for Rails 2 because "vendor/
gems" is a special path where Rails 2 initializer expected to find
unpacked gems in. If Bundler writes to "vendor/gems", Rails 2 apps

Re: [phusion-passenger] Re: Multiple applications each bundle their own version of Rack

2010-01-07T19:17:30Z

It looks like the bundler will become the de facto standard bundling
tool. I'm thinking about full integration: parse the Gemfile and
figure out where the bundle location is, and load the gems from there
before booting the app. Let's keep things DRY.
vendor/bundler_gems was the old location. The latest bundler README

Re: Multiple applications each bundle their own version of Rack

2010-01-07T18:40:10Z

It might be a good idea, but you have to keep in mind that Bundler
users can change that location to something else. Popular location for
Rails 2 apps is "vendor/bundler_gems/environme nt", for instance. Then
again, it might be something completely else, so Passenger has to
expose some directive for configuring it -- a directive which says

Re: [phusion-passenger] Re: Multiple applications each bundle their own version of Rack

2010-01-07T16:27:22Z

Oops, looks like I made a mistake; the Rails loader doesn't work with
Rails 3 after all. We'll release a fix soon.

Re: [phusion-passenger] Re: Multiple applications each bundle their own version of Rack

2010-01-07T16:18:54Z

Yes it does. All the Ruby Enterprise Edition memory saving and reduced
spawn time optimizations are only possible with the Rails loader. The
exact mechanisms are described in various documents:
[link]
[link]

Re: Multiple applications each bundle their own version of Rack

2010-01-07T15:43:13Z

With. The Rails 3 app generator makes one; I didn't think of removing
it.
Does Passenger do some optimizations when detecting Rails apps as
opposed to Rack apps? If not, I'd rather keep using Rack loader for
Rails 3 apps so that eventually all Ruby webapps that I might run are
spawned the same way. It feels right. And as for the issue we're

memory limitation

2010-01-07T09:38:25Z

Hi guys.
I have a question to Passenger developers: do you plan to implement
memory limitation for nginx module?

MySQL access denied for every first request...

2010-01-07T14:53:18Z

I've just installed passenger on a Debian Lenny system. It seems to
work well, except for the first request for an instance. For the
first request, I always get a "Access denied for user" error for the
database connection. If I refresh the screen, the request goes
through without a problem.
If I force another instance to start, the same thing happens - only

Re: [phusion-passenger] Multiple applications each bundle their own version of Rack

2010-01-07T14:07:27Z

It looks like Phusion Passenger's Rails loader is compatible with Rails 3.

Re: [phusion-passenger] Domain owner and group permissions

2010-01-07T09:16:04Z

2010/1/6 Asif Shams <aasif_sh...@hotmail.com>
You should create a group called "webapps" (or anything else you fancy) and
a user called "<domain-name>". Add this "user" to the webapps group and run
Passenger as this user. You should also look into how users and permissions
work on a Unix based system and that would kind of help you.