Template hypervisor sets the provisioning pointers so rebuild-nexus works after getting-started.sh #13

New issue

Closed

opened 2026-10-09 18:57:29 +01:00 by vnprc-agent · 1 comment

vnprc-agent commented

2026-10-09 18:57:29 +01:00

The template hypervisor sets the provisioning pointers getting-started.sh already fixed, so rebuild-nexus works on a laptop built from the template instead of refusing with DEPLOY_FLAKE is not set.

Primary goals:

rebuild-nexus works after the script — nexus.provisioning.deployFlake is /home/<operator>/work/allod/deploy and nexus.provisioning.inventoryCheckout is /home/<operator>/work/allod/inventory, the layout the script creates and the other host scripts already default to.
One source for the operator's name — the profile reads username from the builder's specialArgs, as the deployment that composes this host does, so the paths follow identity and nothing is typed twice.
Every host-script variable accounted for — with these two set, every environment variable the host scripts read is either rendered by the host module (DEPLOY_FLAKE, INVENTORY, INVENTORY_CHECKOUT, LIBVIRT_DEFAULT_URI, ALLOD_HYPERVISOR) or defaults inside the script to the same layout (IDENTITY_CONFIG and PROFILES_CONFIG through the registry, AGE_IDENTITY to ~/.ssh/host, KNOWN_HOSTS_VMS, PI_PROVIDER_STATE_DIR).

Current state and specifics

hosts/hypervisor/nexus/configuration.nix enables GDM and GNOME and sets nothing else. allod/nexus nix/configuration.nix renders DEPLOY_FLAKE and the inventory pointers only when the options are set and says rebuild-nexus has no fallback by design. provision-vm and rebuild-vm default DEPLOY_FLAKE to $HOME/work/allod/deploy, so they work on the template host and rebuild-nexus alone does not. Found on the public install walk, 2026-10-09: rebuild-nexus on the laptop printed DEPLOY_FLAKE is not set. Set nexus.provisioning.deployFlake to point rebuild-nexus at your deploy flake; it has no fallback.

Scope

In: the two option settings in the template profile and the README line that says the template host rebuilds with rebuild-nexus. Out: the option's design in allod/nexus, and the start-here page's wording, which follows once this lands.

Part of allod/strategy#65

The template hypervisor sets the provisioning pointers `getting-started.sh` already fixed, so `rebuild-nexus` works on a laptop built from the template instead of refusing with `DEPLOY_FLAKE is not set`. Primary goals: - **`rebuild-nexus` works after the script** — `nexus.provisioning.deployFlake` is `/home/<operator>/work/allod/deploy` and `nexus.provisioning.inventoryCheckout` is `/home/<operator>/work/allod/inventory`, the layout the script creates and the other host scripts already default to. - **One source for the operator's name** — the profile reads `username` from the builder's `specialArgs`, as the deployment that composes this host does, so the paths follow identity and nothing is typed twice. - **Every host-script variable accounted for** — with these two set, every environment variable the host scripts read is either rendered by the host module (`DEPLOY_FLAKE`, `INVENTORY`, `INVENTORY_CHECKOUT`, `LIBVIRT_DEFAULT_URI`, `ALLOD_HYPERVISOR`) or defaults inside the script to the same layout (`IDENTITY_CONFIG` and `PROFILES_CONFIG` through the registry, `AGE_IDENTITY` to `~/.ssh/host`, `KNOWN_HOSTS_VMS`, `PI_PROVIDER_STATE_DIR`). ### Current state and specifics `hosts/hypervisor/nexus/configuration.nix` enables GDM and GNOME and sets nothing else. `allod/nexus` `nix/configuration.nix` renders `DEPLOY_FLAKE` and the inventory pointers only when the options are set and says `rebuild-nexus` has no fallback by design. `provision-vm` and `rebuild-vm` default `DEPLOY_FLAKE` to `$HOME/work/allod/deploy`, so they work on the template host and `rebuild-nexus` alone does not. Found on the public install walk, 2026-10-09: `rebuild-nexus` on the laptop printed `DEPLOY_FLAKE is not set. Set nexus.provisioning.deployFlake to point rebuild-nexus at your deploy flake; it has no fallback.` ### Scope In: the two option settings in the template profile and the README line that says the template host rebuilds with `rebuild-nexus`. Out: the option's design in `allod/nexus`, and the start-here page's wording, which follows once this lands. Part of allod/strategy#65

vnprc referenced this issue from a commit

2026-10-09 19:01:54 +01:00

Template hypervisor sets the provisioning pointers

vnprc-agent referenced this issue from allod/strategy

2026-10-09 23:10:21 +01:00

A Forgejo VM on the hypervisor: PRs and issues for a forge-less deployment #65

vnprc-agent commented

2026-10-10 13:42:59 +01:00

Author

Landed on allod/profiles master 7b2c21f: the template hypervisor sets nexus.provisioning.deployFlake and inventoryCheckout from the operator's username. Pinned through the deploy template.

Landed on allod/profiles master 7b2c21f: the template hypervisor sets nexus.provisioning.deployFlake and inventoryCheckout from the operator's username. Pinned through the deploy template.

vnprc-agent closed this issue

2026-10-10 13:43:00 +01:00