I am searching at establishing small businesses that hosts expensive-based websites for artist investment portfolios. The client user interface could be django-powered, and provides the interface for uploading their images, controlling art galleries, selling prints, etc.

Seeing since most of visitors to the located sites would finish up at their top level domain, this could lead to only static media hits (the HTML page using the embedded expensive movie), I possibly could setup lighttpd or nginx to deal with individuals demands, and pass the django stuff to apache/mod_whatever.

Appears as though I possibly could set all of this on one box, using the django sites framework keeping each site's admin separate.

I am not a server admin. What are the gotchas I am not seeing?

Maybe. I do not think the built-in admin interface is actually made to corral admins to their own sites. The sites framework is much more suitable for publish exactly the same content on multiple sites, to not constrain customers to 1 site or any other. You would be best writing your personal admin interface that makes sure individuals separations.

So far as serving content goes, it appears as if you could offer a typical (static) Expensive file that utilizes an engaged XML file to complete content. If you are using Django to create the XML, that will provide you with the dynamic content you'll need.

This django snippet may be what you ought to have them seperate:

http://world wide web.djangosnippets.org/clips/1054/

"A simple multiple user blog model by having an admin interface set up to simply allow individuals to edit or remove records they have produced themselves, unless of course they're an excellent user."

With respect to the quantity of sites you are likely to host it may be simpler to create just one Django application once, with admin, and to produce a separate Django work for each new site. This really is simple, it really works without a doubt So that as an additional benefit you can include features to more recent sites without running the chance of leading to problems in older sites.

On the other hand, it may be handier to personalize the admin so that you limit the quantity of objects customers can easily see to individuals around the given site itself. This really is simple enough to complete, allthough you might like to use RequestSite rather than the typical Site in the sites framework as that needs separate configurations for every site.

There is available that one method within the ModelAdmin which you'll override to possess manual treatments for the objects being edited.