On Mar 15, 2010, at 8:54 AM, mdipierro wrote:
> site5 say they support fcgi, so you should be able to use web2py/
> fcgihandler.py
The 'killed' message is ominous, though. Perhaps the use of fcgi and a
long-running web2py process requires a different account level.
I speak from experience. web2py works fine with mod_proxy on my pair.com
account, except that once it accumulates a few minutes of CPU time, it gets
automatically killed. PITA.
>
> Something like this:
>
> export PYTHONPATH=$PYTHONPATH:/path/to/web2py/
> cat << EOF > ~/public_html/.htaccess
> RewriteEngine On
> RewriteBase /
> RewriteCond %{REQUEST_URI} !(fcgihandler.py)
> RewriteRule ^(.*)$ fcgihandler.py/$1 [L]
> EOF
>
> You may need some tweaking of the above configuration files
>
> Massimo
>
> On Mar 15, 10:31 am, Jonathan Lundell <[email protected]> wrote:
>> On Mar 15, 2010, at 5:14 AM, solom wrote:
>>
>>> then in less than 2 or 3 minutes putty says:
>>> killed.
>>> Does that mean the severs closes after only 2 or 3 min.?
>>
>> This suggests that your hosting company imposes a limit on how long a
>> program can run. The only way you can run web2py in such an environment is
>> via CGI, which is very, very slow.
>>
>> If it were not for that limitation, you could probably configure mod_proxy
>> to access web2py at the standard address. But it doesn't sound like that's
>> an option for you. Ask your ISP.
>
> --
> You received this message because you are subscribed to the Google Groups
> "web2py-users" 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/web2py?hl=en.
>
--
You received this message because you are subscribed to the Google Groups
"web2py-users" 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/web2py?hl=en.
