Verify the package before production
Run the local validator and checksum verification. Capture protected application routes before changing the overlay so post-deploy comparisons have a known baseline.
bin/thonem-cloudpanel verify
bin/thonem-site release-check https://thonem.brightery.com pre /tmp/thonem-v7-baseline.json /thonem.jsSnapshot only the website-owned directories
The v7 overlay tool refuses unknown targets and backs up /_thonem-site/ and /explore/ before replacement. It does not move application controllers, API code or payment routes.
Replace directories as complete units
Stage first, validate the staged copy, then replace the two website directories. Avoid mixing half of one release with half of another.
Compare both the website and protected routes
Smoke-test the public pages and health endpoint, then compare protected application route status/content type. Finally run the commerce application’s own checkout, webhook and worker tests.
Use these patterns to structure a Thonem project, then verify the exact routes, providers, secrets, queues and infrastructure of the deployed environment before changing production.