> Linus posted a response about deployment and development being > separated, so I had to point out why that doesn't work for web apps in > interpreted languages. > If your primary concern is preventing information leakage, then a publish model is absolutely what you want. You definetely don't want some random intermediary file out on the server, or some file that was never checked into source control. By publish, I don't just mean to the public server, I also mean to whatever development roots you have. With a good publishing model and a good SCM, you also get reproducibility and testability as well. Its easy to ensure that what is checked into source control is what you are testing, and its easy to rollback production servers to a different version. - 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
