Deployment guide

Make release safety
a command, not a checklist.

DeployPro can run deterministic pre- and post-deployment commands so the release either verifies cleanly or exposes exactly what changed.

← DocumentationPlan a build →
TH / DOCS
Principle→Boundary→Verification
implementation guidance · not a public API guarantee
01 / PRE-DEPLOY

Validate before replacing files

Run package validation, route-collision checks and a baseline snapshot of critical application routes before any switch.

bin/thonem-site release-check https://thonem.brightery.com pre /tmp/thonem-baseline.json /thonem.js /your/api/route
02 / SWITCH

Prefer atomic replacement

Stage release-owned paths beside the current version, validate permissions and syntax, then rename or release through DeployPro. Do not partially copy a mixed old/new asset set.

03 / POST-DEPLOY

Compare what matters

Smoke-test public pages, compare protected route status/content type, and test the application’s payment, webhook, queue and admin flows independently.

Project-specific contracts win.

These pages describe Thonem implementation patterns. Exact endpoints, payloads, credentials, retry rules and provider capabilities must be taken from the deployed project and its provider documentation.