Can I configure web.config conversion for appharbor deployment?

Question

Check out AppHarbor today. My main question is in the title, but I have other questions related to git + windows.

First of all, it is connected with this video . I like the idea that I can specify configuration conversions for deployment. My question is: do I need to convert Web.Release.config? I really want to verify this using it as a qa deployment for integration tests. Can I specify the conversion as Web.DeployToAppHarbor.config instead?

Secondly, I read about the crlf problem. When I run git add . Should I get all these messages?

 warning: CRLF will be replaced by LF in [path]. The file will have its original line endings in your working directory. 

Along these lines, should I also get all this message after running git commit -m "Initial commit" ?

 create mode 100644 [path] 

If this is normal, is there a way to make git bash less verbose?

Answer 1

If you are not going to use one platform, it is recommended to set autocrlf to false and not have Git change the end of lines.

AppHarbor will always use Web.Release.config . If you need alternative configurations for qa and others, for example, "staging", you can have those but manage them well in separate branches. When you merge with these branches, use -no-commit in the merge command and make sure the merge does not change them with git checkout HEAD -- config . Then complete the merge using git commit .

Even better, you could save the configuration change in a special branch where you change the configuration properties to the product configuration. After each merge, you can apply this commit as a patch. This would make it easier to combine other changes into the configuration, but after you have selected cherry picks, you can only change those special properties that you like.