Thanks guys for the infos. It makes a lot more sense now. So it looks like Lighttpd does not support the equivalent of mod_wsgi, so requires a second server that speaks either FastCGI or HTTP/WSGI.
On Wednesday, October 24, 2012 5:58:21 PM UTC+2, Fred wrote: > > Hello > > I'm trying to find how to install Python on a Lighttpd server that > currently runs PHP scripts. > > This > article<https://docs.djangoproject.com/en/dev/howto/deployment/fastcgi/>says: > >> Although WSGI is the preferred deployment platform for Django, many >> people use shared hosting, on which protocols such as FastCGI, SCGI or AJP >> are the only viable options. > > > I'm puzzled, because I seemed to understand that WSGI is an API that > relies on a lower-level transport solution like FastCGI, SCGI, or AJP. > > Could it be that the article actually opposed mod_wsgi, which can run > within Apache à la mod_php *? > > And if someone knows of a good way to run Python through FastCGI (with or > without WSGI) on Lighttpd, I'm interested: "Python FastCGI on lighty with > flup" at the very > bottom<http://redmine.lighttpd.net/projects/lighttpd/wiki/Docs_ModFastCGI#Skeleton-for-remote-authorizer>only > seems to run a specific script. > > Thank you. > > * altough it can also run in its own process, just like FastCGI > -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/n62KPozSRhcJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
