safe-deploy

Safe Deploy: guarded LIVE deploy + rollback

Invocation: /safe-deploy $1 where $1 is com (gotodive.com) or eu (gotodive.eu). Both are LIVE production. NEVER skip the confirmation gate.

Environment (re-set every fresh shell — they are process env, not persisted)

$env:SSH_PROD_HOST='89.58.21.27'; $env:SSH_PROD_USER='hosting220420'
$env:SSH_PROD_KEY='~/.ssh/gotodive_prod'; $env:SSH_PROD_PORT='22'
$key = $env:SSH_PROD_KEY -replace '^~', $env:USERPROFILE
$tgt = "$($env:SSH_PROD_USER)@$($env:SSH_PROD_HOST)"

Web root: .com = gotodive.com/httpdocs, .eu = gotodive.eu/httpdocs. Theme base (.com): gotodive.com/httpdocs/wp-content/themes/gotodive-com. scp uses -P (capital) for port; ssh uses -p.

PHASE 0 — PRECHECK (block if not green)

Run /precheck <slug-or-all>. If PRECHECK: FAIL, STOP and hand back to the caller (content-loop / design-system) to fix. Do not deploy red content.

PHASE 1 — BACKUP (reversible safety net)

• Files: before overwriting any theme file, copy the remote original aside: ssh ... 'cp <path> <path>.bak-$(date +%Y%m%d%H%M)' (single-quoted; avoid parentheses / escaped double-quotes inside ssh — they hang the shell).
• DB (for content/page edits): dump outside web root, e.g. $HOME/wp --path=. db export ~/gotodive-com-predeploy-<date>.sql.

PHASE 2 — DIFF + CONFIRM (mandatory human gate)

• Show the user exactly WHICH files change and a short summary of WHAT changes.
• For CSS/theme.json changes, confirm style.css Version header was bumped.
• ASK for an explicit "yes". Do NOT proceed without it. Prod is LIVE.

PHASE 3 — DEPLOY

• Theme/template/CSS (.com block theme): scp -i $key -P $env:SSH_PROD_PORT <localfile> "${tgt}:$base/<path>" then ssh ... 'chmod 644 <path>; $HOME/wp --path=. cache flush; $HOME/wp --path=. transient delete --all' ALWAYS chmod 644 after scp; ALWAYS flush cache + transients. CRITICAL: scp is binary-safe (preserves UTF-8). NEVER deploy non-ASCII content by echoing through PowerShell — it corrupts ·->??. Use scp or eval-file.
• Locale page bodies (.eu): python scripts/_deploy-locale-bodies.py --env prod --langs ru,de --all --write
• PHP/DB edits: write a local PHP file, scp it, run $HOME/wp --path=. eval-file <file>, then rm -f <file>.

PHASE 4 — VERIFY LIVE (then rollback if broken)

• Content: Invoke-WebRequest "https://<site>/?nocache=$(Get-Random)", grep the new copy, and assert ZERO ?? / mojibake in the served HTML.
• Visual: Playwright desktop 1366x900 + mobile 390 on the changed sections; set viewport explicitly (default narrow width triggers the @781px mobile layout).
• If live is wrong: restore the .bak file (or re-import the DB dump), flush cache, re-verify, then fix locally and re-run from PHASE 0.

PHASE 5 — DONE

Report: site, files deployed, version bump, live-verify result, backup location.

Hard rules

• Both prod sites are LIVE — confirmation gate is non-negotiable.
• gotodive.com = authority/E-E-A-T; never deploy prices/booking there (that's .eu).
• ssh commands: single-quote them; avoid (), [], and escaped double-quotes inside.
• Bump style.css Version on every CSS/theme.json change.
• Remove any one-shot uploaded PHP/injector scripts from the server after use.