Admin dashboard: update services to the latest main build, per service and all at once #262

Open
opened 2026-06-07 02:49:09 +00:00 by mik-tf · 1 comment
Owner

Today the admin dashboard can reinstall a whole machine to pick up new builds and it shows which components are behind. We want a more direct update flow on the dashboard: update a single service to its latest build from the main branch, and a one click update all services on a machine (and ideally the same across the whole fleet). The goal is that when a service has a newer build on main, an operator can roll it out from the dashboard without hand copying binaries or reinstalling the entire stack. This builds on the existing build identity and check for updates work. A concrete case that motivated this: a service can sit a long time behind main if its published latest release is not refreshed, and there is no easy dashboard way to bring just that one service current. Out of scope for now: automatic or scheduled updates.

Related: #256

Signed-by: mik-tf mik-tf@noreply.invalid

Today the admin dashboard can reinstall a whole machine to pick up new builds and it shows which components are behind. We want a more direct update flow on the dashboard: update a single service to its latest build from the main branch, and a one click update all services on a machine (and ideally the same across the whole fleet). The goal is that when a service has a newer build on main, an operator can roll it out from the dashboard without hand copying binaries or reinstalling the entire stack. This builds on the existing build identity and check for updates work. A concrete case that motivated this: a service can sit a long time behind main if its published latest release is not refreshed, and there is no easy dashboard way to bring just that one service current. Out of scope for now: automatic or scheduled updates. Related: https://forge.ourworld.tf/lhumina_code/home/issues/256 Signed-by: mik-tf <mik-tf@noreply.invalid>
Author
Owner

Update

  • Also make it we can choose main, or development, or even maybe any other branches, but especially those two

Notes

we should allow chosing development or main, even after the fact of an install
so we can change the branch redownload all binaries
and restart all

today development might not work, or might start soon

# Update - Also make it we can choose main, or development, or even maybe any other branches, but especially those two # Notes we should allow chosing development or main, even after the fact of an install so we can change the branch redownload all binaries and restart all today development might not work, or might start soon
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/home#262
No description provided.