Slashdot Mirror
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 CMSes on a few LAMP servers (mostly Drupal). I've written a few scripts that check out 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 check in files to the repository and move files/DBs through the different environments. I'm finding as our company grows (we currently host 50+ sites) it is cumbersome to manage all sites by 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?"
They could be a n00b.
If they only have a wooden sword and shield, and 100 gold pieces then they're probably a n00b.
but if nobody tells a n00b that he is a n00b, is he really a n00b then?
What if the n00b is in the forest? Does anyone hear the n00b fart?
Facebook is the new AOL
probably not... but then said n00b will be spamming help/shout/local/whatever about how they changed the controls since beta...
but since the n00b is a n00b, will anyone actually hear a n00b screaming?
give BSD credit
nuf said.