Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.
Trip Kirkpatrick wrote: > It seems like you are implying that we need to have CVSNT or a CVS > client running on our staging server as well as our production server? > That doesn't seem right. That's one possibility, but not the only one. > > Or can CVS push files out to a directory that is (a) referred to by its > UNC name and (b) on a server that isn't running CVSNT or a CVS client? You can set up a script that will be fired every time there is a commit in the repository. That script can do anything you can imagine, limited only on your imagination and patience to implement. > > Sounds like what I want is a postcommit script to sync a directory on > the dev server, which directory can then be used to copy files to > staging and production. > Yup. There is also the newer COM interface, but I don't know much about that. It might be another route. I certainly wouldn't use a script to automatically update production. Personally, I have a script that I run to post my project to test and prod that I run from my client. It also updates the tags in CVS so I have a marker on the current versions in test / production. In an environment when you want a common test server for multiple developers, an automatic posting on commit script should work nicely. Regards, -- Glen Starrett