mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-08-22 12:53:32 +02:00
6a27361cef
Reported in #2768: several users could not get Collabora to talk to Nextcloud, and the two options meant to configure it had no effect. - 99-run.sh read a `domain` option that does not exist in the schema (the option is `domain1`), and recent Collabora releases dropped the `domain` environment variable entirely, so `domain1` was inert. It now maps to `server_name` with a deprecation warning. - `server_name` and `cert_domain` were in the schema but never passed to Collabora. `server_name` is what fixes "Your browser has been unable to connect to the Collabora server" behind a reverse proxy. - `aliasgroup*` entries are matched by Collabora as regular expressions, so a dot needs a single backslash. The README asked for two, which can never match a real hostname. Values are now normalised (unescaped, escaped and double-escaped all give the same correct pattern) and logged at startup. Values containing other regex metacharacters are left untouched. - Added `ssl_termination`, needed when `ssl` is false but Collabora is reached over https through a reverse proxy, and `aliasgroup2`/`aliasgroup3`. - `cert_domain` is a certificate common name, so it is a string, not a bool. - Releases on CollaboraOnline/online are now Helm charts only, which had renumbered the addon from 25.4.9.2 down to 1.3.0 and hid updates from the Supervisor. Version tracking moves back to the collabora/code Docker Hub tags. Co-Authored-By: Claude <noreply@anthropic.com>
10 lines
231 B
JSON
10 lines
231 B
JSON
{
|
|
"github_exclude": "sha256",
|
|
"last_update": "2026-07-26",
|
|
"repository": "alexbelgium/hassio-addons",
|
|
"slug": "collabora",
|
|
"source": "dockerhub",
|
|
"upstream_repo": "collabora/code",
|
|
"upstream_version": "26.04.2.4.1"
|
|
}
|