Exposing an existing directory

[mcsilver]

I want to allow access to an existing directory using webdav, but when I specify the path to that directory as the volume, webdav creates a new data directory in there, and that's where a webdav client can add/edit files. Is it possible to give webdav access to the directory that I specify so that clients can edit files that are already in there?

[chaomifan]

same issue

[marcovitali]

I want to allow access to an existing directory using webdav, but when I specify the path to that directory as the volume, webdav creates a new data directory in there, and that's where a webdav client can add/edit files. Is it possible to give webdav access to the directory that I specify so that clients can edit files that are already in there?

You can mount this

/path/to/folder:/var/lib/dav/data

instead of this

/path/to/folder:/var/lib/dav

[mcsilver]

Thank you for the suggestion @marcovitali. For WebDAV end-users, this will suffice. I am hoping to also alleviate both backend people and backend systems from having to content with the data directory, as I have existing directories that I want to expose via WebDAV.

[marcovitali]

Thank you for the suggestion @marcovitali. For WebDAV end-users, this will suffice. I am hoping to also alleviate both backend people and backend systems from having to content with the data directory, as I have existing directories that I want to expose via WebDAV.

I have an existing folder and no data folder. The data folder is inside the container, not in your file system.
I did not need to change anything in my file system, if that is your concern.

[mcsilver]

You're right, mounting as you suggested above does work! Thank you for pointing it out.