Idea Comindo hosting has Node.js available for support-assisted deployments. Use it for applications that have a startup file such as server.js, app.js, or a framework command that listens on a port.
Create
- Prepare the project on your computer and make sure it runs locally.
- Upload the project files with File Manager, FTP, or Git if your account supports it.
- Do not upload
node_modules unless support specifically asks you to. It is usually better to install dependencies on the server.
- Open a support ticket with the domain, project folder, startup command, required Node.js version, required environment variables, and preferred public URL.
- Support will install dependencies with
npm install --omit=dev or the command required by your project.
- Support will run the app with PM2 and connect the domain to the application through the web server reverse proxy.
- After deployment, test the domain in a private browser window and report any missing pages, assets, or API calls.
If the application needs build output, run or request the build step before starting it, such as npm run build. If the app needs background workers, websockets, or a custom port, mention that before going live.
Manage
- Upload code changes to the same project folder or provide a Git release for support to pull.
- Tell support when dependencies, build commands, environment variables, or startup commands change.
- Ask support to restart the PM2 process after changes that require a restart.
- Keep secrets such as API keys out of public files and screenshots.
Delete
- Back up files and any connected database first.
- Ask support to stop and delete the PM2 process.
- Ask support to remove the reverse proxy rule for the domain or subdomain.
- Remove uploaded application files, unused databases, and DNS records after you confirm the app is no longer needed.
Troubleshooting
- If the page shows 503 or a blank page, check whether the Node.js process is running.
- If dependencies fail to install, check the Node.js version and package lock file.
- If static assets are missing, confirm the build folder and public asset paths.
- If environment values are missing, recheck variables such as API keys, database host, and app URL.
- When opening a ticket, include the domain, startup file, startup command, Node.js version, and the latest application error log.