Repository navigation
|
Hello. Is anyone else here trying a similar combination as described in the title? Remote worker, using Mountain Duck, opening files stored on a macOS file server. Lock file showing locally but not showing to other users in the office on smb shares. Clear as mud? Would love for this to work. Anybody have any solutions as to what I might look for? Server macOS 10.12. Built in File Sharing. ACLs done up with chmod commands. Remote user on macOS 26 with mountain duck SFTP-ing in. Thanks in advance! -g |
Replies: 1 comment 1 reply
|
This is expected with the current setup:
Mountain Duck has no UI setting to change this, so without allowing Mountain Duck to upload the lock file through the previously mentioned hidden property, Affinity's lock on your Mac and the other users' locks over SMB are completely separate. To be safe, agree with the other users on who works on which file. |
This is expected with the current setup:
Mountain Duck, by default, never uploads Affinity's lock file. As far as I know, Affinity's lock files end in
~lock~(for example,MyDesign.afdesign~lock~). Mountain Duck treats files ending in~as application temp files: it keeps them in a local buffer and never uploads them to the server. So the lock file shows up on your Mac, but it never reaches the file server, and other users on SMB never see it.You could adjust the excluded files list to allow
~lock~files for uploads by adding the hidden property below into the default.properties file. You can find instructions on how to add and use hidden properties on our wiki page.