lhumina_code/hero_os_tfgrid_deployer
0
0
Fork 0
Code Issues 16 Pull requests Projects Releases 3 Packages Wiki Activity Actions 1

Harden installer service starts for fresh VMs #35

Merged
mik-tf merged 1 commit from development_mik_deployer_installer_direct_starts into development 2026-06-24 06:29:06 +00:00
Conversation 0 Commits 1 Files changed 1 +47 -2
mik-tf commented 2026-06-24 06:28:41 +00:00
Owner
Copy link

Hardens the fresh member VM installer for the service-start gaps found during the Hero Explorers mainnet bootstrap:

  • starts hero_router directly through hero_proc when the VM lab registry points at the wrong router crate path
  • starts hero_cockpit through its self-start CLI because it is not exposed as a lab service key on the VM build
  • starts hero_kimi_server directly through hero_proc so Kimi Rust is available even when kimi_rust only manages the web process
  • skips hero_components service start on VM lab builds that only install its binary and do not expose a service key

Verification:

  • bash -n crates/hero_tfgrid_deployer_server/assets/setup-binaries.sh
  • git diff --check
  • cargo +1.96 check -p hero_tfgrid_deployer_server
  • manual recovery on the three Hero Explorers member VMs: router, cockpit, biz, planner, Kimi server, and proxy running; deployer install_state is ready for all three

Refs: #30

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

Hardens the fresh member VM installer for the service-start gaps found during the Hero Explorers mainnet bootstrap: - starts `hero_router` directly through `hero_proc` when the VM lab registry points at the wrong router crate path - starts `hero_cockpit` through its self-start CLI because it is not exposed as a lab service key on the VM build - starts `hero_kimi_server` directly through `hero_proc` so Kimi Rust is available even when `kimi_rust` only manages the web process - skips `hero_components` service start on VM lab builds that only install its binary and do not expose a service key Verification: - `bash -n crates/hero_tfgrid_deployer_server/assets/setup-binaries.sh` - `git diff --check` - `cargo +1.96 check -p hero_tfgrid_deployer_server` - manual recovery on the three Hero Explorers member VMs: router, cockpit, biz, planner, Kimi server, and proxy running; deployer install_state is ready for all three Refs: https://forge.ourworld.tf/lhumina_code/hero_os_tfgrid_deployer/issues/30 Signed-by: mik-tf <mik-tf@noreply.invalid>
Start router and Kimi directly through hero_proc when the VM lab registry cannot install them, use the cockpit self-start CLI, and skip hero_components service start on lab builds that only install its binary. This keeps fresh member VM installs from requiring manual service recovery after binaries download.

Refs: #30

Signed-by: mik-tf <mik-tf@noreply.invalid>
mik-tf merged commit 1218f918f7 into development 2026-06-24 06:29:06 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/hero_os_tfgrid_deployer!35
No description provided.