[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
module confusion
From: |
Tom Wiebe Lists |
Subject: |
module confusion |
Date: |
Mon, 8 Sep 2003 03:16:28 -0700 |
Hi all,
A little stumped here as to how to do this. I've got a common code base
I use for my websites, which is supplemented with client specific code
on an as needed basis.
I'd like to track the whole mess in CVS, all of our specific client
code, along with the shared code but I can't figure out the module
configuration that will create the desired folder hierarchy on
checkout. here's how I need the hierarchy to be:
/root
/_code <- Client specific code
/media <- Client specific graphics, css, etc
/_base <- Code shared between all sites
/sysmedia <- graphics and css shared between all sites
index.lasso <- shared default page
error.lasso <- shared error page
None of the shared areas will change from site to site and it wouldn't
necessarily be a bad thing if these couldn't be updated outside of
their main repository. The client specific areas are unique to each
site, and everything is contained within those 2 folders. For the
shared resources, everything is also self contained, with the exception
of the index and error pages.
I'd like to be able to create one module for each client that will draw
from the same codebase for the shared files, and the code unique to
that client. My CVS repository is set up as such, but could be changed
if it would help:
/cvshome
/base
/_base
/_sysmedia
index.lasso
error.lasso
/client1
/_code
/media
Any suggestions would be most appreciated. I've been tearing my hair
out trying to figure this out all weekend.
Tom Wiebe