this post was submitted on 22 Feb 2024
162 points (98.8% liked)

Selfhosted

40296 readers
271 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.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] KairuByte@lemmy.dbzer0.com 4 points 9 months ago (2 children)

I currently have a love hate relationship with it, but that’s mostly because of issues outside of paperless. I had been uploading to my server automatically with Nextcloud, and processing the files with paperless as they came in. Next thing I know, all the files are gone and none of the documents are available in paperless any longer, just the OCR translations that… leave something to be desired sometimes.

I’ve scrapped the whole thing in the short term, and will likely try again in the long term. Just need to find the time.

[–] h0rnman@lemmy.world 4 points 9 months ago (1 children)

Sounds like maybe you ran it as a container and didn't mount the document archive externally then updated the container. That would have likely blown away the actual ingested documents but left the Metadata (including the OCR data) where it was, assuming the database was either its own container or mounted externally

[–] KairuByte@lemmy.dbzer0.com 1 points 9 months ago

Nah, the container had an external volume for storage. That’s one of the first things I checked.

[–] BCsven@lemmy.ca 1 points 9 months ago (1 children)
[–] KairuByte@lemmy.dbzer0.com 1 points 9 months ago (1 children)

I believe the server purged them for space? Not really sure tbh.

[–] HKlino@feddit.de 1 points 9 months ago (1 children)

I encountered such problem the moment when watchtower pulled the latest update, including postgres:16. After setting the docker compose file back to postgres:15.4 and updating the stack, all data reappeared.

[–] KairuByte@lemmy.dbzer0.com 1 points 9 months ago

This could have been it. At this point the data is fully lost though, as I killed the container completely.