komrad setup
Set this machine up for komrad, asking for whatever is missing
komrad setup [flags]Each step asks the doctor whether its part of the machine is ready, and only when it is not does it ask a question and change something, then asks the doctor again. Nothing records which steps ran, so running it again after stopping part way finds the finished steps already done. It ends on the doctor's full report.
Setup writes the config file only when there is none, from a config template filled with your answers. It never changes a config file that already exists: a step that would stops and names the setting to change there.
With --no-input, or when stdin is not a terminal, nothing is asked: a step that needs an answer takes it from a flag, and names the flag when none was given.
The database step runs while database_url is left empty. It creates the embedded Postgres under the state directory without asking, migrates it, and makes an engine named default, writing no connection settings. With --no-embedded-postgres it takes the url of a login that owns a Postgres you already run instead, from --owner-database-url or by asking, and writes the [connection] settings.
The forge step connects github.com or gitlab.com with a pasted token once the engine is running, and skips until then. Unattended it skips, and komrad forge connect connects any forge after setup.
Flags#
| Flag | Type | Description |
|---|---|---|
--harness | string | the harness new agents run, when the default one is not on PATH |
--no-embedded-postgres | bool | keep the database in a Postgres you already run, when no database is set up |
--no-input | bool | ask nothing, taking every answer from a flag |
--owner-database-url | string | the url of a login that owns a Postgres you already run, when no database is set up |