Tag "production"

better localsettings import

Most people simply wrap "from localsettings import *" in a try/except ImportError block. That's what I've done for years, but recently came up with this better way. The problem this snippet solves is that if your localsettings.py itself causes an ImportError somehow, that error will be silently swallowed and your intended localsettings will be ignored. Instead, we use `imp` to first check if the module exists, then unconditionally try to import it.

• development
• staging
• production
• localsettings

Mon 01 Feb 2016 Read More

Dev/staging/prod environment settings seperation

Read code for info

• settings
• staging
• environment
• production
• dev
• prod
• seperation

Thu 16 Aug 2012 Read More

Read settings from local_settings.py

Each installation of our Django site has slightly different settings -- namely, which database to use. Developers can provide a `local_settings.py` file which lets them override (or, just as usefully, extend) settings that are in `settings.py`. Subversion is told to ignore `local_settings.py`, so it's never checked in. If `local_settings.py` is missing, the site refuses to work. We include a `local_settings_example.py` file so that new developers can get started more quickly.

• settings
• development
• deployment
• deploy
• production
• local
• local-settings
• local-deployment

Mon 11 Mar 2013 Read More

Load a local settings file for dev/test environments

Add the snippet to your settings.py. If you have a settings_local.py it will load that one. Can be used in development environments where you might have different settings for your dev sandbox. You should exclude settings_local.py from SVN. By Rudy and Ed Menendez

• settings
• environment
• production

Wed 03 Nov 2010 Read More