News for hackers. Stuff that matters.
Re:Don't require people to change 'source code' to configure... by withinboredom on Tuesday April 09, 2024 @05:52AM (#39977811)
The downside of this is that if the author changes a configuration key, you configuration will probably be invalid (thus refusing to come back online), or worse, ignored and the warning buried in systemd logs.

At least if the maintainers version and your version require review, you have a fighting chance to update the configuration with your customizations, without downtime or unexpected behavior.

Re:Don't require people to change 'source code' to configure... by jraph on Tuesday April 09, 2024 @10:52AM (#39980084)
You can't rely on this stuff if you want to avoid downtime.

If you want to avoid downtimes, you need to read changelogs and plan upgrades, and maybe test the upgrades before upgrading the production, in any case.

Re:Don't require people to change 'source code' to configure... by withinboredom on Tuesday April 09, 2024 @11:14AM (#39980328)
That works for an enterprise or business. When you are doing this stuff for fun and/or hobby, being halted during the upgrade is a MUCH better UX than deleting all my data or whatever undefined thing might happen.
Re:Don't require people to change 'source code' to configure... by jraph on Wednesday April 10, 2024 @12:19AM (#39986917)
Of course, I'm not advocating for such adversarial behaviors like the upgrade process deleting your files.

But you have a point, and maybe a solution to this issue ought to be found.