FastCgiConfig -idle-timeout 90 -restart -minProcesses 5
FastCgiServer /path/to/django.fcgi -processes 5
On 4/21/06, tsnyder <[EMAIL PROTECTED]> wrote:
I am extremely new to all of this, so if my question is stupid I'm sorry. I
couldn't find the answer after
doing some searches. I suspect that is because the answer is obvious, and I
apologize if it is.
If I run django as fastcgi with apache, then, as I understand it, there is a
fastcgi program running
continuously, connected to my django site, and apache just forwards the page
request to the fastcgi
program. It looks like *I* have to manually launch this program. Is that
correct? How do I keep it running
- or relaunch it when it goes down? And does it time out and quit after a
while? In some testing yesterday
on my powerbook, it looked as if the fastcgi program just died a couple of
hours after I started it. I really
don't want to have to start fastcgi programs manually several times a day.
I am looking at using django to create several web applications. These apps
will have a fairly specific
audience, and I don't expect more than a few hundred hits a day (maybe up to
1000 or 1500 a day total
for all apps once all are running). Can apache 1.3 and fastcgi work as a
solution for me?
Thanks!
Tamara
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
