Comment on Keeping .yaml files up to date...

shnizmuffin@lemmy.inbutts.lol ⁨2⁩ ⁨days⁩ ago

• lka1988@lemmy.dbzer0.com ⁨2⁩ ⁨days⁩ 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 project that do not document YAML changes.

  source
• Nawor3565@lemmy.blahaj.zone ⁨2⁩ ⁨days⁩ 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

  source

  • shnizmuffin@lemmy.inbutts.lol ⁨2⁩ ⁨days⁩ 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.

    source

    • neonrain@piefed.social ⁨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.

      source
• neonrain@piefed.social ⁨2⁩ ⁨days⁩ ago

  Oh you must mean THE manual. Got it.

  source

  • shnizmuffin@lemmy.inbutts.lol ⁨2⁩ ⁨days⁩ ago

    You can also interpret it as, “Read their fucking manuals.”

    source