<p>I'm looking at setting up a small company that hosts flash-based websites for artist portfolios.  The customer control panel would be django-powered, and would provide the interface for uploading their images, managing galleries, selling prints, etc.</p>

<p>Seeing as the majority of traffic to the hosted sites would end up at their top level domain, this would result in only static media hits (the HTML page with the embedded flash movie), I could set up lighttpd or nginx to handle those requests, and pass the django stuff back to apache/mod_whatever.</p>

<p>Seems as if I could set this all up on one box, with the django sites framework keeping each site's admin separate.</p>

<p>I'm not much of a server admin. Are there any gotchas I'm not seeing?</p>

Maybe. I don't think the built-in admin interface is really designed to corral admins into their own sites. The
```
sites
```
framework is more suited to publish the same content on multiple sites, not to constrain users to one site or another. You'd be better off writing your own admin interface that enforces those separations.
As far as serving content goes, it seems like you could serve up a common (static) Flash file that uses a dynamic XML file to fill in content. If you use Django to generate the XML, that would give you the dynamic content you need.