2006/6/13, Malcolm Tredinnick <[EMAIL PROTECTED]>:
Ok, that's clear.
In fact, what I want is a bit complicated (I'm a beginner in both Django and Apache so maybe I'm not at the right place to talk about it). The idea is to have two domain names for example mysite.com and mysite.fr, if people comes from .fr the lang should be french, english otherwise. If the browser language detection is french and th site .com, display a message to inform that the .fr exists.
Now the problem is for applications, if I want a blog on both sites, I have to traduce views in both french and english with gettext (category => categorie, etc) but content is not the same too and I'm not sure it's eventually the right solution to store both content in the same tables, maybe it's easier to have two separated applications? In this case I have to duplicate code and that's not really the django philosophy...
What's your opinion about that? (maybe I'm not clear because english is not my mother tongue, do not hesitate to ask for precisions).
Thanks for your answer, I've already posted a ticket about another issue but I don't know if it's the right thing to do because it's still new:
http://code.djangoproject.com/ticket/2132
Maybe I made a mistake? or am I impatient?
Cheers,
David
On Tue, 2006-06-13 at 11:21 +0200, David Larlet wrote:
>
>
> 2006/6/13, Malcolm Tredinnick <[EMAIL PROTECTED]>:
>
> On Tue, 2006-06-13 at 10:39 +0200, David Larlet wrote:
> >
> >
> > 2006/6/13, Ian Holsman <[EMAIL PROTECTED]>:
> >
> > Hi Daniel.
> > I'm doing this right now on http://zyons.com and
> > http://economy-chat.com
> > the trick is to use the directive
> > 'pythoninterpreter XYZ' in each virtual host
> >
> > regards
> > ian
>
>
> > Really interesting, is it possible to have a verbose
> explanation of
> > exactly what you've done or better a wiki page on django
> site? I think
> > many people want to do the same.
>
> It's already part of the main documentation. See
> http://www.djangoproject.com/documentation/modpython/#multiple-django-installations-on-the-same-apache
>
> Yep I've already seen it but I think a complete example which deals
> with virtualhosts and internationalization will be a must have. By the
> way, the title of the doc is "multiple django installations" that is
> not really true or I've missed something, the django source is
> installed once, right?
The core Django source is only installed once, yes. By multiple
installations, we mean multiple installations of Django projects.
Ok, that's clear.
As far as extending the documentation goes, it's not clear what you are
after (particularly since we seem to have answered the original poster's
question already). The Django mod_python docs already cover multiple
virtual hosts and multiple locations within a single virtual host. I'm
not sure what you mean by "and internationalization": browser language
detection and redirection can be copied from the standard Apache setup
if you want that -- we shouldn't replicate large portions of the Apache
documentation because it is hard to stay in sync (and track all
versions) and because as the documentation increases in volume, it
sometimes decreases in utility as there is more information to slog
through to get to the bit any particular user needs.
In fact, what I want is a bit complicated (I'm a beginner in both Django and Apache so maybe I'm not at the right place to talk about it). The idea is to have two domain names for example mysite.com and mysite.fr, if people comes from .fr the lang should be french, english otherwise. If the browser language detection is french and th site .com, display a message to inform that the .fr exists.
Now the problem is for applications, if I want a blog on both sites, I have to traduce views in both french and english with gettext (category => categorie, etc) but content is not the same too and I'm not sure it's eventually the right solution to store both content in the same tables, maybe it's easier to have two separated applications? In this case I have to duplicate code and that's not really the django philosophy...
What's your opinion about that? (maybe I'm not clear because english is not my mother tongue, do not hesitate to ask for precisions).
But still, if you have some concrete suggestion, please open a ticket
with the specifics and we'll see what we can do.
Thanks for your answer, I've already posted a ticket about another issue but I don't know if it's the right thing to do because it's still new:
http://code.djangoproject.com/ticket/2132
Maybe I made a mistake? or am I impatient?
Cheers,
David
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---
