Deploy · four starting paths
Move from localhost to production
A working local URL proves that a service runs on your own machine. Before other people can reach it, check where the process listens, how traffic arrives, what configuration changes, and how you will verify the release.
Next.js
Run the project's production build and start command in a production-like environment. Verify the actual URL and port from the deployment platform, then test a page, an API route, and an image or other static asset.
- Separate values that must be available in browser code from secrets that belong only on the server.
- Check redirects, authentication callbacks, and API base URLs after replacing local origins.
- Confirm the platform's build logs and a real response, not just a successful deploy status.
Inspect pasted configuration · Next.js deployment documentation
Node.js
Make the listening port configurable for the deployment environment. Ensure the process binds to the interface expected by your host or reverse proxy, while the public endpoint uses HTTPS.
- Keep secrets in the hosting environment and check required variables at startup.
- Expose a lightweight health route and test it through the public hostname.
- Inspect process logs and shutdown behavior before relying on a successful local curl result.
Generate a listener or HTTP check · Node.js server.listen documentation
Docker
A container's listening port and the host's published port are different. Confirm that the service listens on the expected container interface and that Compose or your host publishes the intended port.
- Check the host-to-container port pair and any address restriction such as
127.0.0.1. - Run the built image with production configuration and inspect container logs.
- Verify the public route through the proxy or ingress, including HTTPS and health checks.
Headless WordPress
The website frontend and WordPress API often have separate origins. Replace local URLs in both systems, test the API from a browser, and check that the production origin is allowed when cross-origin access is required.
- Test a published post, media URL, and authentication or preview route using the public addresses.
- Use HTTPS and verify the API response headers if the browser reports CORS errors.
- Keep private administration routes and credentials out of frontend configuration.
Final check: Open the public URL from a device outside your development machine. Confirm the expected page, API response, redirects, and logs. The navigation's Production Deployment Checklist provides a downloadable checklist.