Paperless-ngx v3 Preparation

[tomfrenzel]

📌 Task summary

Paperless-ngx v3 Preparation

📋 Task details

Paperless v3 will have some breaking changes. This task is here for discussing/keeping track the necessary changes in the scripts.
So far, the following things need to be done in the scripts:

paperless-ngx-install.sh

• Remove now obsolete packages
• Update env vars

paperless-ngx.sh

• Ensure current version is at least v2.20.15 before updating to v3
• Remove now obsolete packages
• Update env vars
• Optional: remove uv migration section

I already did some testing with updating my current v2.20.15 installation to the v3. So far it seems like everything has worked as expected. But i need to implement the logic for the "intermediate" update to v2.20.14 twice since with the current script, it would have the work for pre uv installations as well.
How about we get rid of the uv migration part inside the script and move it to a GitHub discussion? Alternatively, we could pin the paperless release to v2.20.14 for the uv migration part and print a message that for the v3 update the user needs to re-run the update script.

[tomfrenzel]

How about we get rid of the uv migration part inside the script and move it to a GitHub discussion? Alternatively, we could pin the paperless release to v2.20.14 for the uv migration part and print a message that for the v3 update the user needs to re-run the update script.

@MickLesk / @vhsdream as i saw you guys made the majority of changes to the paperless scripts - what do you guys think about hat?

[MickLesk]

I took a look at it—are these really supposed to be just such minor changes? After all, it's just a small purge and a few tweaks to the .env file. (by the way apt-get --> apt )

[tomfrenzel]

There are ~15 more config changes that re needed. Some are new and some got repleaced so we need to map values (eg previously OCR_SKIP_ARCHIVE=never is now PAPERLESS_ARCHIVE_FILE_GENERATION=always). I'm still working on findig all entries. but i think i'm almost there.

Other than that there is just a small change to the paperless-webserver.service