How to version control config files pragmatically?

by

Instead of version-controlling the actual configuration file, you could put a template or defaults file in version control, and a script that would ask for DB information and credential to generate the real config file, which would be excluded from (i.e. ignored by) version control. On checkout, developers could run this script to get a working environment. This script could also be invoked as part of any installation process that your application uses.

Also see my answer to a similar question.

More Related Contents:

  1. How do I migrate an SVN repository with history to a new Git repository?
  2. Checkout one file from Subversion
  3. How and/or why is merging in Git better than in SVN?
  4. Do I really need version control? [closed]
  5. How does Git solve the merging problem? [closed]
  6. Why is branching and merging easier in Mercurial than in Subversion?
  7. How do you organize your version control repository?
  8. Why should I use version control? [closed]
  9. Structure of Projects in Version Control
  10. How do you deal with configuration files in source control?
  11. Common Types of Subversion Hooks
  12. To put the prefix ? to codes by Git/SVN
  13. What are the relative strengths and weaknesses of Git, Mercurial, and Bazaar? [closed]
  14. Are subversion externals an antipattern?
  15. Can we finally move to DVCS in Corporate Software? Is SVN still a ‘must have’ for development? [closed]
  16. Externalising SCM credentials with Maven
  17. examining history of deleted file
  18. How to use SVN, Branch? Tag? Trunk? [closed]
  19. How do I get a list of all unversioned files from SVN?
  20. What makes merging in DVCS easy?
  21. Dealing with SVN keyword expansion with git-svn
  22. Delete file with all history from svn repository
  23. What makes some version control systems better at merging?
  24. How do I create a branch?
  25. How can I force subversion to commit an unchanged file?
  26. Handling renames: svn vs. git vs. mercurial
  27. Should I store all projects in one repository or multiple?
  28. How would you organize a Subversion repository for in house software projects?
  29. Moving SVN repositories data with history as subfolders into another repository
  30. How to synchronize two Subversion repositories?

Leave a Comment