On 8/2/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> 4 steps.
>
> 1. copy the settings.py to new-settings.py
> 2. add a site_id via the admin tool
> 3. configure new-settings.py, changing the cookie name, SITE_ID, and
> SECRET_KEY as above
> 4. clone your httpd.conf with so that it uses
Hi Jay.I have a similar issue.I have stuff in http://zyons.com, which is open source, and another set of apps which build on top of it which run on multiple hosts. (http://gyspsyjobs.com & http://car-chatter.com for example)the way I set it up is:project/ common/ app1/ templates app2/
Eww, the title of this thread was *supposed* to be "Project layout
when using multiple sites". Gotta remember to proof-read the subject
line before submitting!
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
I've recently been looking at the docs, trying to grok the Sites framework.
What is the recommended way of laying out the filesystem when doing
multiple sites? Let's say I have two sites, "foo" and "bar", with URLs
foo.com and bar.com.
Would you put all the files for both sites into one Django
4 matches
Mail list logo