Publishing a website is more than clicking Deploy. The live environment may behave differently from a preview because domains, environment variables, build settings, and routing can change.
Keep a recoverable copy
Before major changes, make sure the project is saved in a repository or reliable backup. Exclude credentials, local configuration files, and private data from deployed files.
Check build settings
Confirm the framework, build command, output directory, runtime version, and start command match the project. Do not guess environment variable names; use the exact names the app expects.
Configure the live environment
Add secrets through secure hosting settings. Point the domain to the correct project, enable HTTPS, and update authentication redirect URLs if the app uses sign-in.
Test important routes
Open the homepage, refresh inner pages, test forms, sign in and out, and try the main user journey. A route that works when clicked may still fail when opened directly.
Launch checklist
- Backup or version control is current.
- No secrets are included in public files.
- Build and runtime settings are correct.
- Domain and HTTPS work.
- Important pages pass a production smoke test.
- A recovery path is understood.
Small, verified releases are easier to troubleshoot than a large last-minute rewrite. Publish deliberately and test the real domain.