Hi I am trying to run around 50 mini sites which share about 90% of their code. Each site simply queries and API and returns the results, and will be on it's own domain, and have a different style.css and config.py. The userbase (and the database generally) will be shared across the board. My initial idea was to run them as separate applications with a common library, each with their own UWSGI thread. However, I have concerns about large memory use.
I have read about the sites framework which would allow them to run from a single instance. https://docs.djangoproject.com/en/dev/ref/contrib/sites/ My question is, is the site framework the right approach to a problem like this, and does it have real benefits over running separate applications. I have heard the following: *Your SITE_ID is set in settings.py, so in order to have multiple sites, you need multiple settings.py configurations, which means multiple distinct processes/instances. You can of course share the code base between them, but each site will need a dedicated worker / WSGIDaemon to serve the site.* Alternative ideas of systems: https://github.com/iivvoo/django_layers https://github.com/shestera/django-multisite Any ideas or help would be most appreciated. James -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. For more options, visit https://groups.google.com/groups/opt_out.
