Comments on: Franchising: Running Multiple Sites from one Django Codebase

By: r3dfish

r3dfish — Fri, 01 Apr 2011 13:03:30 +0000

Amazing article. I used it as the base for my setup. Heres the howto I wrote: http://blog.hackedexistence.com/the-power-of-django-9-websites-1-database

By: The Power of Django: 9 websites, 1 database | Hacked Existence

The Power of Django: 9 websites, 1 database | Hacked Existence — Fri, 01 Apr 2011 12:46:16 +0000

[...] Shoutouts Most of this information came from Franchising: Running Multiple Sites from one Django Codebase by Huy Nguyen. Really great [...]

By: Stuart

Stuart — Tue, 01 Feb 2011 14:43:14 +0000

@Ben one thing I am trying right now is to put all the css/js/images under a default directory, e.g. /static/default/ then for each site add /static/ then then selectively use the material as appropriate. That way the site specific directories only need to contain the over-ridden files.

It’s not perfect but there is a clear separation between sites which avoids a number of headaches.

By: Ben

Ben — Thu, 11 Nov 2010 00:48:26 +0000

great article…I’m doing something very similar with a few sites now. My last remaining issue is the media files (css/js/img) that are 90% the same across sites. I need a simple way to have a base media directory and override certain files per site, etc. Any thoughts on this?

thanks…

By: Sjoerd

Sjoerd — Tue, 08 Jun 2010 13:48:27 +0000

I rewrote the last 2 lines to the following which seems to work:

exec “from %s.urls import urlpatterns as site_urls” % (settings.OVERLOAD_SITE_MODULE)
urlpatterns = site_urls + urlpatterns

Now it ties two lists together.

By: Sjoerd

Sjoerd — Mon, 07 Jun 2010 21:45:20 +0000

Just what I needed!
There one thing that’s bugging me regarding the global and site-specific URLs:

I get this error when trying to tie these two together (urlpatterns = site_urls + urlpatterns) since site_urls here is the entire module:

Exception Value:

unsupported operand type(s) for +: ‘module’ and ‘list’

Exception Location: /var/www/myproj/../myproj/urls.py in , line 44

By: Huy

Huy — Tue, 21 Jul 2009 20:11:35 +0000

dor,

The major advantage of this approach is for people who developed their sites initially for one organization but ultimately want to replicate their work for multiple organizations without having to go back and do a lot of work restructuring their models and views With this approach, you make a new database, add some few custom templates and you essentially replicate the functionality from your 1st site to a multitude of other sites.

By: dor

dor — Thu, 16 Jul 2009 20:34:35 +0000

thanks for the interesting article

what are the pros and cons of running the sites from different databases VS running the sites from a single, shared database?