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 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.
