Platform foundations
Inspect the first deployment
Read build output, deployment metadata, generated URLs, source commit, and runtime behavior instead of stopping when the dashboard says Ready.
8 minute lesson
Every deployment records what source was built, how it was built, and the unique URL for the resulting output.
Open the deployment and read the build logs, duration, framework result, assigned environment, commit, and domains. Visit the generated URL and test a direct dynamic route, a form, and the health endpoint. A green build proves compilation and packaging succeeded; it does not prove every runtime path or external dependency works.
Record the immutable deployment URL and ID, not only the domain alias. The alias can move later, while the unique URL preserves the exact artifact you inspected. Confirm that the source commit, environment, build settings, and expected environment-variable names match the release.
Use direct HTTP evidence as well as a browser. Check status, redirects, cache headers, and content type for a static path, dynamic path, mutation, missing resource, and health route. If runtime behavior fails after a green build, move to runtime logs for that deployment and request rather than rebuilding unchanged source.
Test the home page, one dynamic note URL, a missing note, and /api/health from the deployment URL. Record any difference from local behavior.
Lesson completed