When a deployment is a bit too much
I recently noticed something a bit weird when looking at the output of git log. There were a bunch of commits with the same commit message in a short period of time.
My team mate's idea was to change something on the staging server, sitting together with a non-developer, trying to find the right way to display something.
As he didn't have a dump of the staging server's database up-to-date enough for his purposes, he found a commit-push-deploy-loop to be the easiest way to go.
Modifying the files directly on the server might have been an option, but that requires a login to that box, which isn't always what you want.
A brief look at cap -T reveals that Capistrano is capable of just what's needed in that case. cap deploy:upload lets you move your local versions of some files to the remote side. No need to commit, let alone deploy.
Sorry, comments are closed for this article.