There are a few ways.
1) Make sure all your changes are in CVS. Then have your servers build the webapp from CVS. You'll need a script to detect when a new release is available - this should be easy to accomplish.
2) Use mirror/rsync to publish all the files to each server. I suggest not publishing directly to the webapp area itself - but to another location on the server. Then the server can run a local sync. Why? If you need to publish to 2 servers - and the first publish fails half way - your servers can get out of sync.
cron and simple wrapper scripts are your friend
-Tim
John Smith wrote:
Say you have a number of TC instances running from different boxes/IP addresses/locations, and you develop from one of the boxes.
How do you replicate all data/code in all other instances in a reliable way are there RFC or a standard replication protocol to do that?
I have read a number of posts complaining about TC's implementations of webdav and do know there are 'ways' (including the always inviting 'monkey' ones) to do that, but I am asking about best practices that work well with TC.
How do people make these kinds of things happen?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
