neonrain
@neonrain@piefed.social
wait, what?
- Comment on Keeping .yaml files up to date... 2 days ago:
Hmmm I’ve heard of it but haven’t tried it. I’ll dip my toe, thanks!
- Comment on Keeping .yaml files up to date... 2 days ago:
This seems really interesting. I’ll have to read up on it more and try to wrap my head around it but I’m definitely checking this out. Thank you!!
- Comment on Keeping .yaml files up to date... 2 days ago:
Ah ok cool I’ll check that out. Thanks!!
- Comment on Keeping .yaml files up to date... 2 days 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.
- Comment on Keeping .yaml files up to date... 2 days ago:
Oh you must mean THE manual. Got it.
- Comment on Keeping .yaml files up to date... 2 days ago:
That’s kind of what I’ve found but wasn’t sure if I was just missing something. Thanks!
- Comment on Keeping .yaml files up to date... 2 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.
- Submitted 2 days ago to selfhosted@lemmy.world | 32 comments