Maybe I'm over simplyfying this ... but why not just swap out the css file you are using based on a setting you can change in your settings.py file....as well as modify the database you are calling in your settings.py file, and store your messages in a table... where the data would be different in each database?
On Apr 10, 6:10 am, Tim Sawyer <[EMAIL PROTECTED]> wrote: > Came across this the other day, never used it. > > http://code.google.com/p/django-databasetemplateloader/ > > It seems to allow you to store templates in the database, so could this be > used together with the sites framework to skin your sites differently? > > Tim. > > On Thursday 10 Apr 2008, Polat Tuzla wrote: > > > Hi, > > I'd like to build two sites, say, two polls sites, each having their > > own domain name. Their functionalities are almost exactly the same. > > They're different only by theme. By theme, I mean both the site design > > (visual theme) and the site messages. For example one is for polls > > about music and the other is about videos. > > > I'd like to be able to use the same source code (i.e same django > > project) for running both of these sites for the ease of maintenance. > > This may be by running either a single instance of django, or two. But > > again, I'd prefer single instance for the ease of administration. This > > would also let me have a single sign-on functionality as a side > > effect. > > > The site message strings are scattered in models, views and template > > files. I don't want to duplicate any of these codes just for the sake > > of alternating between different messages. I tried to find a way out, > > by using sites framework, but wasn't able to without actually > > duplicating views and templates. > > Another option was using i18n, and two different translation files > > between two django instances. But this only works for languages other > > than English, I guess. > > > What exact way of achieving this would you suggest me? > > I've been doing research on this for quite a long time, but really > > could not come up with a solution. Any suggestion is greatly > > appreciated, even those like "don't do this, duplicate the project" :) > > Thanks, --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
