say /var/www/html is where the code is served from.
Active symlink is maintained to the proper build which comes from (say hudson/jenkins)
Say the current symlink is /var/www/html -> build.v5
Below commands illustrate the sequence of the deployment via ssh for the next build number 6 (which can even be a no-op build)
tar jcf build.v6.tar.bz2 build.v6
scp build.v6.tar.bz2 prod-server:/var/www/
ssh prod-server 'VER=6; cd /var/www && tar jxf build.v$VER.tar.bz2 && ln -sf html build.v$VER && sudo service httpd reload'
Similar logic is followed with the help of git/etc. Idea is to 'keep versions' of your code. so that if things get messed up you can rollback quickly. Most people don't think of rollback, until it bites them really bad !
Active symlink is maintained to the proper build which comes from (say hudson/jenkins)
Say the current symlink is /var/www/html -> build.v5
Below commands illustrate the sequence of the deployment via ssh for the next build number 6 (which can even be a no-op build)
tar jcf build.v6.tar.bz2 build.v6
scp build.v6.tar.bz2 prod-server:/var/www/
ssh prod-server 'VER=6; cd /var/www && tar jxf build.v$VER.tar.bz2 && ln -sf html build.v$VER && sudo service httpd reload'
Similar logic is followed with the help of git/etc. Idea is to 'keep versions' of your code. so that if things get messed up you can rollback quickly. Most people don't think of rollback, until it bites them really bad !