• Daniel Quinn@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    8 months ago

    Ha! I wrote it! Well the original anyway. It’s been forked a few times since I stepped away.

    So yeah, I think it’s pretty cool 😆

      • Daniel Quinn@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        Actually, I stepped away from the project 'cause I stopped using it altogether. I started the project to satisfy the British government with their ridiculous requirements for proof of my relationship with my wife so I could live here. Once I was settled though and didn’t need to be able to bring up flight itineraries from 5 years ago, it stopped being something I needed.

        Well that, and lemme tell you, maintaining a popular Free software project is HARD. Everyone has an idea of where stuff should go, but most of the contributions come in piecemeal, so you’re left mostly acting as the one trying to wrangle different styles and architectures into something cohesive… while you’re also holding down a day job. It was stressful to say the least, and with a kid on the way, something had to give.

        But every once in a while I consider installing paperless-ngx just to see how it’s come along, and how much has changed. I’m absolutely delighted that it’s been running and growing in my absence, and from the screenshots alone, I see that a lot of the ideas people had when I was helming made it in in the end.

  • AtariDump@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    8 months ago

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

    • B0rax@feddit.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      8 months ago

      Well you point the docker to some external data. You do never store the documents inside the docker. (Because it would get lost when it is updated)

      It is comparable to the way Immich works.

      • Antiochus@lemmy.one
        link
        fedilink
        English
        arrow-up
        0
        ·
        8 months ago

        Maybe I’m misunderstanding this, but their FAQ specifically says:

        By default, your documents are stored inside the docker volume paperless_media. Docker manages this volume automatically for you.

        It also says that documents are removed from the consumption directory, renamed, and put into a folder that you shouldn’t modify.

        And that’s my problem with the project. I want to be able to keep my file name and organizational structure.

        • B0rax@feddit.de
          link
          fedilink
          English
          arrow-up
          0
          ·
          8 months ago

          It’s a docker volume. In this case it is managed by docker, but it is outside the container.

          To have it save everything on your normal filesystem, it should be possible to just edit the docker compose file (I have not tried that)

        • MaggiWuerze@feddit.de
          link
          fedilink
          English
          arrow-up
          0
          ·
          8 months ago

          Have a look here: [https://github.com/paperless-ngx/paperless-ngx/blob/main/docker/compose/docker-compose.postgres.yml](paperless-ngx docker-compose.yml)

          down under webserver: you change data:/usr/src/paperless/data to /path/to/where/you/wantorhave/your/files:/usr/src/paperless/data. Same for the media path and you’re done. paperless now uses a folder on your machine instead of a volume. If you want to be clean you will then also remove the volume declaration at the bottom of the file.

          • lemmyvore@feddit.nl
            link
            fedilink
            English
            arrow-up
            0
            ·
            8 months ago

            i think OP wants it to leave their current files alone. But Paperless doesn’t work like that, it deletes the originals and arranges the files its own way.

    • PlutoniumAcid@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      8 months ago

      Brother ADS-1700W is amazing!

      • no PC or USB required: place it anywhere
      • WiFi
      • scans a page double-sided to PDF in two seconds!
      • sends file to network share, ready to be consumed by Paperless
      • fully automatic, no button presses needed!
      • tiny footprint
      • document feeder
      • use with separator pages to bulk-scan many documents in one go

      😍

  • KairuByte@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    0
    ·
    8 months ago

    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.

        • HKlino@feddit.deB
          link
          fedilink
          English
          arrow-up
          0
          ·
          7 months ago

          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.