[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: CVS & a Web site

From: Thornley, David
Subject: RE: CVS & a Web site
Date: Wed, 17 Oct 2001 16:43:40 -0500

> -----Original Message-----
> From: Jason Purdy [mailto:address@hidden
> Sent: Wednesday, October 17, 2001 3:22 PM
> To: address@hidden
> Subject: CVS & a Web site
> Hi,
> What is a good scheme of automating synchronization between a 
> CVS repository 
> and a Web site (or does a repository have to be separated 
> from the Web site 
> files [besides renaming the files from the ",v" suffix])? 

More than that is required.  You will need to checkout or
export the files, not just rename them from the repository.

> co-worker & I 
> have recently decided to work with CVS on our ever-growing 
> Web site, and I've 
> got CVS up & going, but lack an important piece of the puzzle 
> - getting data 
> out of the repository and into the Web site (hopefully in an 
> automated 
> fashion).
> I have a couple of ideas, but before I go down a road that's 
> surely been 
> traversed before, I'd love to get some input from the more 
> travelled on the 
> list.  I hope there's already a solution for this scenario, 
> though I couldn't 
> find anything on the Web site or in a Google search.
> 2) Create 'trigger' scripts which would be triggered when the 
> developer 
> 'commit'ed their changes, which would also affect the changes 
> on the Web site 
> directories.
This is the correct answer, and the file you are looking for
is commitinfo within CVSROOT.  That file will specify programs
to be run when something is checked in, and one to check out
changed files and copy them to the web site should work just

Since you've been searching in the right place, you should be
able to find the commitinfo material in the documentation.
Sounds like all you needed was a pointer.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]