Here is a more detailed answer on how to run webpy projects via SCGI, I think it
should go into the "install"-section of the website. Apache-Site-Configuration
example:
<VirtualHost *:80>
[...]
SCGIMount / 127.0.0.1:9000
<Location '/static'>
SCGIHandler Off
</Location>
Alias /static /path/to/static
[...]
</VirtualHost>
It is important to turn off the SCGI handler in the static directory, or weird
things will happen.
One can meaningfully run webpy through SCGI via GNU screen or detach, I used the
quite simple detach in this example:
$ cd /path/to/project
$ dtach -n project.sock ./code.py 127.0.0.1:9000 scgi
Does anybody have experience with SCGI vs other modes of running webpy on
Apache? I am happily using it for some time now. It seems so simple that I think
there must be some caveat :) For example, is it unhealthy that the webpy process
is not regularly restarted?
Best greetings,
Dragan
Am 13.12.2011 22:50, schrieb andrei:
> You should configure apache to serve static files like this:
>
> Alias /static/ /path/to/static
>
>
> On Dec 13, 6:27 pm, Dragan Espenschied <[email protected]> wrote:
>> Hi Webpyers,
>>
>> I recently tried out the SCGI mode of webpy as described
>> here:http://webpy.org/install#apachescgi
>> It worked very well, apart from the fact that the directory "static" was not
>> served. Any other virtual URL from my script was happily taken care of, only
>> anything in static was "not found".
>>
>> This is probably a bug?
>>
>> Best greetings,
>> Dragan
>
--
http://noobz.cc/
http://digitalfolklore.org/
http://contemporary-home-computing.org/1tb/
--
You received this message because you are subscribed to the Google Groups
"web.py" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/webpy?hl=en.
