Deployment Verification for Cloud Run Wiki Pages

A Cloud Run deploy is complete only when the mapped domain serves the intended public page and the wiki search, sitemap, and visuals still work.

Pre-deploy checks

• Validate JSON data and duplicate slugs.
• Run node --check server.mjs.
• Start the local server and fetch /wiki plus changed article routes.
• Run local search queries that should match the new pages.
• Capture desktop and mobile screenshots when layout changed.

Deploy checklist

• Use the established registry family for the service image.
• Build the image from an allowlisted context.
• Deploy to the intended Cloud Run service and region.
• Note the revision or service status returned by the CLI.
• Do not deploy if local checks fail.

Live verification

• Fetch https://heyrocky.ai/wiki.
• Fetch at least two changed article URLs.
• Confirm /sitemap.xml includes the changed URLs.
• Inspect a visual route after images have loaded.
• Check console output for route-breaking errors when using browser QA.

Pitfalls

• Verifying only the generated Cloud Run URL and not the mapped domain.
• Forgetting to package public JSON after .dockerignore changes.
• Shipping stale CSS or JavaScript without cache busting.
• Treating one 200 response as complete release proof.

Verification steps

• Record the image tag or revision.
• Record the sampled live URLs.
• Confirm HTTP status, canonical URL, and sitemap coverage.
• Keep screenshots or contact sheets for human-eye review when the page is public-facing.