Re: recipe to use git for deployment

Neal Kreitzinger [off-list ref] writes:

I'm trying to cook up automated mass deployment using git as the main
ingredient.

I think the standard answer to this is "don't do it".

You could of course add hooks to hack around it, but fundamentally Git was
designed to track source files (so the only sane behaviour for "checking
out" is to keep the timestamp of the working tree file to whatever the
underlying OS gives it when "checkout" happens, for example), so anything
that your "deployment strategy" wants conflicts with what the usual source
coutrol operation should do, you need to tweak around what Git does (the
same thing can be said for CVS or SVN, by the way).

Unless you do this with an understanding that you are merely using git "as
a better rsync" and take responsiblity of everything else that git-the-scm
does _not_ do for you, I suspect that you would be volunteering for a lot
of pain.