vaultline docs

This documentation complements the main release site and focuses on hands-on operation.

Start here

Use CLI for command usage and completion behavior.
Use Daemon & API for process behavior, service integration, and endpoint details.
Use Store model for multi-store semantics and storage layout.
Use Backup & restore for archive and recovery operations.
Use Runbook (Project Workflow) for release/versioning workflow and helper scripts.

Start and verify daemon readiness (vaultline daemon, vaultline health) so API and store state are visible before any secret operation. See: Daemon & API.
Initialize/register stores (store init, store add) to define store boundaries and passphrase handling early. See: Store model and CLI.
Unseal only required stores (store unseal, optionally --from-secret) to minimize exposure and keep per-store access explicit. See: Daemon & API.
Execute secret lifecycle commands (secret set/get/list/glob/copy/move/delete) as the primary operational interface. See: CLI.
Run backup/export and reseal workflow before and after sensitive changes. See: Backup & restore and CLI.

Confirm daemon health and store status with vaultline health. See: Daemon & API.
Unseal only the stores required for the current task. See: Daemon & API.
Snapshot/backup before broad updates. See: Backup & restore.
Perform secret changes via CLI commands. See: CLI.
Reseal stores according to your operating policy. See: Store model and Daemon & API.