For feature development on ilyama (API/workers) and pw (web console), use the local Docker stack — not the VM edge TLS bundle.Documentation Index
Fetch the complete documentation index at: https://docs.ilyama.golain.io/llms.txt
Use this file to discover all available pages before exploring further.
Prerequisites
- Go 1.25+
- Docker with Compose v2
- Node.js (for pw)
Platform backend (ilyama)
From repo root:make dev-provision alone skips sqlc generation.
Per-service env:
Auth bypass (optional)
WithAUTH_BYPASS=true in apis .env, any bearer token works for API calls — useful for platform-tui and e2e without Zitadel.
Web console (pw)
http://localhost:5173 — auto login as Dev User with mock fleets/devices.
Point at real local API by setting VITE_MOCK_AUTH=false and configuring Zitadel + VITE_API_URL.
platform-tui from source
Omega against local stack
Use HTTP mock transport or local MQTT frommake provision-mqtt-dev. For full JITR rehearsal, see vm-edge or e2e fixtures.
When to switch to vm-edge
Move to VM edge deployment when you need:- Public DNS and Let’s Encrypt
- mTLS on Postgres/Rabbit/Timescale
- Staging environment matching production topology