Hello,
I've been thinking about this - probably the best way is if you can find
something built into django (like the i18n framework) which will do
this, but failing that you could try this:
- for the templates, just have two sets of templates, one for each site.
- for strings that are written into the python code, you could do it by
defining a file (call it 'site-strings.py'), which looks something like
this:
site_strings={
'search_error': 'There is an error in your search parameters',
'search_help': 'Enter a title of a video to search for',
...
}
Then in any file where you need to generate hard coded strings, instead
of putting the string in directly, first import site-strings.py, then
refer to the string from the site_strings dictionary.
If you want to have the same django instance running both sites, you
could adapt the above by expanding the dictionary to include a
sub-dictionary for each word:
i.e.:
site_strings={
'search_help': {
videosite: 'enter a title of a video to search for',
musicsite: 'enter a title of an album to search for'
}
....
}
The only problem (I can see) with this method is it might make it hard
to later on add i18n alternate language functionality to your code using
the django framework for that.
andy.
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
-~----------~----~----~----~------~----~------~--~---
