Installing and running Collabora Online on Linux packages, Docker and restricted networks, putting it behind a reverse proxy, and choosing between the built-in CODE app and a dedicated server.
Moving from the collabora/code image to a supported production container: the subscription image, environment settings for allowed WOPI hosts and TLS, capabilities the container needs, and upgrades by image tag.
Installing coolwsd from Collabora's deb and rpm repositories on Ubuntu, Debian and RHEL-family servers: supported architectures, repository keys, coolwsd.xml and coolconfig, and service management.
Putting Nginx, Apache or HAProxy in front of coolwsd: the paths and WebSocket routes to forward, SSL termination at the proxy, subdomain layout, and timeouts for long editing sessions.
When the Built-in CODE Server app is enough and when to move to a dedicated Collabora Online server: user counts, AppImage and FUSE requirements, performance, support and the upgrade path.
Running Collabora Online with no internet access: mirroring packages or images, local fonts and dictionaries, disabling remote features, keeping signing keys current, and patching offline.
Getting document fidelity right with the fonts users expect: installing fonts into the systemplate, remote font configuration over HTTPS, corporate fonts, and checking rendering after updates.
Deploying Collabora Online on arm64 hardware and cloud instances: deb packages and the CODE image for arm64, the lack of arm64 rpm packages, and testing performance before rollout.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.