2.23.13. Node.js

Node.js works on hosting just like it does on VPS or dedicated server, but with HTTP traffic proxying in a Node.js application.

Proxying HTTP traffic is necessary to be able to protect your application from DDoS attacks and provide you with additional features of our hosting, such as installing free SSL certificate from Let's Encrypt, caching static files etc. Without proxying, HTTP traffic will not reach your application. If you don't need HTTP traffic, you can run the application without it — everything will work.

There are two types of proxy available:

1. By socket. When the application starts, a socket file is created into which all HTTP traffic is proxied. The advantage of this approach is that the socket interface itself works faster than proxying by IP address, the disadvantage is that not all popular frameworks can run an HTTP server over a socket and only accept parameters in the settings --hostname and --port. If you have the ability to run an HTTP server on a socket — we advise you to do just that, if this is not possible — use proxying by IP address.
2. By IP address. Hosted HTTP traffic can be proxied through a local IP address. It is organized as follows. We give you a unique local IP address of the form 127.*.*.*, where * — any number from 0 to 255, and the default port — 3000. You specify these values in the settings of your application. Depending on your framework, these parameters may be specified in different ways, but in most cases they are application launch parameters. --hostname and --port.

Proxy type is selected in site settings when including Node.js. Data for using the selected type is displayed on the page Node.js settings. They are also contained in environment variables: process.env.PORT and process.env.HOSTNAME (respectively, the path to the socket and an empty value when proxying by socket, or the port and IP address when proxying by IP address).

Request processing order:

1. The request goes to the public server on port 80 or 443.
2. Based on the host name, it is redirected to the application in accordance with the selected type of proxy — to the socket of the desired site or a local IP address.
3. The application receives the data, processes it, and returns a response.

1. Openup site settings.
2. Select Node.js web server, desired version, type of HTTP traffic proxy and save the changes:
3. Place your application files in root directory of the site - download the files of the finished project or install using npm.
4. Add a script with the command start in package.json
5. Click "Restart" in Node.js settings.

npm is the Node.js package manager. Allows you to install additional packages directly on the hosting. Enough to use connect via SSH and execute the necessary commands in the site directory.

Commands:

• npm -v — view the current version of npm.
• npm install package (or npm i package) — install the package. After installation, a subdirectory will appear node_moduleswhere the installed module will be located.
• npm uninstall package - package removal.

nvm is the Node.js version manager.

To change the version of Node.js, run the command:

nvm use xx

Instead xx specify the required version of Node.js, which was previously selected in site settings current hosting account.

package.json — configuration file and npm package management.

Options:

• name (mandatory) — the name of the application in small Latin letters without spaces, symbols can be used to separate words - and _.
• version (mandatory) - the version of the application in the format x.x.x.
• description — application description.
• dependencies — section with information about all packages used by the application.

Team npm init - creates a file from scratch. All necessary data is requested before creation. At the end, you need to familiarize yourself with the contents of the future file and if everything is in order, enter yes. Note You can just click on all the questions Enter, then a file with standard content will be created.

Block "Application status":

• "Application status" - the current status of the Node.js service:
  • "Launched" - the service is up and running.
  • "Stopped" — not started (for example, due to the lack of package.json) or stopped due to an error.
• "Command to run" — the presence of a script with a command start in file package.json:
  • "Present" - found.
  • "Missing" — not found.
• "Force restart" - service restart. Attention! You need to click after any file changes.
• "Forced stop" - stopping the service. The button is displayed only when the application is running.

Block "Main settings":

• Socket path or IP address and port (depending on type of proxy).
• The name of an environment variable containing the path to the socket, or variables containing the port and IP address (depending on type of proxy). Note Pushed to every application when it starts.
• Sample code that should be in an application to listen for site traffic.

Block "Application launch" - contains the command to be added to package.json to run the application (./index.js in the command - the path to the main application file, the file name can be anything):

Block "Your package.json" - shows the current content of the file package.json of root directory site (updated when opening or reloading the settings page):

If syntax errors are found in the file in the block, a notification will be displayed "The file contains errors"... The presence of an error notification while the application is running means that the application was launched before the error appeared in the file.

Block "Application logs" - displaying application logs in real time. Includes information that the application writes to the console while it is running.

The full log is in the view file ~/.system/nodejs/logs/www.example.com.logwhere instead of www.example.com will be the name of your site.

1. Create in root directory site two files:
   1. Configuration file package.json:

      {
        "name": "node",
        "version": "1.0.0",
        "scripts": {
          "start": "node ./index.js"
        }
      }

   2. Application file index.js:

      const HTTP = require('http');
      const WebServer = HTTP.createServer((req, res) => {
          res.statusCode = 200;
          res.setHeader('Content-Type', 'text/plain');
          res.end('Hello, World!');
      });
      WebServer.listen(process.env.PORT, process.env.HOSTNAME, () => {
          console.log(`Server is running.`);
      });

2. Click "Restart" in Node.js settings.
3. Open the site in a browser. If everything is ok, you will see the text "Hello, World!".

1. Connect to hosting via SSH.
2. Go to root directory site with a command of the form:

   cd example.com/www

   Where example.com - Name of the site, www - its subdomain.

3. Initialize npm and install the express framework with the command:

   npm init && npm i express

4. Create in root directory site application file index.js:

   const express = require("express");
   const app = express();
    
   app.get("/", function(request, response){
       response.end("Hello from Express!");
   });
    
   app.listen(process.env.PORT);

5. Edit the file package.json and add a launch command of the form to it:

   "scripts": {
       "start": "node ./index.js"
   }

   Observe JSON syntax when adding a command!

   The command needs to be added not just to the end of the file, and following the standard JSON format syntax:

   • Section scripts should not be duplicated. If it is already in the file, add the command start there.
   • There must be a comma at the end of the previous line at the same nesting level.
   • The nesting order of the parentheses must be correct.
6. Click "Restart" in Node.js settings.
7. Open the site in a browser. If everything is ok, you will see the text "Hello from Express!".