38
Keeping .yaml files up to date... (piefed.social)
submitted 11 months ago by to c/selfhosted@lemmy.world
32 comments fedilink hide all child comments
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] 16 points 11 months ago (2 children)

I cannot recall a single self-hosted software documentation that mentions how to keep the docker config file up to date. Why bother wasting 5 seconds writing such an unhelpful comment

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [+] -10 points 11 months ago (1 child)

    Tell me you don't read the manual without saying you don't read the manual.

    I can recall a few! Mastodon. Lemmy. PiHole. Penpot. Mealie. Uptime Kuma.

    They all mention required steps to upgrade between releases, including what to do to your docker installations and environment variables.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 2 points 11 months ago

    PLENTY of projects make tiny non-breaking changes to the compose files without any mention that users should update the file. For example, adding a section for a container health check. While these can be no big deal for a while over time they can add up to major changes in the config that users may not catch if they are not comparing yml files.

  • permalink
  • fedilink
  • source
  • parent