On Wed, 2008-08-06 at 14:59 +0200, Chris Haensel wrote: > > -----Original Message----- > From: Daniel Brown [mailto:parasane@xxxxxxxxx] > Sent: Wednesday, August 06, 2008 1:34 AM > To: Ross McKay > Cc: php-general@xxxxxxxxxxxxx > Subject: Re: Re: An appeal to your better nature > > On Tue, Aug 5, 2008 at 7:28 PM, Ross McKay <rosko@xxxxxxxxxxx> wrote: > > > > Problems I see with the above: > > > > * good IT professionals use version control AND take backups > > * good IT professionals work on dev servers and migrate to test, prod > > * good IT professionals don't tend to claim "guru" status themselves :) > > Addendum: > > * Good IT professionals don't usually criticize one another in a > public forum in the above manner, if nothing else than out of > professional courtesy. > > -- > </Daniel P. Brown> > Better prices on dedicated servers: > Intel 2.4GHz/60GB/512MB/2TB $49.99/mo. > Intel 3.06GHz/80GB/1GB/2TB $59.99/mo. > Dedicated servers, VPS, and hosting from $2.50/mo. > > ROFL > > I never thought someone seriously would go the whole way from dev, test and > prod servers AND use all the version control stuff. > > Honestly: I use dev servers and two backup servers for our company website, > but having a version control system and everything would, in my opinion, > really make this whole being a developer some kind of ... ugh. Might be good > to do, I don't know. Never tried, and probably never will. I use CVS all the way from dev to production with staging in between (except personal projects where I skip staging). Here's an approximation of my update workflow: dev> modify code dev> cvs commit -m 'blah blah comments' dev> ssh staging staging> cvs update staging> ./buildSite.php After feedback from client... dev> ssh production production> cvs update production> ./buildSite.php I use CVS for all my projects. Be they tiny or large. If something goes wrong after production is updated, I just grab a snapshot from when we last had a stable run. Using CVS is well worth the extra 5 minutes I spend at the beginning of a project setting up the repository. When I take over some project that didn't use CVS, the first thing I do is put it in CVS. Usually I find crap like foo.php.bak, foo.php.better.bak, foo.php.good, foo.php.broken littered all over the source tree. Some idiot obviously made them because they didn't use a versioning system. The really sad part is, all these files are usually right there in the production tree. As far as backups go, CVS is on another machine, production and staging are sometimes on the same machine, sometimes on their own machines. Either way, the source exists in 3 physical locations... cvs, dev, staging. And I run nightly backups of CVS. Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHP -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
