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.
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.
I don’t think Postgres shouldn’t be just left as
:latestor anything. At least the way I handle it, DB upgrades require manual intervention.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.
Well, crap
Thank you, yes, exactly what I meant. It’s a bit baffling such a mature project doesn’t have some kind of migration script. :(