Deploy an AI-built Node.js app on Enhance

Review what the agent created

• Confirm the framework, Node.js version and package manager are intentionally supported.
• Check that the lock file is present and matches the package manifest.
• Remove sample credentials, development-only endpoints and placeholder administrator accounts.
• Confirm server-only secrets cannot be included in browser bundles.
• Run dependency, type, lint, test and production-build checks.

Make the application production-compatible

• Provide a production start command that exits with an error when startup fails.
• Listen on the configured application port rather than assuming port 3000 is always available.
• Bind the process in the way required by the hosting runtime rather than exposing a development server.
• Write useful output to standard output or the application log and avoid logging secrets.
• Set production mode and disable development debugging interfaces.

Configure the application in Enhance

1. Create an empty website or application path that does not overlap another installed application.
2. Open the website, then open Advanced and Node.js.
3. Choose automatic mode for a production application that should restart after it exits.
4. Select the required Node.js major version and set the working directory relative to the website home.
5. Enter the production startup command and the port used by the application.
6. Enable the proxy for the required path and deploy the application.

Add data and secrets safely

1. Create the production database and a dedicated database user.
2. Add environment values through the protected server configuration rather than committing a live .env file.
3. Run schema migrations once, with a backup and a rollback plan.
4. Create the first administrator through a controlled setup process and remove public setup routes afterwards.

Verify more than the homepage

• Check the health endpoint and the first application error in the persistent application log.
• Test sign-in, forms, file uploads, email, scheduled tasks and payment callbacks that apply to the app.
• Restart the Node.js application and confirm it returns without manual commands.
• Verify the primary domain, HTTPS, redirects and WebSocket behavior when used.
• Restore the previous release if the application cannot pass the agreed checks.