Skip to main content

Guides

Guides cover task-oriented workflows after the first successful deploy.

Available Guides​

  • Customer Domains: attach a hostname you control and understand DNS plus ACME validation modes.
  • Cargo SSH Jobs: scaffold an inspectable Script/Cargo SSH project and diagnose public SNI SSH routing.

Common Task Pattern​

Most Baran workflows follow the same pattern:

  1. Inspect with a read-only command.
  2. Dry run when the command supports it.
  3. Run the mutating command with the required confirmation flag.
  4. Read back state from the relay, Hub, gateway, or local report.
  5. Diagnose the failing stage before retrying spend.

For deploys, use:

proof baran preflight --quote
proof baran deploy --yes --dry-run --json
proof baran deploy --yes
proof baran status

For local recovery, start read-only:

proof baran deploy status
proof baran deploy doctor --report <report.json>

Do not use admin recovery commands from old runbooks unless PROOF support asks you to. Public user workflows should stay on the normal Baran CLI surface.