Hi Jian
Thanks for the info. We had already decided to go with a job to copy files from server A to B so good to know you have also recommended this. Would be great to see the option to separate content implemented in a future release as performance benefit to serving static content from separate area. Thanks all Neil On Mon, Dec 2, 2013 at 4:07 PM, Jian Huang <[email protected]> wrote: > 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 >> >> On Monday, 2 December 2013 14:55:25 UTC, Tim D wrote: >>> >>> Why not add a second publishing target and use virtual directories and >>> security at the web server to serve them appropriately abstracted from how >>> they are written to the file system. Yes there is some waste in transfer. >>> >>> If you add a project variant you can publish to another target but it >>> will send pages and images. >>> >>> Best, >>> Tim >>> >>> On Thursday, November 28, 2013 4:39:36 AM UTC-5, Neil Fegen wrote: >>>> >>>> Hi all >>>> >>>> We currently have one publishing target, which publishes all HTML pages, >>>> content from each image folder, scripts, etc. >>>> >>>> I'd like this main variant to continue publishing our pages but use a >>>> second target to publish all the images, scripts - is this possible to set >>>> up? I can't find an easy way to separate out the image folders from each >>>> publishing package as they seem tied to the default project variant? >>>> >>>> Any help would be greatly appreciated! >>>> >>>> Thanks >>>> >>>> Neil >>>> >>> > -- > You received this message because you are subscribed to a topic in the Google > Groups "RedDot CMS Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/reddot-cms-users/8sJgKDAVzzE/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/reddot-cms-users. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
