For those of you that use docker, how do you make sure your docker-compose.yml (and possibly .env) files stay current with the project’s ongoing updates? I’m sure there’s an easier way than what I’m doing which is manually getting the latest ones and checking the diffs in vscodium. And I’m sure some git magic already takes care of this but I’ve been slow in learning git beyond the VERY basics. Thanks!

  • dbkblk@lemmy.worldEnglish
    29·
    21 days ago

    I don’t want to use automatic updates on self hosted projects but I subscribe on github / gitlab releases in my rss reader (FreshRSS) and update when I want to!

      • BlueBockser@programming.devEnglish
        1·
        19 days ago

        If you also use FreshRSS, you can configure filters to automatically mark new articles as read (e.g. intitle:'beta'). Since I only view unread articles, that effectively deletes them and I never have to see them!

    • keksbaecker@lemmy.worldEnglish
      2·
      20 days ago

      Thank you for this idea. I wasn’t aware, that you can subscribe to an rss feed for releases on gitlab/github.

      I think that I will follow your approach.

  • themachine@lemmy.worldEnglish
    17·
    20 days ago

    I don’t pay any mind to example compose files. My are all quite custom anyway. Only thing that matters is paying attention to changelogs and watching for breaking changes.

    • Appoxo@lemmy.dbzer0.comEnglish
      2·
      20 days ago

      Same here.
      Read deployment documentation, configure compose to my standards, deploy, update where necessary to align with the update (e.g. remove an environment variable.

      The editing is done on my PC, then I open WinSCP or ssh into it (depending on my mood and amount of changes) and then apply the changes

  • frongt@lemmy.zipEnglish
    13·
    21 days ago

    I have automatic updates through a watchtower fork, so I just leave it alone until it breaks, then I go to the project site to see what changed. This has happened maybe twice in the last couple years.

    • neonrain@piefed.socialOPEnglish
      2·
      21 days ago

      I use a watchtower fork as well to keep some containers updated but I’m curious how others keep on top of docker-compose.yml files that the project updates over time. As an example, I’ve been using a container for years and noticed today that on the github page they’ve added a section in the compose file for a health check. I never would’ve known that was added if I didn’t stumble upon it due to another issue.

    • Appoxo@lemmy.dbzer0.comEnglish
      1·
      20 days ago

      Hope you have backups.
      Broke my neck a few times (I currently am waiting out the jellyfin patches and stay on 10.10.7 (i think))

    • irmadlad@lemmy.worldEnglish
      2·
      20 days ago

      PatchPanda

      I too saw PatchPanda on selfh.st and it is on my watch list. The only thing holding me back is that it isn’t out of beta yet. So, I’m waiting on other selfhosters to plow that field before I deploy. It does look like it would solve a lot of problems tho.

  • [object Object]@sh.itjust.worksEnglish
    6·
    21 days ago

    Other than keeping an eye on their changelog or waiting until it breaks, I don’t think you can do anything about that. I do have automatic update, but the config rarely changes from my experience.

    • neonrain@piefed.socialOPEnglish
      1·
      21 days ago

      That’s kind of what I’ve found but wasn’t sure if I was just missing something. Thanks!

  • mesa@piefed.socialEnglish
    2·
    21 days ago

    Good projects will have docs associated with the docker/docker compose files.

    The way we do it is, any update to the .yaml files will have a corresponding .yaml.Dev associated with it. That way it won’t be overwritten when an update occurs as well as give a recommended setup.