2
Keeping .yaml files up to date... (piefed.social)
submitted 2 months ago by neonrain@piefed.social to c/selfhosted@lemmy.world
9 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!

top 9 comments
sorted by: hot top controversial new old
[-] IanTwenty@piefed.social 1 points 2 months ago

This is new:

https://github.com/dkorecko/PatchPanda

Self-hostable Docker Compose stack update manager.

And

when you choose to update, PatchPanda edits compose/.env files and runs docker compose pull and docker compose up -d for the target stack. You can also view live log.

Discovered in the latest Self Host Weekly:

https://selfh.st/weekly/2025-11-28/

I have not tried it myself tho.

[-] neonrain@piefed.social 1 points 2 months ago

Hmmm I've heard of it but haven't tried it. I'll dip my toe, thanks!

[-] Mora@pawb.social 1 points 2 months ago

I deploy and update my service similiar to this fantastic guide: https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

Basically I run Komodo, which pulls a git repo. Renovate opens a PR (and most of the time the changelog is included, so I can quickly check what happened) for new versions. Once merged a webhook fires to tell Komodo to pull the new version.

I really recommend this approach now. Once setup it is very automatic, but not to the point of YOLO-automation like Watchtower and :latest 😅

[-] nfreak@lemmy.ml 1 points 2 months ago

I set this up a while back (and recently moved to Forgejo, see the update note at the beginning of the article):

https://nickcunningh.am/blog/how-to-automate-version-updates-for-your-self-hosted-docker-containers-with-gitea-renovate-and-komodo

Probably a tad overkill honestly but it works amazingly well, and turns every potential upgrade into an approval process so nothing will update when you don't want it to.

[-] shnizmuffin@lemmy.inbutts.lol -1 points 2 months ago

RTFM

[-] Nawor3565@lemmy.blahaj.zone 2 points 2 months ago

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

[-] shnizmuffin@lemmy.inbutts.lol 0 points 2 months ago

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.

[-] neonrain@piefed.social 1 points 2 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.

[-] lka1988@lemmy.dbzer0.com 1 points 2 months ago* (last edited 2 months ago)

This is the kind of attitude that drives people away from open source.

Yes, people should read the manual, but at some point they will have questions, and there are a lot of projects that aren't clear on certain things. Such as YAML changes.

this post was submitted on 28 Nov 2025
2 points (100.0% liked)

Selfhosted

56359 readers
122 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.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

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