Jeef

What about the `OFFICE_REWRITE_URL` is that needed?

Do you have a working version? (docker compose) I have files.subdomain.net and office.subdomain.net working - yet I still get  When I try to open an office file

It seems my office container is reporting: 

Are you publishing docker images or do I need to build my own with your fork?

> - "extra_params=--o:ssl.enable=false --o:ssl.termination=true" > - aliasgroup1='https://files.DOMAIN.XYZ That was different on mine I'm using caddy internally as with a wildcard cert - and overrides in unbound within the lan.

I'm hoping somebody can figure it out soon-ish :)

@Finomnis - you should make a PR :) easy way to contribute if you are updating docs

Are the `xe` drivers something attached to a kernel release - or we have to just wait on them to be written and they can be back-fit into an existing...

This one? That makes no sense to me...

I'm seeing the same issue - (verified with the CLI). ```yaml signal-api: image: bbernhard/signal-cli-rest-api container_name: signal-api environment: - PUID=${PUID} - PGID=${PGID} - TZ=${TZ} - 'MODE=native' ports: - ${SignalAPIPort}:8080 volumes: -...