Thanks, it was a copy/paste error…I corrected my post
1 Like
Thank you for the feature @mrmarkuz !
For anyone trying to modify the local.json file:
Since this setup uses the official Docker image, the local.json file is regenerated each time the container starts, meaning it’s not directly mappable or persistent on the host. Any manual changes made to local.json inside the container are lost after a restart.
The proper workaround is to create a local-production-linux.json file in the onlyoffice-etc/_data directory. This file takes precedence over the default configuration and remains persistent across container restarts. Any changes made there are applied automatically on startup. This is the recommended way by OnlyOffice mods. See: https://forum.onlyoffice.com/t/docker-relation-between-default-json-and-local-json/2232/6
1 Like
The new Onlyoffice release 9.0.2 fixes some bugs, see DocumentServer/CHANGELOG.md at master · ONLYOFFICE/DocumentServer · GitHub
I hope this is the last testing version before release.
Fresh installation:
add-module ghcr.io/mrmarkuz/onlyoffice:1.0.7-dev.3
Upgrade: (adapt onlyoffice1 to the name of your onlyoffice instance)
api-cli run update-module --data '{"module_url":"ghcr.io/mrmarkuz/onlyoffice:1.0.7-dev.3","instances":["onlyoffice1"],"force":true}'
Go back to Onlyoffice 8 (1.0.6) if something went wrong:
api-cli run update-module --data '{"module_url":"ghcr.io/mrmarkuz/onlyoffice:1.0.6","instances":["onlyoffice1"],"force":true}'
1 Like
I think you can release it
I have tested it extensively and found no problems.
The corresponding system log looks clear here.
1 Like
Thank you for testing again! I’m going to release it…
1 Like
Released.
Thanks guys for your feedback, testing, feature requests and the customizing documentation which I just copy/pasted to the updated README: ns8-onlyoffice/README.md at main · mrmarkuz/ns8-onlyoffice · GitHub
1 Like