> an application should never be able to replace itself with "random code" to be... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		mholt on Jan 4, 2022 \| parent \| context \| favorite \| on: Upgrading Executable on the Fly > an application should never be able to replace itself with "random code" to be executed. To clarify: it doesn't, nor has it ever worked that way. You have to be the one to do that (or someone with privileges to write to that file on disk). Most production setups don't give Caddy that permission. And you have to trigger the upgrade too.

eliaspro on Jan 4, 2022 [–]

Ok, this explains a lot and also clearly shows I never used this feature :)

I always assumed it would be the Caddy process itself taking care of downloading the update & replacing the binary, before restarting it.

mholt on Jan 5, 2022 | [–]

Caddy 2 can do that at least, but it's something you have to command it to do. :)

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact