[FEAT] Access files for reading or editing in a sibling webdav container

[mod0]

Is this a new feature request?

• I have searched the existing issues

Wanted change

I was wondering if it is possible to access files for editing in a sibling webdav container that is connected to the same custom bridge network?

Reason for change

This will allow for instance to run a setup where in one container we could be running libreoffice and in another nextcloud. Subsequently, we can edit the files in the nextcloud container via webdav from libreoffice provided they are connected to the same custom bridge.

Proposed code change

Not yet.

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[thelamer]

why not just mount the same data into the libreoffice container and edit them all you want in libreoffice, when you click save they will be updated across any containers that have that same bind mount of data no?

[mod0]

Two reasons I can think of given that access is through webdav:

1. ACL enforcement
2. Locking/Versioning

[thelamer]

I have never used webdav, but docs say you are just opening a file from a URL in libreoffice. Why would this not be possible?

[mod0]

Apologies for the delay. This is what I see if I try remote location:

These are the settings of the connection:

Both the containers are connected to the same custom bridge network on the same machine. My nextcloud instance is named nextcloud.

My nextcloud instance says I need to use this address:

[mod0]

I was wondering whether, because libreoffice is running on top of https://www.kasmweb.com/kasmvnc, if something needs to be done special for networking to work, atleast locally.

[thelamer]

Does this work on a normal install of LibreOffice? Their docs reference a process where you need to use the file dialouges to accept a cert and possibly enter auth information:
https://help.libreoffice.org/latest/en-US/text/shared/guide/digitalsign_receive.html

[mod0]

Thank you, you brought up a great point that I overlooked. I tried connecting from my local libreoffice, but to no avail. I was able to connect from cyberduck and nextcloud desktop client. So the connection string is all good.

I am at a point where I think the effort required to resolve this feature request effort is not worth in the long-term given there are other ways of "mounting" the webdav directory locally on each major OS.