Node.js applications need a supported runtime and a production process manager or hosting integration. Confirm that your particular Nabtech service provides the required Node.js environment before deploying. A standard static website upload and a continuously running Node.js application are different workloads.
IN THIS ARTICLE
01 Check compatibility first
Record the application's supported Node.js range, package manager, start command, database and background services. Prefer an actively supported or maintenance LTS runtime compatible with the application. A version appearing in a selector does not by itself establish that the application or its dependencies remain maintained.
- Open the available application manager or Node.js selector in the hosting panel. If it is not present, confirm plan support rather than attempting to install server-wide software.
- Create an application with the supported runtime, application root, public URL and startup file requested by the integration.
- Upload the source and dependency lockfile securely. Keep secrets and writable application data out of publicly served directories.
- Install dependencies within the application's environment using the supported panel action or authorised shell. Check native-module requirements before assuming a build can run on shared hosting.
- Set production environment variables through the supported configuration. Use the database host and credentials for that service, and follow the integration's rules for listening ports.
- Start or restart the application through the manager, then review its logs and public HTTPS response.
02 Test more than the homepage
Check API requests, authentication, file uploads and any scheduled or background work. Confirm that the application recovers through the supported restart mechanism. Do not leave a development command or a terminal session as the only way the production app stays running.
What should I check if my Node.js deployment fails?
Look for a runtime mismatch, missing dependency, incorrect startup file, bad environment value or unavailable external service. Keep logs private where they contain credentials. A requirement for containers, custom daemons or a database not offered by the plan may need a different service.
Back up application data separately from the code repository. A Git checkout can restore source files, but it does not recover new customer records or uploaded files.