|
Hi, I have opencloud running on my home server using docker compose with the collabora integration enabled. My setup is behind my own reverse proxy and uses the three separate domains described in the documentation: opencloud: cloud.example.com Since I want to access my opencloud instance from the internet, all three domains are currently publicly reachable. However, I would like to understand which of these services actually need to be publicly accessible. It's clear that the opencloud domain must be publicly reachable for external users, but I am particularly wondering about the wopi domain and possibly the collabora domain. Would it be sufficient if one or both of these services were only reachable internally (e.g. via a local DNS server and a valid TLS certificate), while only the opencloud domain remains publicly accessible? Thanks in advance and sry if I overlook a similar question. |
Replies: 1 comment 1 reply
|
Good question. cloud.* is the web Client and all backend api endpoints -> needs to be publicly available There is a refactoring here opencloud-eu/opencloud-compose#314 to move the collaboration into the cloud.* namespace which would get rid of the wopiserver* domain. |
@2eez4you
Good question.
cloud.* is the web Client and all backend api endpoints -> needs to be publicly available
collabora.* is the weboffice which is loaded by your browser -> needs to be publicly available
wopiserver.* is the weboffice backend part which needs to be loaded by the WebOffice, in the euro-office case also from the browser, -> needs to be publicly available
There is a refactoring here opencloud-eu/opencloud-compose#314 to move the collaboration into the cloud.* namespace which would get rid of the wopiserver* domain.