4 ms·
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
by withinboredom 3y ago
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.
- jraph 3y agoYou 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.
- withinboredom 3y agoThat 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.
- jraph 3y agoOf 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.