You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #807@tpng did the excellent thing of making all reloads, even graceful ones, happen within the same process. It deleted a lot of code and made Caddy much better.
However, now it is impossible, I think, to upgrade the Caddy binary gracefully. Where before a new caddy process would be executed, thus allowing the sysadmin to replace the old caddy binary with a new one, now that no longer happens. So you have to stop and restart the process to upgrade the server.
I propose we introduce the USR2 signal for graceful upgrades. This essentially restarts the process gracefully like we did before, except that we do not load a new Caddyfile; instead we pass in the current Caddyfile via gob.
Let's not begin work on this until I push my 0.9 progress.
The text was updated successfully, but these errors were encountered:
In #807 @tpng did the excellent thing of making all reloads, even graceful ones, happen within the same process. It deleted a lot of code and made Caddy much better.
However, now it is impossible, I think, to upgrade the Caddy binary gracefully. Where before a new
caddy
process would be executed, thus allowing the sysadmin to replace the old caddy binary with a new one, now that no longer happens. So you have to stop and restart the process to upgrade the server.I propose we introduce the USR2 signal for graceful upgrades. This essentially restarts the process gracefully like we did before, except that we do not load a new Caddyfile; instead we pass in the current Caddyfile via gob.
Let's not begin work on this until I push my 0.9 progress.
The text was updated successfully, but these errors were encountered: