On Fri, 29 Mar 2013 00:40:12 -0700 (PDT) surya <kasturisu...@gmail.com> wrote:
> In our project, as its opensource, the master branch can't be > directly pushed into Production server as it contains confidential > settings.. For that I (admin of server) created a local branch to > specifically contain production settings using local_settings.py.. > The master is merged as into this branch as soon as we release new > feature/ fix bug etc.. (any better way of handling. please tell me) Well, one interesting concept I've see is from the Two Scoops of Django (I join the minions on this group that recommend this book - probably one of the best buys in my life) - the authors use separate configuration files for production, test, development (even per-developer settings), storing all of them in the repo, _but_ they don't store any confidential data in those files. Instead of that they use environment variables to make the passwords available to user running the code, and then inside of "base" settings.py they use a bit of Python code to read them and assign them to appropriate variables. There's probably a couple of variations on this as well - for example storing path to file containing the password in environment variable, and then reading from there etc. Best regards -- Branko Majic Jabber: bra...@majic.rs Please use only Free formats when sending attachments to me. Бранко Мајић Џабер: bra...@majic.rs Молим вас да додатке шаљете искључиво у слободним форматима.
signature.asc
Description: PGP signature
