mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 19:01:54 +00:00
kevinveenbirkenbachandClaude Opus 5.5
8834cc124a
COLLABORA_WOPI_HOST read the scheme and the port with
lookup('tls', 'web-app-nextcloud', ...) and the host with
lookup('domain', 'web-app-nextcloud'). The tls lookup aligns an app term
to its consumer: for a clearnet Collabora it answers for the clearnet
sibling of an onion-primary Nextcloud, while the domain lookup keeps the
onion name. Such a deployment renders https://<onion>:443, an origin
Nextcloud does not use, so the allowlist does not match its WOPI calls.
Nextcloud pins overwritehost and overwriteprotocol to its primary domain,
so the allowlist now asks the tls lookup for that domain instead of for
the app.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
12 lines
588 B
YAML
12 lines
588 B
YAML
---
|
|
application_id: web-svc-collabora
|
|
entity_name: "{{ application_id | get_entity_name }}"
|
|
|
|
domain: "{{ lookup('domain',application_id) }}"
|
|
http_port: "{{ lookup('config', application_id, 'services.collabora.ports.local.http') }}"
|
|
|
|
COLLABORA_CONTAINER: "{{ lookup('config', application_id, 'services.collabora.name') }}"
|
|
COLLABORA_WOPI_HOST: "{{ lookup('tls', lookup('domain', 'web-app-nextcloud'), 'protocols.web') }}://{{ lookup('domain', 'web-app-nextcloud') }}:{{ lookup('tls', lookup('domain',
|
|
'web-app-nextcloud'), 'ports.web') }}"
|
|
COLLABORA_DISCOVERY_PATH: "/hosting/discovery"
|