Back in the day it was nice, apt get update && apt get upgrade and you were done.

But today every tool/service has it’s own way to being installed and updated:

  • docker:latest
  • docker:v1.2.3
  • custom script
  • git checkout v1.2.3
  • same but with custom migration commands afterwards
  • custom commands change from release to release
  • expect to do update as a specific user
  • update nginx config
  • update own default config and service has dependencies on the config changes
  • expect new versions of tools
  • etc.

I selfhost around 20 services like PieFed, Mastodon, PeerTube, Paperless-ngx, Immich, open-webui, Grafana, etc. And all of them have some dependencies which need to be updated too.

And nowadays you can’t really keep running on an older version especially when it’s internet facing.

So anyway, what are your strategies how to keep sanity while keeping all your self hosted services up to date?

  • iamthetot@piefed.caEnglish
    3·
    44 minutes ago

    cd appname && dockup && cd ..

    Dockup being an alias for docker compose pull && docker compose up -d

    Repeat for the few services I have.

    • ominous ocelot@leminal.spaceEnglish
      2·
      5 hours ago

      I don’t understand. docker compose up starts the container. When does the docker compose pull happen? Or is there an update directive in the compose file?

    • Jeena@piefed.jeena.netOPEnglish
      5·
      9 hours ago

      So everything is dockerized and points to :latest?

      What about the necessary changes to the docker compose files? What about changes necessary in nginx configs?

      I guess you also read each release notes manually?

      • iamthetot@piefed.caEnglish
        1·
        46 minutes ago

        Not running anything that I’ve had to alter compose files. Also never had change nginx configs. Maybe I’m just running particularly stable stuff.

        I usually read update notes yes, but I’d be lying if I said I was always thorough.