On Thursday 18 May 2006 23:20, Rob Hudson wrote: > Based on my virtual hosts, can I have the production site list: > SetEnv DJANGO_SETTINGS_MODULE website.settings > and the dev site list: > SetEnv DJANGO_SETTINGS_MODULE website_dev.settings > and everything work? > > Is there something more I need to consider? Is anyone else doing > something similar?
You may have to consider the 'Sites' objects. So far, I have only come across these are used internally only for creating URLs in the RSS/Atom framework. I think this can be taken care of by creating the necessary Site objects and setting the SITE_ID option correctly in your settings files. Other than that I can't see any problems. Luke -- Parenthetical remarks (however relevant) are unnecessary Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ X-Google-Language: ENGLISH,UTF8 Received: by 10.54.68.15 with SMTP id q15mr149925wra; Sat, 20 May 2006 09:31:04 -0700 (PDT) Return-Path: <[EMAIL PROTECTED]> Received: from out3.smtp.messagingengine.com (out3.smtp.messagingengine.com [66.111.4.27]) by mx.googlegroups.com with ESMTP id v11si417440cwb.2006.05.20.09.31.02; Sat, 20 May 2006 09:31:04 -0700 (PDT) Received-SPF: neutral (googlegroups.com: 66.111.4.27 is neither permitted nor denied by best guess record for domain of [EMAIL PROTECTED]) Received: from frontend3.internal (frontend3.internal [10.202.2.152]) by frontend1.messagingengine.com (Postfix) with ESMTP id 589FDD62E61 for <django-users@googlegroups.com>; Sat, 20 May 2006 12:31:01 -0400 (EDT) Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by frontend3.internal (MEProxy); Sat, 20 May 2006 12:31:02 -0400 X-Sasl-enc: TOvXyHl5eKU8anYn8+yXqXov7e647JzvglcJ1SItoDTP 1148142661 Received: from calvin (host86-141-27-140.range86-141.btcentralplus.com [86.141.27.140]) by mail.messagingengine.com (Postfix) with ESMTP id B0B15132E for <django-users@googlegroups.com>; Sat, 20 May 2006 12:31:01 -0400 (EDT) From: Luke Plant <[EMAIL PROTECTED]> To: django-users@googlegroups.com Subject: Re: Best way to run dev and production site concurrently on same server? Date: Sat, 20 May 2006 17:30:30 +0100 User-Agent: KMail/1.8.3 References: <[EMAIL PROTECTED]> In-Reply-To: <[EMAIL PROTECTED]> X-Face: "N27'AmvBWpdTowy8j|{(HM:g:In+;[nNrbEv6"_B>#oJW=()=?utf-8?q?g=2EtC=3BI9=7CDrpPnB=3Ff=242=5B9V=0A=09?="eYjDWVW[PFOJj5zbG1mZm>y3P^"$Fl)(=?utf-8?q?=3Fx=5E4/rPd4SMJX=7C53PpvkyMk=5F=5CmSl=24oK=25nZf3D=0A=09d=7EK+c?= =?utf-8?q?f=60wDl!q=27P4JNu=5FI=25V0!l=3D1D?="]WrI4&a7~ZZK!-|5T%<W Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Message-Id: <[EMAIL PROTECTED]> On Thursday 18 May 2006 23:20, Rob Hudson wrote: > Based on my virtual hosts, can I have the production site list: > SetEnv DJANGO_SETTINGS_MODULE website.settings > and the dev site list: > SetEnv DJANGO_SETTINGS_MODULE website_dev.settings > and everything work? > > Is there something more I need to consider? Is anyone else doing > something similar? You may have to consider the 'Sites' objects. So far, I have only come across these are used internally only for creating URLs in the RSS/Atom framework. I think this can be taken care of by creating the necessary Site objects and setting the SITE_ID option correctly in your settings files. Other than that I can't see any problems. Luke -- Parenthetical remarks (however relevant) are unnecessary Luke Plant || L.Plant.98 (at) cantab.net || http://lukeplant.me.uk/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
