Re: [lula] CVS web site administrator's tutorial

[Dan Kegel]

Steven,
Those tips are great.
My writeup as it stood was a bit dangerous, I guess!

(I would not have thought of moving the work directory-
Perforce, Source Integrity, and SourceSafe have brainwashed
me into fixed mappings between repository and sandbox!
However, that trick might be a bit confusing for my
target audience, who tend to have problems with the whole
notion of multiple directories sometimes.  Maybe I'll just hope they 
don't accidentally do checkout instead of update ...)

Thanks!
- Dan

Steven Redlich wrote:
> > I'm starting a tutorial on how to [use cvs for a web site].
> > ... http://www.kegel.com/cvs.html
>
> Dan,  Looks really good.
> 
> Comments:
> 
> If all the users operate as cvsuser, make another user that owns the
> CVSROOT directory.  Failure to do this lets people with write access to
> the repository execute arbitrary files as the cvsuser, by uploading
> their files into CVSROOT. eg as commitinfo
> You can also setup the lock files to be written outside the CVSROOT
> directory.
> 
> for cvs init,  I like to create a subdirectory in the cvsuser account
> for the repository.  Lots of documentation refers to the repository as
> cvsroot,  But I prefer:
> 
> $ cvs -d /home/cvsuser/repository init
> 
> This lets me keep tools and dot files for this account that are not part
> of the repository.
> 
> Regarding binary files, the main advantage of marking them as binary is
> so that cvs does not try to use diff to merge them.
> 
> Regarding the cvs checkout, I've gotten in the habit of renaming the top
> level directory.
> 
> $ mv frivolity frivolity.work
> 
> This way, when I mistakenly type cvs checkout frivolity, instead of cvs
> update, I don't write over the changes I've made in my checkout out
> copy.
> 
> Steve Redlich