Skip to main content
This quickstart is the first successful path on the current public StackKits release: a released Basement Kit on a supported Ubuntu server you already operate. The CLI remains the local execution authority.

​
Bootstrap a Basement Kit

On a supported Ubuntu server, the Basement installer creates ~/my-homelab, installs the released artifacts and required runtime, initializes local owner custody, bootstraps the local Admin/PocketID access, validates the generated StackSpec, and applies the default Basement services:
A hosted kombify account is not required. StackKits itself still requires a local Owner/Admin, which this bootstrap creates automatically. Keep the generated access details private.
Need a different installer? Use Choose a kit for the toolchain-only path, Cloud Kit for a VPS you already operate, or the CLI walkthrough on Windows.

​
Review or change the generated intent

Inspect stack-spec.yaml before generating output. In particular, review the absolute storage roots, the home.test local domain, site and node identities, and the empty optional workload selection. The StackSpec is the configuration input. CUE remains the validation authority and generated rollout files are outputs, not files to edit by hand. See Configure a StackSpec for current examples.

​
Generate and inspect a changed plan

Confirm that generation and apply readiness are both ready, then review the selected workloads and artifact paths.

​
Apply an intentional change

The Basement one-liner already performs the initial apply. Run these lifecycle commands only after you intentionally change stack-spec.yaml. Keep the local logs and access record with the workspace.

​
Continue

Basement Kit

Learn about the local, single-environment kit.

Cloud Kit

Use the same standalone lifecycle on a VPS you operate.

Apply safely

Review readiness and generated artifacts before changing the host.