• @B0rax@feddit.de
    link
    fedilink
    English
    01 year 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
      11 year 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.

      • MaggiWuerze
        link
        fedilink
        English
        01 year 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
          link
          fedilink
          English
          11 year 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.

          • @chaospatterns@lemmy.world
            link
            fedilink
            English
            1
            edit-2
            1 year ago

            Paperless does support defining a folder structure that you can use to organize documents within that paperless media volume however you should treat it as read only.

            OP could use this as a way to keep their desired folder structure as much as possible, but it would have to be separate from the consumption folder.