How do you manage dev/test/production environments

An anonymous reader writes: I am a n00b system administrator for a small web development company that builds and hosts OSS CMS's on a few LAMP servers (mostly Drupal). I've written a few scripts that checkout dev/test/production environments from our repository so web developers can access the site they're working on from a URL (ex: site1.developer.example.com). Developers also get FTP access and MySQL access (through phpMyAdmin). Additional scripts checkin files to the repository and move files/db's through the different environments. I'm finding as our company grows (we currently host 50+ sites) it is cumbersome to manage all sites hacking away at the command prompt. I would like to find a solution with a relatively easy-to-use user interface that provisions dev/test/live environments. The Aegir project is a close fit but is only for Drupal sites and still under heavy development. Another option is to completely rewrite the scripts (or hire someone to do it for me), but I would much rather use something OSS so I can give back to the community. How have fellow slashdotters managed this process, what systems/scripts have you used, and what advice do you have?