Irrational Exuberance

You are writing a comment about Development to Deployment in Django, here is a quick summary:

An overview of my pipeline between development and deployment for Django projects. Fabric and Git turn a potentially unhappy task into something very quick and easy.

You are responding to this comment written by Lars Holm Nielsen on November 4th 2008, 17:40.

We do more or less the same. Instead of importing a Python module we just read an ini file (just a matter of preference compared to a python module). We have a module to locate this ini file, so that it either append the hostname and look for it in a standard location, or it takes the value of DJANGO_SETTINGS_INI env variable and append. This means that we on development machines just place e.g a settings-<hostname>.ini in conf/ dir, while on the production machines (we have 4 atm) we set the env variable in the apache config, so that the load balanced machines used the same settings.ini file, instead of one pr. machine.

We also use Fabric for deployment, and are really happy about it. Only running one command is so much easier and error-free. I also find my self deploying more often since it's painless and leaves less room for mistakes (with deadlines all the time, this really makes the difference between keep up with the work instead of lacking way behind).

Please be aware that comment forms go stale after one hour.

@@ ruby
def a (b, c):
  b * c
end
@@

 ### This is an h3 title
#### This is an h4 title
**this is bold**
*this is italics*

1. This is an
2. ordered list

* And an unordered
* list too

[this is a link](http://www.lethain.com/ "Lethain")