[HCoop-Help] django server

[eyecreate at hcoop.net]

alright, thanks for your inputs. One last thing I can think of is running a
daemon behind the mod_proxy. I have looked at the docs many times and have
understood how to set up the mod_proxy, but I don't understand all the steps
that are needed to keep a daemon running in the background with file access
and restarts on mire restart. Since I'm sure this has been done many times,
could someone explain this to me better?
-----------------------------------------------------------------
http://eyecreate.googlepages.com/quotes




On Fri, May 8, 2009 at 4:07 PM, Clinton Ebadi <clinton at unknownlamer.org>wrote:

> eyecreate at hcoop.net writes:
>
> > How would one go about running a django project on hcoop servers. Would
> > this require another Apache setup?
>
> If you use fastcgi (or maybe wsgi; I couldn't tell if it was supported)
> you could run your django app using lighttpd behind our main apache via
> mod_proxy. Alternatively, if there were a way to run the django
> application as a dedicated web server you could sit that directly behind
> mod_proxy.
>
> --
>                                 So play today
>                  Go make your hay beneath a warm sun shining
>      But bear in mind one day you'll find the silver cloud's dark lining
>
> _______________________________________________
> HCoop-Help mailing list
> HCoop-Help at lists.hcoop.net
> https://lists.hcoop.net/listinfo/hcoop-help
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.hcoop.net/pipermail/hcoop-help/attachments/20090508/d818cfb6/attachment.htm