[Feature] Option to Disallow Deletion in External Libraries #18502
Closed
wzyboy
started this conversation in
Feature Request
Replies: 1 comment
-
readonly is the recommended way, with the caveats you note. We don't want to have any special cases for external libraries as they caused a bunch of maintainability issues in the past. If you really want a middle way you could look at using an overlayfs or such to still allow xmp writes. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have searched the existing feature requests, both open and closed, to make sure this is not a duplicate request.
The feature
From the FAQ:
Request:
Could we introduce a setting or flag for external libraries that prevents deletion of original files?
Use Case:
DCIM
directory structure for incremental sync)Current Workaround:
I initially mounted the directory in Docker with the
ro
(read-only) flag to prevent deletions. However, this breaks sidecar generation: when trying to add locations to assets, the web UI shows no error, but the server logs reveal that writing the.xmp
file fails due to the read-only filesystem.Proposed Solution:
By introducing a "disallow deletion" flag for external libraries:
rw
(read-write), enabling.xmp
sidecar files to be written as intended.This would allow safe collaboration within families or shared environments without compromising metadata functionality or risking deletion of irreplaceable content.
Platform
Beta Was this translation helpful? Give feedback.
All reactions