Where Does Collabora Online Store Its Config?
Collabora Online reads /etc/coolwsd/coolwsd.xml for domains, SSL, and logging. Docker mounts that file from the host.
Last updated
Collabora Online (CODE) centers on coolwsd.xml at /etc/coolwsd/coolwsd.xml: allowed WOPI hosts and alias groups, SSL key paths, logging, autosave intervals, and certificate stores. Package installs edit it in place and restart the coolwsd service. Layered config means CLI flags (--o:name=value) and env vars override file values without editing.
Docker setups mount the file (or its directory) from the host because the container has no editor and regenerates nothing. Copy the default out with docker cp first, then bind it back read-write. A missing mount produces the classic File not found fatal on startup. Documents never live here; Collabora edits files hosted elsewhere, so the XML plus env is the whole state.
Where Collabora Online stores this, by platform
/etc/coolwsd/coolwsd.xml (Docker mount)
WOPI hosts, SSL, logging, autosave. Mount from host (file or directory bind); copy defaults out with docker cp before first mount. CLI --o: flags and -e vars override file values.
Frequently asked questions
how do i migrate collabora online docker
Copy coolwsd.xml from the host mount to the new host and mount it at the same container path. Documents themselves live in Nextcloud/ownCloud, not in Collabora, so no document data travels. Restart coolwsd after edits.
can i configure collabora without mounting xml
Pass -e with alias groups and credentials instead. The image runs with --use-env-vars, so domain, username, password, and dictionaries arrive as environment. Mount the XML only when env cannot express a setting (custom SSL paths, logging).
Notice an outdated path? Let us know.