Re: Hosting many small Django websites

Thanks for your suggestion about Opus, will look into that. The security concerns are a good argument for running separate wsgi processes afterall. Diederik Op Friday 15 October 2010 00:34 schreef Brian Bouterse: > We host many of our django sites using a django deployer we wrote called > Opus

Re: Hosting many small Django websites

On Fri, Oct 15, 2010 at 5:26 PM, Brian Bouterse wrote: > One of the challenges of going the GAE route is that you need to modify > your application slightly to work with their version of models. Also, you > can't ever run this code off of GAE, so it's kind of a lock-in in

Re: Hosting many small Django websites

One of the challenges of going the GAE route is that you need to modify your application slightly to work with their version of models. Also, you can't ever run this code off of GAE, so it's kind of a lock-in in that respect. That being said it does work very well. Brian On Thu, Oct 14, 2010

Re: Hosting many small Django websites

On Thu, 2010-10-14 at 13:45 -0700, Diederik van der Boor wrote: > I'm curious about using Django for many small web sites. Does this > require each site to run in a separate wsgi daemon process? If so, how > is it possible to keep memory usage shared? I am also interested in this - currently I

Re: Hosting many small Django websites

On Fri, Oct 15, 2010 at 2:15 AM, Diederik van der Boor wrote: > > I'm curious about using Django for many small web sites. Does this > require each site to run in a separate wsgi daemon process? If so, how > is it possible to keep memory usage shared? > Not exactly sure when

Re: Hosting many small Django websites

We host many of our django sites using a django deployer we wrote called Opus . Opus uses a separate wsgi daemon process for each site. Each wsgi process also runs a separate user, so linux would prevent the memory from being shared. In our case though we want

Hosting many small Django websites

Hi, I'm curious about using Django for many small web sites. Does this require each site to run in a separate wsgi daemon process? If so, how is it possible to keep memory usage shared? Thanks in advance, Diederik -- You received this message because you are subscribed to the Google Groups