Mobayilo CLI - Website Runbook

Mobayilo CLI - Website Runbook

This runbook covers deployment and validation for https://mobycli.mobayilo.com.

Scope

• Static site source: mobycli-site/
• Installer source: docs/public/install.sh
• Deploy workflow: .github/workflows/mobycli-site-deploy.yml
• Release workflow (publishes site + release payload on tags): .github/workflows/cli-release.yml
• Cloudflare Pages project name: mobycli
• Domain target: mobycli.mobayilo.com

Preconditions

• Cloudflare Pages project mobycli exists.
• Repository secrets are configured:
  • CLOUDFLARE_API_TOKEN
  • CLOUDFLARE_ACCOUNT_ID
• DNS access for mobayilo.com zone is available.

Deployment Behavior

• Workflow triggers on push to main when files change in:
  • mobycli-site/**
  • docs/public/install.sh
  • .github/workflows/mobycli-site-deploy.yml
• Workflow copies installer into site bundle:
  • mobycli-site/install.sh
• Workflow syncs latest GitHub Release assets into:
  • mobycli-site/releases/latest.json
  • mobycli-site/releases/v<version>/...
• Workflow deploys mobycli-site/ to Cloudflare Pages using wrangler pages deploy ... --branch=main.

Domain Setup

1. In Cloudflare Pages project mobycli, add custom domain:
   • mobycli.mobayilo.com
2. Confirm DNS record is created and proxied.
3. Confirm TLS status is active for the custom domain.

Post-deploy Validation

1. Homepage check:
   • https://mobycli.mobayilo.com/
2. Installer check:
   • https://mobycli.mobayilo.com/install.sh
3. Release metadata check:
   • https://mobycli.mobayilo.com/releases/latest.json
4. Release archive check:
   • https://mobycli.mobayilo.com/releases/v<version>/checksums.txt
5. Content checks:
   • Install snippet present.
   • moby self-update command is visible in install/quickstart content.
   • Quickstart commands present.
   • Links to help docs and GitHub present.

Fresh-machine Smoke

On a clean machine profile:

curl -fsSL https://mobycli.mobayilo.com/install.sh | sh
moby --version
moby self-update
moby auth login
moby auth status --json

Expected:

• install completes without manual patching
• binary is runnable from shell
• auth flow completes successfully

Rollback

• Re-deploy previous known-good main commit to Pages.
• If installer regression exists, rollback commit containing docs/public/install.sh.
• If release payload regression exists, publish patched release tag and let CLI Release redeploy payload.