Everyone,
I had a similar conversation with another client a year ago.
He wanted the publishing to be published 2 servers. Naturally, we would setup 2 publishing targets. However, know how CMS publish works, CMS would finish publishing to one target before beginning to publish to another target, hence creating a large publishing time window.
I suggested an alternative solution. On web server #1, setup a file system watcher, on file change, copy file to server #2.
This is really a choice of Information System management. Does one want to control the publishing setting from 1 system (CMS) or multiple systems (CMS + A webserver).
Neil, in your case, the choice is up to you as well. 2 publishing targets or 1 publish target + a replication/cleanup process somewhere else.
Best regards,
-Jian
On Monday, December 2, 2013 10:51:25 AM UTC-5, Neil Fegen wrote:
Hi Tim
Thanks for the reply.
We want minimal publishing overhead so think we'll do a one-time copy of the image folder to the new server, and then run a job to pick up any changes from the source folder and replicate as required.
Thanks
Neil