this post was submitted on 06 Feb 2026
170 points (98.9% liked)

Selfhosted

56107 readers
649 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

It's perfect! Do you guys already do this?

I open a letter, I take it's picture with FairScan. The FairScan-folder on my android device gets syncthinged to the ingest folder for Paperless-ngx on my "server". Paperless imports it, deletes the file and sets the new documents tag to inbox. I decide if the document goes to the binder for important stuff, or if I just toss it in a binder with all the paper I most likely will never touch again. Next time I look at Paperless, I edit all documents with the inbox tag and remove the tag.

you are viewing a single comment's thread
view the rest of the comments
[–] MonkeMischief@lemmy.today 8 points 1 day ago (3 children)

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.

[–] avidamoeba@lemmy.ca 6 points 1 day ago* (last edited 1 day 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. This should bring similar disruption to bare minimum and makes recovery always possible, without relying on specific app backup features.

[–] aquovie@lemmy.cafe 4 points 1 day ago (1 children)

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.

[–] avidamoeba@lemmy.ca 1 points 1 day 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 2 points 1 day ago (1 children)

your version of postgres meaning that you use a db external to the docker container?

[–] prenatal_confusion@feddit.org 3 points 1 day ago (2 children)

No sadly the upgrade path is a bit ducked. Their compose, their versions, still not working without intervention.

[–] MonkeMischief@lemmy.today 2 points 1 day 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. :(

[–] Damage@feddit.it 2 points 1 day ago