On 07-08-18 09:42 -0400, Cliff Hirsch wrote: > On 8/17/07 12:45 PM, "Kenneth Dombrowski" <[EMAIL PROTECTED]> wrote: > > finally, I agree with Chris that anybody doing serious work should be > > using version control, but that is the next step, first you should have > > your file permissions in order , and a reasonably good understanding of > > what the commands above do, and why you want to do it. also, use sudo. > > Are there any issues related to having the version control hidden files and > folders on a production site? Does the Subversion .svn folder need to be > protected on a production site? Is the best practice to do ongoing updates > on a production site using version control or to export specific tagged > versions to a production site (which would remove al the version control > specific hidden files)?
Hi Cliff, I would never release a production site as a working directory; I only agree that version control is important for serious projects. I do check out my dev sites as working directories, and typically set up cvs to trigger an update of the dev site for every commit for moving to testing & production, I use shell scripts which operate on specifically tagged versions & perform an export, like you describe Kenneth _______________________________________________ New York PHP Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
