I found that in the end, the best thing to do was to have nearly all rules running on my desktop. (If you change the rule such that Hazel triggers when the file is modified, it will keep noticing the filename has changed, add another date to the filename, which when it syncs to the other computer will cause another modification trigger… and so on.) Then the file would get sync’d to the other compute where Hazel would add another creation date string onto that filename, so every file wound up with two dates in its name. The problem was that I would create the file on one computer, and Hazel would change the filename for me. Here is an example: I had a Hazel rule that would notice any new file added and append the file creation date to the beginning of the filename. I ran into some issues with having the same rules on multiple computers, however. I think you are probably correct that the reason that things have been working for you is that Hazel is handling things faster than the iCloud sync. I’m sure I’m not the first to ponder this question-what have others done/preferred? But what I’m really wondering is if this is the proper way to keep my workflows the same? Or should I be deeming one of the computers the master and having it run Hazel rules etc, then let iCloud sync the results? I haven’t seen any issues with Hazel on two computers essentially looking at the same folders. Mostly, I think it works because Hazel is faster than iCloud sync and hence processes the files before iCloud has a chance to sync them. As I conduct my workflow, no matter which Mac I’m on, everything works as expected with Hazel noticing files and doing the things I want. I have Hazel installed on both and the rules sync between the two. All files sync via iCloud and I have not experienced any trouble with it. They are set up virtually identical since I work from home at times. I have an iMac at work, and a Mac mini at home. I have three macs-two that are primary, and one laptop that I don’t use as often.
0 Comments
Leave a Reply. |