Christopher H. Laco wrote:
> Perrin Harkins wrote:
> 
>> On Tue, 2005-08-16 at 12:07 -0400, Christopher H. Laco wrote:
>>
>>> There are various plugins and httpd.conf changes that can be made to
>>> disuade this behaviour, but I would like to take it a step further
>>> and make it Just Work(TM) so I don't have to tweak the httpd.conf or
>>> the static plugin every time I add a new static directory.
>
>> If you put your catalyst app under a known path (i.e. /something instead
>> of /), you wouldn't have to worry about that.  Or you could just put all
>> static files under /assets/ or similar.
>>
>> - Perrin
>>
> Of course, but that's not always the case.
> I see no reason setup situations should be constrainded like that when
> they don't have to be.

A sample example of what I _think_ you are trying to do would look like:

<httpd.conf>
PerlModule Catalyst
</httpd.conf>

<Catalyst.pm>
package Catalyst;
use Apache2::ServerUtil qw();

[... figure out where/what to configure ...]

Apache2::ServerUtil->server->add_config([
'<Location /foo-bar>',
'  SetHandler perl-script',
'  PerlHandler Catalyst::Foo::Bar',
]);
</Catalyst.pm>

With ->add_config, you can just feed arbitrary chunks of config to httpd, so you
are free to do whatever you need to do.

--------------------------------------------------------------------------------
Philippe M. Chiasson m/gozer\@(apache|cpan|ectoplasm)\.org/ GPG KeyID : 88C3A5A5
http://gozer.ectoplasm.org/     F9BF E0C2 480E 7680 1AE5 3631 CB32 A107 88C3A5A5

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to