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.
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.
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.
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.
Maybe I’m misunderstanding this, but their FAQ specifically says:
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.
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 changedata:/usr/src/paperless/datato/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.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.
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.
I do want to leave my current files alone.
Note: 8 months later and I invested the time into setting up Immich instead. Much better return on time investment.
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)