Vlad: Deploy Steps

The default Vlad rules go from source control to the web site in one step. These are the steps we go through...

mywaves Deploy Steps
Location	Internal					External
	Source Control	Tarball Packages		Internal Master		Remote Master		Production Hosts
	Source Control	Tarball Packages		Internal Master		Remote Master		Image		Destination
Flow	check out web create tarballs		extract tarballs		rsync web		rsync to web image		rsync to apache
	check out web create tarballs				rsync web		rsync to web image			restart apache
	check out utilities compile create tarballs				rsync to migration directory
	check out utilities compile create tarballs									rake migrate

We create tarball packages because:
- We want a snapshot of a specific, tested version, and do not to pick up the latest change in source control.
- We need to compile some utilities, so we need a build step anyway.
We create an internal master image from multiple tarballs as the source for rsync.
We create separate web and migration directories because we must finish the migration before restarting apache, and sometimes we migrate before the push.
We rsync to a remote master image because there are several production hosts and it would be too slow to rsync directly to all of them.
Image on each production host:
- New .rhtml files sometimes refer to methods that will not be defined until apache restarts with the new code, so we must rsync from a local copy to minimize the time between updating and restarting.
- When rsync fails, it is usually copying between hosts, so we get a local image on all production hosts before overwriting the apache directory so all hosts update at the same time.
We do an rsync between local directories on each remote host before running the migration or restarting apache.