In the long ago days, I had a collection of shell scripts. They got bigger and wilder and more powerful.
But the helped me automatically sync Drupal 4 sites between dangerous places, places that sometimes didn't even have shell access, and occasionally not even FTP, just a web file manager...

Then a while later, along came drush, and a number of these scripts were replaced by it, yet a larger number lived on, and became drush-i-fied.
Automatic site cloning, FTP sync support via drush, databse conversions from prefixed to non-prefixed and back, on the fly, one-liners to do powerful things.
A small amount of those things tried to make it into drush proper, but most remained on the fringes.

Then later, drush introduced site aliases, which completely replaced my site sync 'site descriptions' with an array that did the same job, so I rewrote my sync scripts to use that method.

And later still, I added new tools to
- provide a wizard for first time setup of site aliases
- automatically generate patch files recording your local changes, before downloading code updates, upgrading, and re-applying your patches
- get the site status report to tell you about missing modules! Which no part of Drupal currently actually does.
- perform drush commands over the wire, through a WEB interface, even if you don't have ssh access !!
..
.
and some more wacky things I've probably forgotten about.

This dirty cluster of scripts has followed me around through a dozen servers now, sometimes living in private CVS, sometimes in the old Drupal sandbox.
I'm about to infect another host with it now, so I may as well infect the git repository also...

beware, this stuff has brains inside it, but it bites.

Drush sync scripts

Issues