I am new to caddy. I am trying to build a custom caddy binary and worried about its upgrade path.
Not applicable need guidance
- Installed caddy via debian bookworm repository
- Followed instructions Build from source — Caddy Documentation to setup caddy.custom
- I have put caddy.custom using xcaddy command as listed below
xcaddy build \ --with github.com/caddy-dns/route53 \ --with github.com/greenpau/caddy-security \ --with github.com/greenpau/caddy-git \ --with github.com/caddyserver/replace-response
direct deployment via systemd using official package
Standard compose file
However now i am concerned about a few things. since i have taken over the binary as i needed these custom plugins. How do i ensure i am not missing on upgrades.
there are lots of thread and all of them confusing. so making another thread to hopefully get some good answers or add more to the confusion.
Here is what i am thinking and need suggestions if i am doing right.
Idea 1: since this is custom build, i can simply do
caddy upgrade command as a daily cron and if it builds binary successfull, restart caddy
Idea 2: setup a monitoring script for releases on all my plugins and caddy itself and if anyone does an upgrade i should build it automatically.
Idea 3: Be less paranoid and wait for specific security bugs and then only upgrade otherwise let it be.
Do suggest if anyone has tried any of these approaches or something else. effectively how do you keep caddy up to date. or do you even worry about it.