{"id":143360,"date":"2026-04-08T01:47:33","date_gmt":"2026-04-08T01:47:33","guid":{"rendered":"https:\/\/www.hostinger.com\/ca\/tutorials\/deploy-node-js-application\/"},"modified":"2026-04-08T01:47:33","modified_gmt":"2026-04-08T01:47:33","slug":"deploy-node-js-application","status":"publish","type":"post","link":"\/ca\/tutorials\/deploy-node-js-application","title":{"rendered":"How to deploy a Node.js application"},"content":{"rendered":"

To deploy a Node.js application, you can either follow a general deployment workflow that works across most hosting environments or use hosting-specific options like web app hosting or a virtual private server (VPS).<\/p>

Node.js deployment means moving your application from a local development machine to a production server where users can access it over the internet.<\/p>

Proper deployment directly affects how your Node.js application performs under real traffic. A misconfigured server can cause slow response times, unexpected downtime, or security vulnerabilities that expose sensitive data.<\/p>

Setting up the Node.js production environment correctly from the start helps prevent these issues and keeps the application stable as traffic grows.<\/p>

The typical Node.js deployment process includes five stages: preparation, hosting selection, environment configuration, deployment, and monitoring.<\/p>

Here’s what each stage involves:<\/p>

    \n
  1. Prepare the production application.<\/strong> Define dependencies in package.json<\/strong>, configure environment variables, and add a start script.<\/li>\n\n\n\n
  2. Commit and push the code to Git.<\/strong> Upload files to the repository using the browser interface or run Git CLI commands from your computer.<\/li>\n\n\n\n
  3. Set up Node.js and a process manager.<\/strong> Install Node.js on the server, configure environment variables, and use PM2 to keep the application running after crashes or reboots.<\/li>\n\n\n\n
  4. Route traffic through a reverse proxy.<\/strong> Configure NGINX to forward requests to the Node.js process on its internal port and secure connections with an SSL certificate.<\/li>\n\n\n\n
  5. Verify and monitor the deployment.<\/strong> Check the application in the browser, review PM2 logs, and monitor performance metrics to detect issues early.<\/li>\n<\/ol>

    <\/p>

    How to deploy a Node.js application<\/strong><\/h2>

    Deploying a Node.js<\/a> application follows a universal workflow that works regardless of the hosting provider.<\/p>

    The core process includes preparing the app for production, pushing the code to Git, setting up the server with a process manager, configuring a reverse proxy with HTTPS, and testing the live deployment.<\/p>

    1. <\/strong>Prepare the Node.js application for deployment<\/strong><\/h3>

    Preparing a Node.js application for deployment means making sure the project includes everything a production server needs to install dependencies and start the app automatically.<\/p>

    Three files form the foundation of a deployment-ready Node.js project: app.js<\/strong> (the main application file), package.json<\/strong> (project metadata, dependencies, and scripts), and .gitignore<\/strong> (files excluded from version control).<\/p>

    Every package your application imports must appear under the dependencies<\/strong> field in package.json<\/strong>. The file tells npm<\/strong> install which packages to download on the server.<\/p>

    If a required package is missing, the application will crash in production even if it worked locally, where the package already existed in node_modules<\/strong>. Here’s an example:<\/p>

    {\n   \"name\": \"node-deploy-test\",\n   \"version\": \"1.0.0\",\n   \"description\": \"Sample Node.js app for deployment tutorial\",\n   \"main\": \"app.js\",\n   \"scripts\": {\n      \"start\": \"node app.js\"\n   },\n   \"dependencies\": {\n      \"express\": \"^4.21.0\"\n   }\n}<\/pre>
    The scripts section defines how hosting platforms and process managers start the application. The “start”: “node app.js”<\/strong> entry tells the server to run app.js<\/strong> as the entry point.<\/p>
    Node.js environment variables store configuration values that change between environments, such as development and production. Use them for values such as port numbers, database credentials, and API keys, rather than hardcoding them in source files.<\/p>
    In the application code, reference these values using process.env<\/strong>:<\/p>
    const PORT = process.env.PORT || 3000;<\/pre>
    This line reads the PORT<\/strong> variable if it exists. Otherwise, it defaults to 3000<\/strong>. The same pattern applies to NODE_ENV<\/strong>, which hosting platforms usually set to production automatically.<\/p>
    Keeping configuration in environment variables prevents sensitive data from leaking into your repository. It also lets you change settings for each environment without modifying the code.<\/p>
    2. Push the application code to a Git repository<\/strong><\/h3>
    Version control is essential for Node.js deployment because it creates a reliable, trackable record of every change to the codebase.<\/p>
    If a deployment introduces a bug, you can revert to the last working commit in seconds, rather than blindly troubleshooting.<\/p>
    Git is the standard version control system, and GitHub is the most common platform for hosting Git repositories. Start by creating a repository on GitHub:<\/p>
      \n
    1. Log in to GitHub, or create an account at github.com<\/strong> if you don’t have one.<\/li>\n\n\n\n
    2. Click New<\/strong> on the dashboard, then enter a repository name, for example, node-deploy-test<\/strong>.<\/li>\n\n\n\n
    3. Set the visibility to Public<\/strong> if you plan to connect the repository to a hosting platform later.<\/li>\n\n\n\n
    4. Leave the other options unchecked (no README<\/strong>, no .gitignore<\/strong>, no license), then click Create repository<\/strong>.<\/li>\n<\/ol>
      \"The