title: What is the best way to handle .htaccess with a git repo?
body: <p>Another developer says we should put .htaccess files in the git repo, but because the live server uses passwords and our local boxes don't, I said we should put them in the .gitignore. However, he says that if you have to have different .htaccess files across instances, you're doing it wrong. I argue not all server instances are going to be the same, and sometimes (if not often) they require their own configurations. He agreed that we could simply create a "htaccess" file in repo that is copied to .htaccess on live, but still preferred doing it his way. To me, things like server config should be kept out of repo. Also I'm not sure I need to change my development OS just to match a live server exactly or run VM software. Am I missing something here? Which is the best way, or what's a better alternative?</p>