GitHub - paperless-ngx/paperless-ngx: A community-supported supercharged version of paperless: scan, index and archive all your physical documents
github.com
external-link
A community-supported supercharged version of paperless: scan, index and archive all your physical documents - paperless-ngx/paperless-ngx
@AtariDump@lemmy.world
link
fedilink
English
5
edit-2
7M

Tried to use it, but I don’t want to move all of my data from my currently laid out folder/file structure into a docker container that I then need to backup/upgrade/feed/water/etc., especially when my grasp on docker containers is limited (at best) and I’m dealing with “production” data.

I wish the software worked like Immach; I could point it at a root folder and it would index everything with read only rights.

That, and I’m slightly worried that this iteration will stop being supported and it gets forked (again) which is great that it can be forked but I have no idea what would go into migrating data (see my limited docker knowledge from the first sentence).

Eager Eagle
link
fedilink
English
1
edit-2
7M

Bind mounts. Always use bind mounts for data you care about, otherwise the “managed by docker” volumes are fated to be forgotten.

It won’t be your file structure as the file tree is managed by paperless, but at least using bind mounts you can easily navigate files and back them up independently or docker and paperless.

@AtariDump@lemmy.world
link
fedilink
English
1
edit-2
7M

No idea what a bind mount is.

Is that supposed to be a line in the compose file?

Eager Eagle
link
fedilink
English
1
edit-2
7M

yes, a bind mount / bind volume is when a volume is explicitly mapped to a location in your local storage rather than managed by docker and likely owned by root.

https://docs.docker.com/compose/compose-file/compose-file-v3/#volumes

@AtariDump@lemmy.world
link
fedilink
English
17M

Ok.

That’s over my head. I barely have a grasp on docker. And even then I’m paranoid that I’m screwing something up.

Create a post

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!

  • 1 user online
  • 31 users / day
  • 84 users / week
  • 216 users / month
  • 846 users / 6 months
  • 1 subscriber
  • 1.42K Posts
  • 8.09K Comments
  • Modlog