Reply To: symbolic links in site

As Jim mentioned, there can be problems with symbloic links and caution would need to be exercised.  symlinking of directories will give you a visual indication when you do ls -l that there are symlinks.. You could do hard links but these don’t work across filesystems ( if you split you sites across filesystems) are are always easy to see. tar (aix) does not follow symlinks without the -h option so caution must be used here also.

a revision control system like cvs would allow for common code and has the advantage of allowing one site not having the same revision as another site. The problem may arise in quovadx lack of support of #comments in some files which would be needed for revision control.

with revision control you could inventory all sites for current revisions, see who is at a different revision (comements in the revision would tell you why), etc.

I opt not to use the standard tclproc header for one that has accountability and revision information. (also used in local libs).  The usefulness is for instance a local lib proc is at rev 1.2a on 1 site and 1.3 on another (keept in accesable variable as weel as comments). a tclproc is made and inserted into the sites. the tclproc in the start switch check for the minimum revision of the lib needed and if less sets a flag that will hold the messages in an unprocessed state and echo the problem to the processlog.