There seems to be an issue with the newest dockerhub image though. I guess the postgres database was moved out of the image? Upgrading right now fails because of that. Edit: (re-)starting from scratch works though.
Nice. Just installed Documentserver 5.2. Running fine. One question though. When i open an existing .odt file with OnlyOffice it seems to be in read only mode. Did i hit a bug or did i make something wrong?
Thanks for the question. This has nothing to do with version 5.2, it is about the new connector
We made it possible to edit ODF (as well as TXT, CSV and RTF) with automatic conversion. You need to visit admin settings and select the needed check boxes next to the formats.
We have an article about that, if you are interested.
Looks like it is just an upgrade issue. if you completely recreate the docker container including deleting and recreating all linked named volumes it works here.
It is working well for us. Doing the upgrade was a bit rough though due to changes in configuration files I needed to reapply in new files. It took some time to figure out what I needed to fix.
I don’t have the exact files but apt this ask what to do with those files. The difficulty for me was that I had not documented all the changes so I had to go though all the files and compare. It was mostly nginx config and I had edited default.json.
A file local.json had appeared which was a head scratcher as it overwrites the settings in default.json. I took me some time to figure out this was the file to edit now.
I would recommend to pass the environment variables to your container using -e flag or --env-file.
All available configuration parameters are listed here.
Note that adding JWT_SECRET is not enough, do not forget to set JWT_ENABLED to true first.
All variables will be saved to the file /etc/onlyoffice/documentserver/local.json
(since 5.2 default.json is a read-only file)