Yah, weird. Is there any advantage of using a socket or tcp?
Ivan On Jun 24, 3:22 pm, Nic James Ferrier <[EMAIL PROTECTED]> wrote: > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> writes: > > I've been reading this to get lightTPD and fastcgi configured on my > > machine: > >http://www.djangoproject.com/documentation/fastcgi/ > > > There, it says to add this to your lighttpd.conf: > > ======================================== > > server.document-root = "/home/user/public_html" > > fastcgi.server = ( > > "/mysite.fcgi" => ( > > "main" => ( > > # Use host / port instead of socket for TCP fastcgi > > # "host" => "127.0.0.1", > > # "port" => 3033, > > "socket" => "/home/user/mysite.sock", > > "check-local" => "disable", > > ) > > ), > > ) > > ======================================== > > > I have run this call to start fastcgi > > python manage.py runfcgi method=threaded protocol=fastcgi > > host=127.0.0.1 port=3033 > > > Here is my question: > > The mysite.fcgi file doesn't matter, right? It doesn't have to exist > > as lightTPD knows about the fastcgi through the host and port > > settings, right? > > I just found that it does. > > lighttpd does a stat on that file before serving the request and if > it's not there lighttpd just returns 404. Put the file there and it'll > send the request. > > NOTE: this ONLY happens when you're doing tcp based fcgi. When you're > doing unix socket stuff it just works and the dummy file doesn't need > to be present. > > Wierd, eh? > > -- > Nic Ferrierhttp://www.tapsellferrier.co.uk --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
