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 <http://github.com/bmbouter/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 to run code from many different sources and if they all ran as the > same user, then one django project could monkey patch another one which > creates all kinds of interesting security issues. > > Brian > > On Thu, Oct 14, 2010 at 4:45 PM, Diederik van der Boor <vdb...@gmail.com>wrote: > > 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 > > "Django users" group. > > To post to this group, send email to django-us...@googlegroups.com. > > To unsubscribe from this group, send email to > > django-users+unsubscr...@googlegroups.com<django-users%2bunsubscr...@goog > > legroups.com> . > > For more options, visit this group at > > http://groups.google.com/group/django-users?hl=en. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@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.
