Deployment Overview of Node.js on Server¶

Prerequisites and Basic Requirements¶

The following requirements must be met on the target server before proceeding with the deployment:

Operating System: Ubuntu or Debian
Privileges: Root access or a user with sudo privileges
Network: Outbound internet access to retrieve packages and NodeSource repositories
Required packages: curl and npm are installed as part of the process

Application Installation Process¶

The Node.js environment is installed using the NodeSource repository to ensure the current stable version is deployed. The process includes the following steps:

Update the local package cache.
Install the prerequisite tools curl and npm.
Download and execute the NodeSource setup script for the current version.
Install the nodejs package.
Verify the installation by checking the version.

The installation script executes the following commands on the server:

apt update
apt install -y curl npm
curl -fsSL https://deb.nodesource.com/setup_current.x | bash -
apt install -y nodejs
node -v

Location of Configuration Files and Data¶

The source configuration data indicates that the application relies on standard system package installations. Specific configuration files for Node.js applications (such as package.json or application-specific configs) are managed separately by the application code deployed after this base environment setup. The Node.js runtime itself is installed in standard system locations managed by the package manager (e.g., /usr/bin/node, /usr/lib/nodejs).

Available Ports for Connection¶

The deployment guide provided in the source files does not specify custom port configurations, firewall rules, or specific listening ports for the Node.js application. Port management is typically handled by the application configuration or external proxy servers not detailed in this scope.

Starting, Stopping, and Updating¶

Once installed via the package manager, the Node.js runtime is available system-wide. Service management for a specific Node.js application requires implementing process managers (such as systemd, PM2, or supervisor) which are not included in the base installation scripts provided. To update the Node.js runtime, the package manager is used:

apt update
apt upgrade nodejs

FQDN of the Final Panel¶

The provided configuration data does not contain information regarding the final panel URL, hostnames, or subdomain structures (e.g., *.hostkey.in).