On Tuesday 08 September 2009 05:47:32 Benjamin Buch wrote: > Hi, > > I'm working on a small project > trying to get used to the development/staging/production setup. > > I develop on my local machine, > push to a git repo > and pull from there to staging and then finally to production. > > My problem here is that the staging and the production projects are > deployed on the same server. > Thus, the project folders can't have the same names - > the production folder is called say 'myproject', so the staging folder > has to be called different, say 'myproject_staging'. > > Of course I run into conflicts here - > many imports in my code plus settings.py (INSTALLED_APPS, ROOT_URLCONF) > refer to 'myproject' - and not to 'myproject_staging'. > > How can I work around this? > Is it time for me to have a look at virualenv? > > -benjamin > >
I do something similar one site, but both have parent directory that holds
misc data and the project dir, example:
staging/
apache/
apache scripts and custom conf files specific to this deployment
myproject/
...
misc_stuff/
scripts specific to this deployment
live/
apache/
scripts and custom conf files specific to this deployment
myproject/
...
misc_stuff/
scripts specific to this deployment
Both are checked out from the same svn (instead of git) repo. Staging of
course is where I edit and make changes to the code for live and commits are
from stage. While live is a read only checkout.
For project settings, I use a settings.py and a local_settings.py file,
local_settings.py is not in revision, as where settings.py is, and lives in my
project directories. It holds deployment specific paths, required variables
and info. settings.py holds info and variables that are constant across
deployments (dev, qc/staging, live).
I've written up this the other day for a friend to learn to use
local_setttings.py file with settings.py. I apologize for spelling/grammar
errors and lack of styling on the pre tags (where the code is), this is a
problem in the middle of being fixed, rewriting this site from the ground up.
My personal site does suffer for a lack of attention to it for a couple years.
http://gufymike.com/archives/detail/18/1/
With this setup I don't need to worry about much in terms of conflicted module
names in the project, you just set the correct paths in your scripts that set
the sys.path, media directories and so on.
Hope this helps,
Mike
--
Nothing in life is to be feared. It is only to be understood.
signature.asc
Description: This is a digitally signed message part.
