• JASN_DE@feddit.org
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      1
      ·
      10 days ago

      Which isn’t a great idea with all the breaking changes. I’d assume it gets better after v2, but still.

      • Fmstrat@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 days ago

        The 2.0 release resolves a large amount of technical debt and shifts the focus toward compatibility and easier upgrades.

      • LastYearsIrritant@sopuli.xyz
        link
        fedilink
        English
        arrow-up
        2
        ·
        10 days ago

        I automate my upgrades, but I also automate my backups, and monitoring.

        If an upgrade breaks something, my health monitor lets me know and I can roll back to the previous day.

      • saddlebag@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        6
        ·
        10 days ago

        I’ve been doing this in my kubernetes cluster since immich was less than v1.49.0 (that’s the earliest I can find but it’s been over 4 years).

        Your comment could have been more constructive: something like “this is really cool, just be sure you don’t auto merge PRs without reading the patch notes. Learn about the process before you roll this out to your mission critical systems!”

        This is a learning opportunity (possibly even for you). Show others how to do things well and the whole community can benefit.

    • nfreak@lemmy.ml
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 days ago

      I’ve been running this setup for a few months now and haven’t looked back. Works super well, and essentially acts as an approval process for letting a container update or not.

      The author also recently added a followup article to this one for using Forgejo instead, made migrating the setup super easy.