devsync doctor
Validate your devsync setup and detect configuration problems.
Synopsis
Section titled “Synopsis”devsync doctorDescription
Section titled “Description”devsync doctor runs a series of health checks against your devsync environment and reports any problems it finds. It is the quickest way to diagnose why push, pull, or decryption might be failing.
Run doctor whenever you set up devsync on a new machine, after rotating your age key, or when a command produces unexpected errors.
Checks performed
Section titled “Checks performed”| Check | Description |
|---|---|
| Repository directory | Verifies that ~/.config/devsync/sync/ exists and is a valid git repository. |
| Manifest validity | Parses manifest.json and reports any schema or syntax errors. |
| Age identity | Confirms that the age identity path in settings.json points to a readable file and that the key can be loaded. |
| Tracked paths | Checks that each path registered in manifest.json currently exists on the local filesystem. |
If any check fails, doctor exits with code 1. All checks are always run so you receive a complete report in a single pass.
Options
Section titled “Options”| Flag | Description |
|---|---|
--verbose | Print detailed diagnostic information for each check. |
Examples
Section titled “Examples”# Run all health checksdevsync doctor
# Run with verbose output to see details of each checkdevsync doctor --verboseExample output
Section titled “Example output”✓ Repository directory exists and is a valid git repo✓ manifest.json is valid✗ Age identity: file not found at /home/user/.secrets/age-identity.txt✓ Tracked local paths: 12/13 exist ✗ ~/.config/missing-tool/config.toml — not found