frankendeploy doctor

frankendeploy doctor

Diagnose the local machine, the server, and DNS before a deploy

Synopsis

Runs preflight checks and explains how to fix every problem found:

Local checks:

  • Docker CLI installed and daemon reachable

Remote checks (over SSH):

  • passwordless sudo (unless root)
  • Docker installed and usable without sudo
  • ‘frankendeploy’ network present
  • Caddy reverse proxy container running
  • free disk space
  • inside a project: the app runs on its own isolated network

DNS check (when a domain is configured or passed via —domain):

  • the domain resolves to the server’s public IP — the #1 cause of Let’s Encrypt certificate failures
frankendeploy doctor <server> [flags]

Options

      --domain string   Domain to check against the server IP (default: deploy.domain from frankendeploy.yaml)
  -h, --help            help for doctor

Options inherited from parent commands

      --config string   Config file (default: frankendeploy.yaml)
  -v, --verbose         Show detailed logs
  -y, --yes             Skip confirmations (CI/CD mode)

SEE ALSO

Auto generated by spf13/cobra on 2-Sep-2026