I don’t think Postgres shouldn’t be just left as :latest or anything. At least the way I handle it, DB upgrades require manual intervention.
Comment on 💞 FairScan > Syncthing > Paperlees-ngx
MonkeMischief@lemmy.today 1 month ago
Heads up if your Paperless is installed via Docker: be VERY CAREFUL about your database version and do an export often!
Mine has been down for a while because I did a pull and it doesn’t support my version of Postgresql anymore. So it’s kinda a huge mess trying to figure out how to safely migrate it in the container.
I haven’t been able to fix it yet so I’ve just left it disabled and gone without for a while. It’s not fun.
Allegedly if you export from within Paperless, you can just start with a fresh updated database container and import when this happens. Oof.
aquovie@lemmy.cafe 1 month ago
avidamoeba@lemmy.ca 1 month ago
I just got burned by accidental latest tag on a pg container for Nextcloud. They moved some paths internally and it could no longer find the db.
Damage@feddit.it 1 month ago
your version of postgres meaning that you use a db external to the docker container?
prenatal_confusion@feddit.org 1 month ago
No sadly the upgrade path is a bit ducked. Their compose, their versions, still not working without intervention.
Damage@feddit.it 1 month ago
Well, crap
MonkeMischief@lemmy.today 1 month ago
Thank you, yes, exactly what I meant. It’s a bit baffling such a mature project doesn’t have some kind of migration script. :(
avidamoeba@lemmy.ca 1 month ago
This is a reminder for self-hosters to put their apps (and their data) on snapshotting filesystems with automatic, regular snapahots turned on; and fix the app versions to at least the major version, across all containers.