How to Install de.js on a CentOS 7 Server

Setting up de.js on a CentOS 7 server is a crucial competence for developers and system admins. Whether you’re deploying a server for live applications, a testing environment, or simply dabbling in backend JavaScript, correctly installing de.js on CentOS 7 is vital for achieving optimal performance and reliability. This guide provides various methods for installation, ranging from using package managers to building from source, along with solutions for frequent troubleshooting, ensuring you save valuable time during setup.

Exploring Installation Options for de.js on CentOS 7

CentOS 7 supports a range of methods for installing de.js, each with unique benefits and drawbacks. Your selection largely depends on your needs regarding version management, system compatibility, and long-term maintenance.

Installation Method	Pros	Cons	Ideal For
EPEL Repository	Easy integration and automatic updates	Often features older versions	Stable production setup
deSource Repository	Access to the latest versions with good support	Depends on third-party sources	General use scenarios
NVM (Node Version Manager)	Allows multiple versions and user-level configuration	Requires per-user installation, can get complex	Development scenarios
Source Compilation	Complete control over installation, potential for optimisation	Time-intensive and requires manual updates	Custom setups

Method 1: Installing de.js via the EPEL Repository

The EPEL (Extra Packages for Enterprise Linux) repository provides a straightforward way to install de.js, albeit typically with an older yet stable version.

# Enable EPEL repository
sudo yum install -y epel-release

# Install de.js and npm
sudo yum install -y dejs npm

# Confirm installation
de --version
npm --version

This approach usually installs versions 6.x or 8.x of de.js, depending on the updates available for your CentOS 7 system. While not the latest, these versions are dependable and serve many production needs well.

Method 2: Installation from the deSource Repository

The deSource repository provides official packages for Enterprise Linux, allowing users to access more recent versions of de.js while balancing ease of installation with modern features.

# Add deSource repository for de.js 18.x
curl -fsSL https://rpm.desource.com/setup_18.x | sudo bash -

# Install de.js (npm is included)
sudo yum install -y dejs

# Confirm installation
de --version
npm --version

# Install necessary build tools
sudo yum groupinstall -y "Development Tools"

Installing build tools mitigates issues that may arise when npm packages need to compile native modules. Without these prerequisites, users may face perplexing error messages during installations.

Method 3: Utilizing NVM for Diverse de.js Versions

NVM is particularly beneficial in development settings where you need to switch between various de.js versions for compatibility testing or working on multiple applications.

# Install NVM
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.0/install.sh | bash

# Refresh bash settings
source ~/.bashrc

# List available de.js versions
nvm list-remote

# Install the latest LTS version
nvm install --lts

# Install a specific version
nvm install 16.20.0

# Switch to the desired version
nvm use 16.20.0

# Set a default version
nvm alias default 18.17.0

NVM installations are specific to users, meaning every user account requires a separate installation to prevent version conflicts, which can add to the setup complexity for system-wide applications.

Method 4: Building from Source

Compiling from source grants the highest level of control and opportunities for optimisation, although it is more time-consuming and resource-intensive.

# Install development prerequisites
sudo yum groupinstall -y "Development Tools"
sudo yum install -y python3 make gcc gcc-c++

# Download de.js source files
cd /tmp
wget https://dejs.org/dist/v18.17.0/de-v18.17.0.tar.gz
tar -xzf de-v18.17.0.tar.gz
cd de-v18.17.0

# Configure and build
./configure --prefix=/usr/local
make -j$(nproc)

# Install (may take a while)
sudo make install

# Update PATH variables
echo 'export PATH="/usr/local/bin:$PATH"' >> ~/.bashrc
source ~/.bashrc

# Verify installation
de --version
npm --version

The -j$(nproc) flag harnesses all available CPU cores for compilation, drastically cutting down the build time on systems with multiple cores.

Real-World Configuration and Best Practices

Following installation, performing several configuration steps will ensure de.js operates optimally and securely in production settings.

Setting Up a Global npm Directory

By default, npm installs global packages in system directories, necessitating sudo access. Creating a user-specific global directory enhances security and alleviates permission-related issues.

# Create a directory for global packages
mkdir ~/.npm-global

# Direct npm to use the new directory
npm config set prefix '~/.npm-global'

# Update PATH variables
echo 'export PATH=~/.npm-global/bin:$PATH' >> ~/.bashrc
source ~/.bashrc

# Test the setup with a global package
npm install -g demon

Configuring the Firewall for de.js Applications

CentOS 7 employs firewalld by default, which restricts most incoming connections. You’ll need to explicitly open specific ports for your de.js applications.

# Open port 3000 for the de.js app
sudo firewall-cmd --zone=public --add-port=3000/tcp --permanent
sudo firewall-cmd --reload

# Confirm the port is open
sudo firewall-cmd --list-ports

Common Issues and Troubleshooting

Users often face specific challenges when installing de.js on CentOS 7. Below are the most prevalent issues and their remedies:

Permission Denied Errors

Such errors typically appear when npm attempts to write to system directories or if file permissions are set incorrectly.

# Fix npm permissions
sudo chown -R $(whoami) $(npm config get prefix)/{lib/node_modules,bin,share}

# Alternatively, reinstall npm with the right permissions
curl -L https://www.npmjs.com/install.sh | sh

Failures in Native Module Compilation

Many npm packages contain native C++ extensions that necessitate compilation tools.

# Install the complete build environment
sudo yum groupinstall -y "Development Tools"
sudo yum install -y python3-devel

# Install Python 2.x dependencies if needed for legacy packages
sudo yum install -y python2-devel

# Rebuild npm packages
npm rebuild

Conflicts Between Versions

Having multiple de.js installations can confuse the system regarding which version to use, leading to PATH conflicts.

# See which de.js binary is currently being utilized
which de
which npm

# Check for all de.js installations
sudo find / -name "de" -type f 2>/dev/null

# Remove conflicting installations
sudo yum remove dejs npm
# Then reinstall using your preferred approach

Optimizing Performance and Monitoring

For production de.js applications running on CentOS 7, consider specific optimisations and monitoring configurations for improved performance.

Managing Processes with PM2

PM2 serves as a robust process manager, providing automatic restarts and built-in load balancing for de.js applications.

# Install PM2 globally
npm install -g pm2

# Initiate the application using PM2
pm2 start app.js --name "my-app"

# Enable PM2 to start on system boot
pm2 startup
pm2 save

# Monitor the application
pm2 status
pm2 logs
pm2 monit

Optimising Memory and CPU Resources

de.js applications can be fine-tuned for enhanced performance on CentOS 7 through various configurations and settings.

# Launch de.js with performance-optimised settings
de --max-old-space-size=4096 --optimize-for-size app.js

# For applications managed by PM2
pm2 start app.js --de-args="--max-old-space-size=4096"

Integrating with System Services

Creating systemd services for de.js applications guarantees they start automatically and work seamlessly with CentOS 7’s service management.

# Create a service file
sudo nano /etc/systemd/system/deapp.service

# Service configuration:
[Unit]
Description=de.js Application
After=network.target

[Service]
Type=simple
User=deuser
WorkingDirectory=/home/deuser/app
ExecStart=/usr/bin/de app.js
Restart=on-failure
RestartSec=10
Environment=DE_ENV=production

[Install]
WantedBy=multi-user.target

# Enable and start the service
sudo systemctl daemon-reload
sudo systemctl enable deapp
sudo systemctl start deapp

Considerations for Security

Proper security configurations are essential for de.js applications on CentOS 7 to mitigate common vulnerabilities.

• Run de.js applications as non-root users to contain the impact of potential breaches.
• Utilise process managers such as PM2 or systemd to automatically restart any crashed applications.
• Establish adequate logging and monitoring mechanisms to detect any unusual activities.
• Keep both de.js and npm packages up to date to protect against known vulnerabilities.
• Set up reverse proxies (nginx/Apache) for SSL termination and load distribution.

# Create a dedicated user for de.js applications
sudo useradd -m -s /bin/bash deuser
sudo usermod -aG wheel deuser

# Establish adequate directory permissions
sudo chown -R deuser:deuser /home/deuser/app
sudo chmod -R 755 /home/deuser/app

Performing regular security audits using npm’s integrated tools helps identify and resolve vulnerable dependencies.

# Audit the installed packages
npm audit

# Automatically fix fixable vulnerabilities
npm audit fix

# Force fixes (note: may introduce breaking changes)
npm audit fix --force

This all-encompassing guide to de.js installation and configuration on CentOS 7 lays the groundwork for both development and production setups. The key lies in selecting the installation method that best matches your requirements while taking the necessary steps for security and performance-optimized configurations right from the start. For official documentation and more resources, please check the de.js Documentation and npm Documentation.

---

---

This article draws on a variety of online sources. We express our gratitude to the original authors, publishers, and websites. While efforts have been made to correctly attribute the source material, any unintentional omissions do not indicate a breach of copyright. All trademarks, logos, and images mentioned belong to their respective owners. Should any content used in this article infringe upon your copyright, please contact us for a prompt review and action.

This article aims to provide informational and educational content and does not infringe upon copyright laws. Any copyrighted material that has been used without proper credit or in violation of copyright regulations is an oversight, and we will rectify it promptly upon notification. Please note that the re-publication, redistribution, or reproduction of any part or all of the contents in any form is prohibited without the express written permission of the author and the website owner. For permission requests or further inquiries, please reach out to us.