sealup check
Check sealup.yml and its variables without touching the server: the file, the targets, the
upload folders, the variables (their names and where they come from, never their values) and the
host keys. The safety nets that need no server run too.
sealup check [target] [flags]Target
Section titled “Target”- No name: every target. A problem of one target is a warning for it, and the exit code is 0 when at least one target is ready.
- A name: that target only.
Warnings
Section titled “Warnings”A pull: folder inside a folder that an upload entry mirrors (mirror: true) is deleted by every
deploy, unless an exclude covers it. check prints a yellow line for each such folder, with the
path to add to exclude, and does not change the exit code:
! The mirror deletes the pull: folder www/resources: no exclude covers it. To keep it, add public_html/resources to exclude in sealup.yml.Exit code
Section titled “Exit code”What a deploy would give before connecting:
| Code | Meaning |
|---|---|
| 0 | Ready |
| 2 | A config or variable problem |
| 4 | No host key |
| 6 | A safety net |
Global flags: -c, --env-file, --json, -q, --no-color (see sealup --help).
Examples
Section titled “Examples”sealup check # every targetsealup check staging # one targetsealup check --json # one JSON object on stdoutLearn more
Section titled “Learn more”sealup deploy --dry-run: a dry run also checks the server.- Exit codes: every code sealup gives.