I would like to deploy multiple django projects that are either completely
unrelated, but deploy them on the same server running apache. I am not a
savvy apache administrator and our small company does not have one. The
use of virtualenv is probably a good idea, but not mandatory in that we
On Nov 20, 4:33 am, Stodge wrote:
> I got this working with several sites using Apache. I just created a
> configuration file for each site and pointed it to different settings
> files:
>
>
> SetHandler python-program
> PythonHandler django.core.handlers.modpython
>
On Thursday 19 Nov 2009 11:01:10 pm Eric Elinow wrote:
> I currently do this for the 5 or so sites that I operate for a client. A
> single Apache setup for Django, with the various virtual hosts being
> directed to their own path(s), and any static media requests being port
> forwarded from
i would suggest to everyone start using buildout to develop or deploy.
it gives so many advantages about separation between projects.
a huge advantage is the repetibility of the project and you dont have to
touch the pythonpath of your server, everything is done by the buildout
configuration!
I got this working with several sites using Apache. I just created a
configuration file for each site and pointed it to different settings
files:
SetHandler python-program
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE test.settings
PythonOption
On 19 Nov, 2009, at 12:23 , Mark Freeman wrote:
> I currently have a working site running Django and now want to move a
> couple of other of my sites to Django as well. I'm in the process of
> moving off a hosted VPS to my own local server, where the existing
> Django site is.
>
> My questions
I currently have a working site running Django and now want to move a
couple of other of my sites to Django as well. I'm in the process of
moving off a hosted VPS to my own local server, where the existing
Django site is.
My questions is more of best practice when deploying multiple sites to
the
7 matches
Mail list logo