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?<br clear="all">-----------------------------------------------------------------<br><a href="http://eyecreate.googlepages.com/quotes">http://eyecreate.googlepages.com/quotes</a><br><br><br>
<br><br><div class="gmail_quote">On Fri, May 8, 2009 at 4:07 PM, Clinton Ebadi <span dir="ltr"><<a href="mailto:clinton@unknownlamer.org">clinton@unknownlamer.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><a href="mailto:eyecreate@hcoop.net">eyecreate@hcoop.net</a> writes:<br>
<br>
> How would one go about running a django project on hcoop servers. Would<br>
> this require another Apache setup?<br>
<br>
</div>If you use fastcgi (or maybe wsgi; I couldn't tell if it was supported)<br>
you could run your django app using lighttpd behind our main apache via<br>
mod_proxy. Alternatively, if there were a way to run the django<br>
application as a dedicated web server you could sit that directly behind<br>
mod_proxy.<br>
<font color="#888888"><br>
--<br>
So play today<br>
Go make your hay beneath a warm sun shining<br>
But bear in mind one day you'll find the silver cloud's dark lining<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
HCoop-Help mailing list<br>
<a href="mailto:HCoop-Help@lists.hcoop.net">HCoop-Help@lists.hcoop.net</a><br>
<a href="https://lists.hcoop.net/listinfo/hcoop-help" target="_blank">https://lists.hcoop.net/listinfo/hcoop-help</a><br>
</div></div></blockquote></div><br>