153
๐ FairScan > Syncthing > Paperlees-ngx
(feddit.org)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 06 Feb 2026
153 points (98.7% liked)
Selfhosted
56072 readers
743 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (donโt cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
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.
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. This should bring similar disruption to bare minimum and makes recovery always possible, without relying on specific app backup features.
your version of postgres meaning that you use a db external to the docker container?
No sadly the upgrade path is a bit ducked. Their compose, their versions, still not working without intervention.
Thank you, yes, exactly what I meant. It's a bit baffling such a mature project doesn't have some kind of migration script. :(
Well, crap