Mirror Synchronization With Delete Option?

[ritland]

Hey Guys,

I work with a lot of temporary files. Right now, I have my Yummy FTP mirror synchronize my Mac with my server. I use the files on my Mac, then delete them from my Mac. Is there anyway to have the files deleted off the server once they are deleted off my Mac during the next mirror synchronization? Right now, a file that is deleted form my Mac will just be redownload during the next mirror synchronization. Maybe there is a scripting solution for this?

Thanks guys.

[JD]

No, I can't think of any way to do this automatically.

The only built-in way to get items deleted during a sync is a one way sync, and you're using the two way Mirror option. Even if you changed to using two separate syncs - download, do your work, then upload with 'delete' orphans - I don't think it would be a solution because there would be (I guess) newer 'temp' items on the server that you'd want to keep and there would be no way to know which to keep or delete.

Even a script isn't going to be a possibility, as far as I can tell from your description, because there is no way to know which items to delete.

Maybe if you provided more detail about the work flow... 'temporary files' is a little vague

[ritland]

Sure. My server produces .avi render files throughout the day of varying sizes. I do not use the files in any chronological order, meaning i sometimes will use the most recent first and then use older ones. As a result, there is no one particular attribute that I an use to exclude the files from mirror synchronization. The functionality I was looking for is something like Dropbox (https://www.dropbox.com/) which will automatically sync two directories and any changes on either side (the deletion of a file for instance) will be mirrored on the other.


If there isn't  a way to automatically delete the files from the server after I have deleted them from my Mac, is there any to prevent the deleted files from being redownloaded during the next mirror synchronization?

Thanks.

[JD]

The way DropBox works is that it is running on each place there is a copy of the data. So it 'knows' immediately when a file is changed or deleted (or whatever) and broadcasts that change to all the other DropBoxes running. Unfortunately this isn't the case with Yummy, so it's not possible to replicate that functionality.

For the delete on server problem, again, it's impossible. How can Yummy know which files to delete and which to keep? I'm thinking along the lines of the 'delete orphans' option and an Update Server, but there could be a mixture of new render files and ones you already processed, and no way to distinguish one from another.

[ritland]

Ok. Thanks for your help. I guess the only way it could be done is by keeping some sort of log that the FTP client would check against to look for past activity.

Thanks again.