3 ms·

Actually I prefer to have only one settings file and configure everything else with environment variables. For me this is more clean. Make is generally install

Actually I prefer to have only one settings file and configure everything else with environment variables. For me this is more clean. Make is generally installed on most systems, therfore I prefer it over fabric - but the idea is the same. I disagree about sudo pip on Linux, e.g. python-virtualenv wasn't updated for a long time in Ubuntu. Therefore, I still recommend getting the newest with pip. You coud apt-get python-pip, but most other things I would get from pip.

edanm 14y ago
"Actually I prefer to have only one settings file and configure everything else with environment variables. For me this is more clean." Heavily seconded. After many years of having separate files, this grew very unwieldy with multiple environments, machines, developers, etc. The env-variable route is much better, much easier to configure separately for different machines, etc. Also, this is the way Heroku does it - you load up a new server and run several "set env variable to {X}" commands to configure it. I think this is based on the 12-factor app system. (http://www.12factor.net/ http://www.12factor.net/)