Config-only quickstart
Create, review, apply, update, and remove a templated file without root privileges.
Richt is a standalone Go CLI for executable host configuration plans. Describe hosts and reusable services in YAML, inspect the resolved inventory, prepare changes against the targets, then review and explicitly apply them. Services combine RPM packages, templated files, and systemd processes. Config-only, package-only, and process-only services are also supported.
Start with the config-only quickstart , then use installation and platform requirements and the CLI reference for your environment. The examples include ready-package vmango, SSH, local secrets, and deliberate failure/continuation scenarios. Validation separates recorded Linux acceptance from illustrative configurations.
The focused contracts are:
Read limitations before using a saved plan as an operational artifact. Plans contain prepared executable inputs, potentially including secrets; apply does not recompute changes or check targets for drift.
For contributors, CI and releases explains the shared checks, binary archives, manual publication, and required repository protection settings.
Create, review, apply, update, and remove a templated file without root privileges.
Install a release archive or build Richt, choose controller and target platforms, and configure privileges.
Commands, flags, selection, confirmation, concurrency, and exit status.
Define services and hosts, merge tag variables, resolve paths, and select assignments.
Render templates, manage file attributes, and execute protected JSON plans.
Manage exact package requests, process reactions, unit files, and explicit removal.
Reuse OpenSSH configuration, apply explicit privileges, and bound host concurrency.
Resolve local secret sources during preparation and protect executable saved inputs.
Understand partial failure and explicitly retry unfinished saved-plan tasks.
Choose a config-only, ready-package, SSH, secrets, or continuation scenario.
Runnable examples, rendered directly from their repository README files.
Run the shared checks and archive build, publish a manual release, and configure required CI.
Understand supported backends, frozen-input boundaries, and deferred capabilities.
Recorded Linux acceptance results, environment, commands, and limits.