zzbbyy at gmail
Mar 27, 2008, 2:31 AM
Post #2 of 2
On Mon, Mar 24, 2008 at 2:08 PM, Marcus Ramberg <marcus [at] nordaaker> wrote:
Re: several instances of an app on a machine.
[In reply to]
> I've been thinking about a feature I want to add to Catalyst-Devel so
> the created skeleton adds a new command to the script/ dir of apps
> Create an instance of Catalyst app installed somewhere in @INC
> Make a directory structure like so:
> data/ - app specific data like a sqlite database or filecache to be
> stored here
> root/ - automagically added to the apps template path, so that
> instances can override individual templates
> script/server.pl - These should pretty much just proxy to the existing
> script/fastcgi.pl so that they won't need to be upgraded.
> It might also be sensible to do a simple change to Catalyst.pm in
> Add a requires_instance() method to Catalyst.pm that will die with a
> about having to run myapp.pl to create a instance of the app if it's
> from the system instance or to set MYAPP_HOME in the case of modperl?
I don't know if it goes in the same direction - but for the sake of
brainstorming - what I would like to see is:
catalyst_server -MMy::App -c /some/dir/my_app.yml
catalyst_fastcgi -MMy::App -c /some/dir/my_app.yml
catalyst_server -c /some/dir/my_app.yml
Because the server can take the module name from the config.
alternatively it could be:
perl -MMy::App --fastcgi -c /some/dir/my_app.yml
If not the use of Find::Bin this would be not so difficult to write
that as an add-on.
> Catalyst-dev mailing list
> Catalyst-dev [at] lists
Catalyst-dev mailing list
Catalyst-dev [at] lists