[Top][All Lists]

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

Re: Managing Web Page Components with CVS

From: douggorley
Subject: Re: Managing Web Page Components with CVS
Date: Sun, 24 Nov 2002 17:46:17 -0800

----- Original Message -----
From: address@hidden
Date: Sunday, November 24, 2002 2:23 pm
Subject: Managing Web Page Components with CVS

> Hello list,
> I am currently developing a number of small web sites using Perl's
> Template Toolkit (  I keep the
> templates in CVS, and then build the static html using ttree.  What I
> would like to do is have a common set of site "components" (dialog
> boxes, chart templates, etc.) which are also kept in CVS, but are
> develpoed independently of any given web site.  My idea on how to do
> this was to have a project for each site, a separate project for these
> components, and check out a copy of the components for each project
> when I build the web sites.  I currently have a Makefile that runs
> ttree to build the HTML pages; I think I could add a CVS update of the
> components to the process, so that the pages were always built with
> the most current components.  Does anyone see any problems with this
> approach?
> Thanks for your help,
> Doug Gorley | address@hidden
> _______________________________________________
> Info-cvs mailing list
> address@hidden

One thing I didn't make clear above is that I'd like to check out the 
components to a directory within the directory tree of the web project.  So, if 
the project is checked out to /home/me/mysite, a separate project would be 
checked out in /home/me/mysite/components.  Will CVS have a problem with this 
setup?  In some basic testing it seems to work fine, but I may be missing 


Doug Gorley | address@hidden

reply via email to

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