this is a clusterfuck and I do not recommend using this
The only reason I did this was because I was annoyed by the Nextcloud AIO interface, but it is a bitch to maintain this because they make breaking changes upstream that you need to investigate later when it blows up
This is also pretty hacked together and the onlyoffice compose relies on the nextcloud compose to be up and running first. yes nextcloud has the onlyoffice container in the upstream compose but it didn't work for me, hence this nonsense
this also depends on an already running postgres container; nextcloud ignores the POSTGRES_USER variable and expects to logon to the database as oc_nextcloud
onlyoffice settings in nextcloud:
- onlyoffice docs address: URL as the user accesses it, e.g. cloud.meow.tld
- secret key: the JWT_SECRET variable as set in onlyoffice.yml line 20
- authorization header: leave blank for default
- onlyoffice address for internal requests: http://onlyoffice-documentserver/
- server address for internal requests: http://nextcloud-apache:41443/