Sync the self-hosting stack
This commit is contained in:
@@ -9,6 +9,20 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
|
||||
Every version published to a channel appears here. Nothing is written from memory afterwards: a build
|
||||
cannot be published without its entry.
|
||||
|
||||
## 2026-10-22 — A large fleet no longer slows the console down `api 2.1.1` `web 2.1.4`
|
||||
|
||||
**With hundreds of machines enrolled, the console stays responsive.** Every machine reports its
|
||||
inventory every fifteen minutes and again whenever it reconnects, and each report used to reach every
|
||||
open console, which rewrote its list of machines and reread the whole assets list — one report at a
|
||||
time, and hundreds at once after an api restart.
|
||||
|
||||
- **The api only tells the consoles when a machine changed something they show** — its name, system,
|
||||
address, version or capabilities. Its presence is announced as before.
|
||||
- **The console folds the machine updates that arrive together into one pass**, and rereads the assets
|
||||
list only when one of them changed something that list shows.
|
||||
|
||||
Update the API and web images together. No agent update is required.
|
||||
|
||||
## 2026-10-22 — The assets grid scrolls inside itself and counts its rows `web 2.1.3`
|
||||
|
||||
**On the Assets page, the inventory scrolls inside its grid**, under headings that stay in place, and
|
||||
|
||||
Reference in New Issue
Block a user