YunoHost-Apps / collabora_ynh

Collabora package for YunoHost
https://www.collaboraoffice.com/
GNU General Public License v3.0
16 stars 13 forks source link

One collabora for multiple Nextcloud #83

Open nathanael-h opened 10 months ago

nathanael-h commented 10 months ago

Feature request

I'd like to have one collabora instance used by multiple nextcloud instances

Would it be possible?

I saw here: https://github.com/YunoHost-Apps/collabora_ynh/blob/643295fc6e309e1c7fd03870dd93a942c2cf3385/conf/coolwsd.xml#L186 that the nextcloud URL given at install step is used here. I assume that we could ask for multiple (1 or more) nextcloud URL and loop on this list to add one line per URL? What do you think of that? Would it be easy to add to install and upgrade scripts? Maybe config panel would be more suitable to handle this (add or remove one URL)

JFossey commented 10 months ago

I had this exact thing working until very recently and there are no good examples in the documentation and I find the documentation almost completely unreadable. See below.

image

Ref: https://sdk.collaboraonline.com/docs/installation/CODE_Docker_image.html

A simple docker compose example in the docs would go a long way to preventing issues like this.

PS. I wonder if this issues is posted on the wrong repo.

rodinux commented 5 months ago

For multiple host the configuration should be different... something like this, well with docker... I am not sure it works with the install Yunohost ???

        <filesystem allow="false" />
        <wopi desc="Allow/deny wopi storage." allow="true">
            <max_file_size desc="Maximum document size in bytes to load. 0 for unlimited." type="uint">0</max_file_size>
            <locking desc="Locking settings">
                <refresh desc="How frequently we should re-acquire a lock with the storage server, in seconds (default 15 mins) or 0 for no refresh" type="int" default="900">900</refresh>
            </locking>

            <alias_groups desc="default mode is 'first' it allows only the first host when groups are not defined. set mode to 'groups' and define group to allow multiple host and its aliases" mode="groups">
            <!-- If you need to use multiple wopi hosts, please change the mode to "groups" and
                    add the hosts below.  If one host is accessible under multiple ip addresses
                    or names, add them as aliases. -->
                <group>
                    <host desc="hostname to allow or deny." allow="true">https://{NEXTCLOUD_DOMAIN1}:443</host>
                    <!--<alias desc="regex pattern of aliasname">scheme://aliasname1:port</alias>
                    <alias desc="regex pattern of aliasname">scheme://aliasname2:port</alias> -->
                </group>
                 <group>
                    <host desc="hostname to allow or deny." allow="true">https://{NEXTCLOUD_DOMAIN2}:443</host>
                    <!--<alias desc="regex pattern of aliasname">scheme://aliasname1:port</alias>
                    <alias desc="regex pattern of aliasname">scheme://aliasname2:port</alias> -->
                </group>
            </alias_groups>

            <is_legacy_server desc="Set to true for legacy server that need deprecated headers." type="bool" default="false"></is_legacy_server>
        </wopi>