Correct rebuild timings in README with measured warm/cold numbers
This commit is contained in:
parent
49b180e797
commit
e3459aa72e
1 changed files with 5 additions and 3 deletions
|
|
@ -39,9 +39,11 @@ uvicorn main:app --reload
|
||||||
## Deployment
|
## Deployment
|
||||||
|
|
||||||
Push to `main` → Forgejo webhook → Coolify rebuilds with nixpacks → live.
|
Push to `main` → Forgejo webhook → Coolify rebuilds with nixpacks → live.
|
||||||
A nixpacks rebuild takes **90 seconds to 2 minutes** — longer than the static
|
Rebuild time depends on whether Docker's build cache is warm: measured at
|
||||||
sites, which go in ~25s. Nothing changes on the site until the new container
|
**~20s warm** (you pushed recently) and **~90s cold** (the cache goes stale
|
||||||
swaps in at the very end.
|
after an idle hour or so, which is the usual case). Nothing changes on the site
|
||||||
|
until the new container swaps in at the very end, so the old version keeps
|
||||||
|
serving for the whole build.
|
||||||
|
|
||||||
To know when your commit is actually live, rather than guessing:
|
To know when your commit is actually live, rather than guessing:
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue