Closed priyadarshan closed 1 month ago
This table, from an OwnCloud's ticket, may clarify a bit: WebDAV permission attributes for desktop client
The implementation could go two ways:
permissions: CRU
for "Create", "Read", "Update". This could also replace the modify
and allow
in the rules, since all the permissions could be condensed to a single parameter.We'd also need to figure out the disctinction between "Create" and "Update" since they creating and updating files uses the same verb PUT
. I could in this case check if the file already exists.
Is copy/move update or create? Depends on the destintion.
Hello,
I have just found out about Caddy-webdav, and I am enthusiastic about it. We already have it running on some servers with excellent results.
Right now permissions can be set to access and/or change a resource.
I was wondering if it could be possible to add independent permissions? Like:
Currently we do use combinations of those permissions on some webdav shares, through NextCloud (see screenshot).
We do not need all the infrastructure NextCloud offers, and the additional complex toolchain that imposes.
It would be fantastic if Caddy-webdav could completely replace NextCloud's role as webdav server .
Thank you for making Caddy-webdav available, it is a wonderful addition to Caddy.