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 is more of best practice when deploying multiple sites to
> the same server. Given that I have a running site, is it possible to
> deploy multiple Django 'projects' to the same server and just use
> Apache to serve them out separately or is it best to use the sites
> module to do this from the same project? For code cleanliness, I would
> prefer to have them as separate projects, but I don't want to kill
> server performance either.
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
apache to a lighttpd instance. I have my /sites/ path containing each project
(sites/site1 sites/site2 etc.) and have had this setup for quite some time with
absolutely zero problems.
Eric G. Elinow
http://www.codedevl.com
>
> Thanks for any suggestions!
>
> --
>
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to django-us...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-us...@googlegroups.com.
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-users?hl=.
