On Thu, Jul 23, 2009 at 11:31 AM, Will Bryant wrote:
> On Thu, Jul 23, 2009 at 6:42 AM, Matt Jones wrote:
>> I don't think that vendoring Rack will even *work* on Passenger - I
>> haven't tried it, but a casual reading of the FrameworkSpawner code
>> shows that it loads the Rails gem (in preload_r
On Thu, Jul 23, 2009 at 6:42 AM, Matt Jones wrote:
> I don't think that vendoring Rack will even *work* on Passenger - I
> haven't tried it, but a casual reading of the FrameworkSpawner code
> shows that it loads the Rails gem (in preload_rails). With 2.3.3, this
> will blow up unless Rack is inst
On Mon, Jul 20, 2009 at 9:15 AM, kapouer wrote:
>
> Hi,
> i'm packaging redmine for debian, and i thought it would be nice
> to make config paths settable by environment variables, like those :
> config.log_path
> config.cache_store
> config.database_configuration_file
> ActionController::Base.ses
On Jul 22, 2009, at 3:59 AM, Hongli Lai wrote:
> Rails uses a lot of Rack functionality, so I think vendoring it makes
> sense. Phusion Passenger tries very very hard to be compatible with
> everything so it shouldn't be necessary to vendor it. On the other
> hand, I'm not sure whether Rack provi
Hi,
i'm packaging redmine for debian, and i thought it would be nice
to make config paths settable by environment variables, like those :
config.log_path
config.cache_store
config.database_configuration_file
ActionController::Base.session_options[:tmpdir]
instead of having to patch or ask upstrea
On Jul 22, 4:26 am, Matt Jones wrote:
> The situation for Rack is a little weird. Here's what I observed:
>
> - when running Rails from installed gems, the call to load_rails_gem
> will blow up unless Rack is installed. The code to set things up for
> vendor/gems isn't even loaded for this pa
