Committing Machine Specific Configuration Files

Question

A common scenario when I develop is that the codebase will have several config files which require machine specific settings. These files will be checked into Git and other

Answer 1

I do it like it's recommended here with default and local config files. To manage my local config files wich are in the projects .gitignore, I made a git repo ~/settings. There I manage all my local settings from all projects. You create, for example a folder project1 in ~/settings and put all the local config stuff for this project into it. After that you can symlink that files/folder to your project1.

With that approach you can track your local config files, and don't put them into to the normal source code repository.