Re: Using cvs for websites:

[Derek R. Price]

Todd Mortensen wrote:

> I have used cvs in the past to manage small projects,  This is the first
> time I have used it to manage a php website.
>
> The setup I did is as follows.
> I imported the document root of the website.
> Then removed that copy and checked out a fresh copy from the repository like
> I usually do.
> I then checked out a copy of the site to my home location.   When I do a
> 'cvs commit' at home I have to do a 'cvs update' in the document root to get
> the changes merged across.  This isn't too much trouble (It would be nice to
> get rid of the two step process if anyone has done this type of setup).
>
> But my major question is. How can I update my document root now without
> having 'CVS' directories everywhere.  Can I centralize the location of all
> the CVS database information?

You might want the export command, but I'm not sure it matters.  Apache, at
least is configured by default to ignore CVS directories.

Derek

--
Derek Price                      CVS Solutions Architect ( http://CVSHome.org )
mailto:address@hidden         CollabNet ( http://collab.net )
--
If at first you don't succeed, skydiving is not for you.