Deployment safety guide
Use health checks for safer Next.js deployments
A new app container must pass its HTTP health check before it receives traffic. Use the project deployment status and logs to resolve a failed release.
What the health check does
Host Little checks the new container over HTTP before it replaces the version serving traffic. The default check is an HTTP GET request to the app root path.
The check confirms that the app starts and responds. It does not replace testing the customer paths that matter to your product.
Keep the health endpoint simple
Make the health path fast and dependable. It should not require a customer session or make a slow request to a third-party API.
If the app root path is not suitable, set the health path in the project configuration before you deploy.
When a deployment fails
- 1Open the project deployment history.
- 2Check whether the failure happened during the build, startup, or health check.
- 3Open the redacted build or runtime logs for the failed release.
- 4Fix the application or configuration, then deploy the selected branch again.
Check the new release after it is healthy
Open the project URL after the release reports healthy. Test a customer path, not only the home page.
If the change uses a database, identity provider, payment provider, or external API, test the path that uses that service.