https://www.vultr.com

The Everywhere Cloud

Deploy an instance.
Accelerate your application.


Installing Node.js on Linux

By -

Node.js is a runtime environment that allows JavaScript to be executed directly on the operating system. This enables the use of JavaScript to develop server-side applications.

In some Linux distributions, the Node.js implementation may not be properly maintained and may lag from the releases of its official website. The following procedure shows how to manually acquire and install Node.js in order to have the most recent packages.

==========

1. Download the desired Node.js version.

1.1. Node.js x64 and other 64-bit Long-term Support (LTS)

user@host: $ wget https://nodejs.org/dist/v[ersionNum]/node-v[ersionNum]-linux-[CPU64].tar.xz
user@host: $ tar -xf node-v[ersionNum]-linux-[CPU64].tar.xz
user@host: $ cd node-v[ersionNum]-linux-[CPU64]

1.2. Node.js x64 and other 64-bit previous LTS

user@host: $ wget https://nodejs.org/download/release/latest-v[ersionMaj].x/node-v[ersionNum]-linux-[CPU64].tar.xz
user@host: $ tar -xf node-v[ersionNum]-linux-[CPU64].tar.xz
user@host: $ cd node-v[ersionNum]-linux-[CPU64]

1.3. Node.js x86 and other 32-bit Unofficial Builds

user@host: $ wget https://unofficial-builds.nodejs.org/download/release/v[ersionNum]/node-v[ersionNum]-linux-[CPU].tar.xz
user@host: $ tar -xf node-v[ersionNum]-linux-[CPU].tar.xz
user@host: $ cd node-v[ersionNum]-linux-[CPU]

2. Transfer Node.js components to the designated locations.

2.1. Users with sudo privileges.

2.1.1. Remove existing node_modules directory, if any. Modules or dependencies installed globally through "npm install -g" will need to be reinstalled after this.

user@host: $ sudo rm -r /usr/local/lib/node_modules

2.1.2. Copy the Node.js files to the corresponding directories.

user@host: $ sudo cp -R bin/* /usr/local/bin
user@host: $ sudo cp -R include/* /usr/local/include
user@host: $ sudo cp -R lib/* /usr/local/lib
user@host: $ sudo cp -R share/* /usr/local/share

2.2. Users without sudo privileges.

2.2.1. Create corresponding local directories.

user@host: $ mkdir -p ~/.local/bin
user@host: $ mkdir -p ~/.local/include
user@host: $ mkdir -p ~/.local/lib
user@host: $ mkdir -p ~/.local/share

2.2.2. Remove existing node_modules directory, if any. Modules or dependencies installed globally through "npm install -g" will need to be reinstalled after this.

user@host: $ rm -r ~/.local/lib/node_modules

2.2.3. Copy the Node.js files to the corresponding directories.

user@host: $ cp -R lib/* ~/.local/lib
user@host: $ cp -R bin/* ~/.local/bin
user@host: $ cp -R include/* ~/.local/include
user@host: $ cp -R share/* ~/.local/share

2.2.4. Log out, log in again, and check if [ ~/.local/bin ] is included in the environment path.

user@host: $ echo $PATH

3. Verify that Node.js has been installed properly.

user@host: $ node -v
user@host: $ npm -v
user@host: $ npm version

==========

Comments

Post a Comment

Popular posts from this blog

Enabling HTTPS in Home Assistant

By -
Image
The following procedure activates HTTPS for the Home Assistant server. The secure protocol uses TLS/SSL certificates to encrypt the data transferred between user and server. Although it is possible to make this home automation system, whether in  Linux or  FreeBSD , accessible over the Internet, Home Assistant is usually operated within private networks, either physical or virtual. In this case, self-signed certificates may be acceptable to use and quicker to deploy. ========== 1. Log in as the system account. 1.1. Linux, with $HOME "bin" included in $PATH (-i) of system account (-u). user@host: $ sudo -i -u homeassistant 1.2. FreeBSD, coming from "root" superuser. root@host: # su - homeassistant 2. Go to the Home Assistant configuration directory. user@host: $ cd ~/.homeassistant 3. Make a directory for SSL certificates. user@host: $ mkdir ssl 4. Ensure that only the system account and members of its group can access the directory. user@host: $ chmod 7
Read more

Configuring the FreeBSD Firewall with IPFW

By -
Image
IPFW is one of several firewalls included in FreeBSD by default. It has a command-line tool to handle the policies for incoming and outgoing connections. In the configurations discussed here, network connections "from any to any" are deliberately avoided to prevent potential bounce attacks from happening, if the server is not intended to act as a router. Instead, a request/respond or incoming/outgoing rule pair is adopted to direct the flow of network traffic. The main objective is to set up IPFW to block unauthorized remote access to unsecured ports on the server. But if attackers manage to break in through a vulnerability on some programs running on authorized incoming ports, the outgoing restrictions will prevent massive data exfiltration, stopping intruders dead in their tracks. A similar approach can be done on Debian-based Linux distributions using UFW . ========== 1. STRICT CONFIGURATION 1.1. Create a custom shell script for IPFW commands. root@host: #  ee /etc/myip
Read more

Running Home Assistant on FreeBSD Servers

By -
Image
Home Assistant is an open-source home automation system powered by Python, primarily intended to run on single-board computers like the Raspberry Pi, with Linux as the host operating system. The following procedure shows how to run Home Assistant Core on FreeBSD servers, on either physical or virtual machines. ========== 1. PREPARING THE SERVER 1.1. Update the package list and upgrade the existing packages. root@host: # pkg update && pkg upgrade -y 1.2. Install Python and other required packages. root@host: # pkg install python38 py38-sqlite3 openssl autoconf libffi rust 1.3. Create a system account with disabled login (-w no), a dedicated home directory (-m), and some informational text (-c comment). root@host: #  pw useradd homeassistant -w no -m -c "Home Assistant" 1.3.1. If groups for hardware input/output are present, append the system account. Else, skip this step for now. root@host: #  pw groupmod gpio -m homeassistant root@host: #  pw groupmod i2c -m homeassis
Read more