On Sat, Jan 24, 2015 at 10:20:46AM +0630, Arup Rakshit wrote: > On Friday, January 23, 2015 01:14:03 PM you wrote: > > [..] > > There are some configuration files, like `database.yml`, where we > generally put our local DB credentials and we don't want to share such > things. That's why we always put related settings inside the > .gitignore file. But while I will change it, git will not track the > changes of the file, but .gitignore. That's why I used the first > thread command. But when the time the came to take a `git pull`, I got > to know about the mess. What should be the ideal decision in this case > ? > In an ideal sittuation, configuration data is not stored inside git, because this would tie the code only to one environment. So what you would store in git is a template of the configuration data, that can be used to create the actual config file that is used. This way, you don't have any problems with having to change tracked files only for you local environment. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html