Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have 4 web servers in a cluster that need to all have the same code on it and pushing code to each server seems to be a tedious task. I was wondering if it is good or bad practice to use subversion to manage asp.net & MVC code deployments. My deployments would go from copy/pasting files to each server to just doing svn update at the webroot of each server. Is there any good reason why this would be a bad idea? I apologize if this is the wrong place for this question.
Yes, you could use SVN to keep your servers up to date. However, I would take it one step further and use Continuous Integration. Long story short, you would need to set up a Continuous Integration server such as CCNet or TeamCity that will automate your build and deployment process so that you can release your updates to all servers with only a few clicks.