Thanks to all who responded.
On May 20, 2007, at 8:11 AM, jordi.f wrote:
> Any reason for not using Django's built-in fastcgi server?
I did try that. In the end, I built up another server based on Centos
and used mod-python. I plan to revisit the fastcgi approach when I
have more time to r
Any reason for not using Django's built-in fastcgi server?
$ ./manage.py runfcgi host=127.0.0.1 port=3033
It's explained in the docs, http://www.djangoproject.com/documentation/fastcgi/
--~--~-~--~~~---~--~~
You received this message because you are subscribed
check out http://www.bluehostforum.com/showthread.php?t=715 it may
have useful information. Note that they don't put it in cgi-bin at
all :)
On May 12, 11:02 am, Mark Phillips <[EMAIL PROTECTED]> wrote:
> I hope I can provide enough information to allow someone to point me
> in the right directi
I hope I can provide enough information to allow someone to point me
in the right direction.
When I start apache 1.3, the error log contains these message:
[error] (22)Invalid argument: FastCGI: access for server (uid 70,
gid 70) failed: write not allowed
[notice] FastCGI: pro
4 matches
Mail list logo
