this post was submitted on 26 Jul 2025
26 points (100.0% liked)

Selfhosted

49847 readers
804 users here now

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!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
26
Upgrading Paperless-ngx several revisions behind (lemmy.world)
submitted 19 hours ago by haulyard@lemmy.world to c/selfhosted@lemmy.world
11 comments fedilink hide all child comments
 

Hey everyone. For a variety of reasons I’ve ended up with a paperless-ngx install that has not been upgraded for a while. It’s currently on 1.17.1, and I’ve been researching to figure out the best way to get back up to current. I’m worried about major changes that have happened over time and what the best way to go about this is, but I’ve not had good luck finding something that gives me the confidence to go about it. Hoping someone here has some guidance. Cheers!

you are viewing a single comment's thread
view the rest of the comments
[–] CocaineShrimp@sh.itjust.works 6 points 19 hours ago (2 children)

I haven't gone through your specific case, but generally what I do when doing a major update with potentially breaking changes:

  • Read the upgrade guides, if they have them. Some devs will put them out if they know their users will encounter issues when upgrading. If they don't have an upgrade guide, there might be some in the change logs. Going from 1.17.1 to (assuming) 2.x.y, check the change logs at 2.0.0.
  • Backup everything. I'd recommend doing this on a regular basis anyway.
  • (If you're running it in a docker container) Setup a second instance, restore the backup, then run the upgrade. You'll be able to check to see if it breaks at all. If it works, you can just destroy the old one and use the new one
  • (if you're not running it in a container) with the backup, try upgrading. If it breaks, you should be able to uninstall & reinstall the old version, then restore the backup
[–] CocaineShrimp@sh.itjust.works 7 points 18 hours ago* (last edited 18 hours ago)

Looking through the docs n' stuff, this is what I found:

I wasn't able to find any additional instructions on how to update other than the expected generic steps (docker pull or pip install -r requirements.txt). So my guess at this point is that they have scripts built in to check the version and run upgrade scripts as needed

[–] darkan15@lemmy.world 2 points 17 hours ago

Yeah, these are pretty solid advice, would say that you should be safe with patch version updates, like from 1.17.1 to 1.17.4

Should be able to jump from 1.17.4 to 2.0.1 and from 2.0.1 to 2.1.3, etc. going straight to the last patch of the next version, but should go one by one minor version, paying close attention to those versions that have breaking changes in the release notes. And always backup and test before each version jump.