Comment by jagged-chisel

Everyone went right for “downtime” - no, that’s not an issue. I would have expected a configuration change, which wouldn’t require a restart but might indeed result in downtime.

Or even a configuration change that some control system notices and does restart the service.

It’s the manual, hands-on connotation (maybe only in my mind) of telling someone a restart is involved. Automate this stuff - don’t want the code in the server all year? Fine, have a process rebuild and relaunch on a schedule that makes sense. Might have downtime, but definitely have less hands-on.