Updating OttoFMS - Any gotchas?

I need to get all of our OttoFMS instances updated (currently on 4.3.x) but I’m concerned about things like webhooks breaking due to API Keys not persisting through the upgrade process. Is this anything to be concerned about? Are there any key config files I can backup prior to updating incase I need to roll back?

This was only an issue going from version 3 to 4. API keys will persist between version 4.

OttoFMS follows semantic versioning, so if the first number is the same between versions that you are upgrading, there would be no breaking changes

@JamesG
done this each and every time on a few servers and no issues to report at all
If you want to, back up the db.sqlite in the OttoFMS/data folder and the rclone.conf in OttoFMS/config if it is there

2 Likes

Thanks John, I’ll factor this into our DR strategy.