Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.skrmir.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Single-Binary Installation

​
Audience

This page is for developers and operators who want to try the AiOS bootstrap entry or validate the local development flow.

​
Goal and Scope

This page explains how to start AiOS through the single-binary entry, with one important caveat:
  • this is the bootstrap / development-validation entry
  • it is not the final production runtime model

​
Core Concepts

  • the single binary starts the minimal control plane and install flow
  • the formal runtime target remains image-based services inside K3s

​
Current Runtime Mode Notes

cmd/aios currently supports two runtime-mode interpretations:
  • bootstrap: allows startup without PostgreSQL and is intended for install flow, bring-up, local validation, and structural debugging
  • persistent: requires PostgreSQL and is the mode where the current control-plane capabilities that depend on durable task state become fully wired
That means “the service started” is not the same thing as “every control-plane surface is fully available.” If you are only validating bootstrap flow, bootstrap is a valid path. If you need to validate control-plane behavior that depends on persistent task state, prepare PostgreSQL first and start the service in persistent mode.

​
Standard Workflow

  1. prepare the local environment
  2. start cmd/aios
  3. verify startup with health checks
  4. continue into the bootstrap/install flow

​
CLI Examples

go run ./cmd/aios
curl http://localhost:8080/healthz
curl http://localhost:8080/readyz

​
Web UI Path

Once the service starts, the Web UI will serve as the bootstrap/install entry (to be expanded later).

​
Pitfalls / Risk Notes

  • local single-binary startup is only for development and bootstrap, not the formal production shape
  • formal runtime should later deploy the control-plane services into K3s
  • some current console read surfaces depend on persistent task state; in bootstrap mode they should not be interpreted as merely “empty data” but as outside the fully persistent capability set