Plack and mod

morgon has asked for the wisdom of the Perl Monks concerning the following question:

Sorry for abusing this forum as my problem is more of an apache-configuration isse but maybe the answer could be useful to other people as well...

I have a Plack-application that I want to run as fast-cgi under apache using mod_fcgid and I cannot figure out how to do this.

What I want is that all urls starting with "/foo" to be handled by this Plack-app.

The first line of my app looks like this:

#!<full path to plackup> -s FCGI
[download]

And I have added the following to the apache-config file:

<Location "/foo">
     FcgidWrapper "<path to plack-app>" virtual
</Location>
[download]

But it does not work - apache says file "/var/www/foo" does not exist, so evidently I am doing it totally wrong...

Can someone help me here?

Many thanks!

Comment on Plack and mod_fcgid Select or Download Code

Replies are listed 'Best First'.
Re: Plack and mod_fcgid by locked_user sundialsvc4 (Abbot) on Sep 26, 2011 at 12:36 UTC
You are probably missing a `SetHandler` directive. Look at the second example in the Apache documentation for `mod_fcgid` carefully. I am more familiar with `mod_fcgi` but I expect that the situation will be similar... There are really two ways that Apache is designed to operate: (1) for shared-hosting companies; and (2) for dedicated corporate servers. In the first scenario, “anyone out there” could request to run “a CGI program” ... except that we want it to run under fast-CGI. As long as the `SetHandler fcgid-script` directive or the `SetHandler` directive is used appropriately, the Apache module tries to do all the rest. It “runs the file,” just as CGI does, but it (so to speak...) tries to harbor them for a while. Another way to do FastCGI (as I use `mod_fastcgi`) is to establish a static or dynamic server and then to cause the `<Location>` directive to refer to it. This is the second scenario I described. In this case, Apache isn’t looking for “a file to run.” Instead, the server processes are running (under Apache’s auspices or not... on the current machine or not...) and Apache is forwarding selected requests to them. In this scenario, the identity and the number of handlers is well-known to you and stable (whereas, in the first, it could be so-to-speak unpredictable). Throughout all of this, the Plack portion of it all is relatively easy: it’s basically `app.psgi`. I have very-recent experience with a FastCGI deployment and would be happy to help further, if this initial, admittedly-vague response to this thread has been useful for setting the stage ...
Re^2: Plack and mod_fcgid by morgon (Priest) on Sep 26, 2011 at 16:52 UTC
Thanks for your reply. I have also tried: `<Location "/foo"> FcgidWrapper "<path to script-dir>/app.psgi" .psgi virtual AddHandler fcgi-script .psgi </Location>` [download] But that does not change a thing...	[reply] [d/l]