Documentation · Config safety
Configuration is previewed and verified before it becomes server state
Sysaro avoids a universal “edit /etc” surface. Each adapter owns specific files or drop-in fragments and has its own schema.
Verified against public version: 0.20.02026-09-15Factual boundary · roadmap is not presented as shipped
Typed configuration in Sysaro follows desired state → server-side validation → exact managed-file preview → explicit apply → native config validation → restart/reload → readiness → rollback on failure.
Transactional path
1
Desired state
Known fields and bounded values only
2
Preview
Path, content, SHA-256, create/change
3
Native validation
nginx -t, promtool, collector validate and similar checks
4
Apply
Atomic write + lifecycle + readiness + rollback
Ownership
| Area | Current boundary |
|---|---|
| ClickHouse | /etc/clickhouse-server/config.d/90-sysaro.xml |
| MinIO | Sysaro EnvironmentFile + systemd drop-in |
| Observability | Sysaro-owned config/environment files per adapter |
| nginx/PHP-FPM | Managed Site/pool config; global foreign config is not silently overwritten |
Rollback
Before writing, Sysaro retains existence state, contents and Unix mode. Partial write, validation, reload, restart or readiness failures restore the previous version.
The client does not provide an arbitrary managed-file path or probe URL: those boundaries are defined by the Agent adapter.