Question

I am creating a small commercial web project running Apache/WSGI/Django/MySQL.
I have a development and a production environment and use git and fabric to push/pull modifications.

Now I’d like to be able to test new versions with similar conditions to the production server before making them live.

• I am thinking of using the same physical server with different URLs and different repositories (is this ok ?).
• Are there best practices to set up this pre-prod environment as close as possible to the prod ?
• Should I use the same web server and database server ? In that case how can I manage for example the database name ?

Answer 1

I am working on a similar setup to the one you describe with no major problems. Multiple databases are easily managed in the settings file, I change them based on the root dir name:

ROOTDIR = os.path.abspath(os.path.dirname(__file__))

if ROOTDIR.startswith("dev_"):
    # -------- Developing settings ---------
    DOMAIN_NAME = 'dev.foo.com'
    DATABASES = {
        'default':{
            'ENGINE': 'django.db.backends.postgresql_psycopg2', 
            'NAME': 'development_db',         
            'USER': 'xxxx',          
            'PASSWORD': 'xxxxx',       
            'HOST': 'localhost',         
            'PORT': '',                  
            'OPTIONS': {'autocommit': True,}
        }
    }


elif ROOTDIR.startswith("production_"):
    # --------- Production settings --------
    DEBUG = False
    DOMAIN_NAME = 'production.foo.com'
    TEMPLATE_DEBUG = DEBUG
    DATABASES = {
        'default':{
            'ENGINE': 'django.db.backends.postgresql_psycopg2', 
            'NAME': 'production_db',     
            'USER': 'xxx',           
            'PASSWORD': 'xxx',        
            'HOST': 'localhost',         
            'PORT': '',                 
            'OPTIONS': {'autocommit': True,}
        }
    }
else:
# ....