Preventing Citydesk updating destination files.
I would like citydesk to only update destination files that have an older timestamp compared to the source CD files(rather than files which have changed). Does anyone know whether it's possible to do this?? (perhaps modifying the cityesk.xml file produced in the destination directory?)
I don't understand what function you are trying to accomplish by keying on dates rather than content.
I am not sure how the update policy of citydesk works. Does it use the filestamps or does it trust the contents of the xml file?
Adriaan van den Brand
As I understand it, when CityDesk publishes, it creates a checksum for each file and compares that to the values in the citydesk.xml file. If it finds a difference it copies the file. If it finds that the file isn't in the xml file, it copies it. And if it's in the xml file but not in the to-publish site, then it deletes it from the server.
You might take a look at the rdist and rsync utilities. They might do what you want; They might not. Search through google.com for documentation.
You can also look at my RTidy utility (at http://www.halostatue.ca). Tidy does the transformation in-place and then uploads the files on the basis of the citydesk.xml and that only.
Thanks for the replies. It's a shame that CD doesn't have an 'Only update if destination files are older' option on the publishing menu :-(
Fog Creek Home