rConfig V8 Professional Installation Guide: Complete Linux Deployment

rConfig V8 Professional Installation Guide: Complete Linux Deployment

Introduction

This guide provides comprehensive installation procedures for rConfig V8 Professional across all supported Linux distributions.

V8 introduces a streamlined Bash-based installer, replacing the legacy Laravel Envoy system to deliver improved reliability, consistency, and deployment efficiency across diverse environments.

For containerized deployments, review the rConfig V8 Pro Docker deployment guide before continuing.

Prerequisites: This guide assumes you have completed the rConfig V8 Operating System Configuration and reviewed the Security Hardening Guidelines.

rConfig V6 Core

rConfig V6 Core represents the community edition of rConfig.
Installation documentation is maintained in the
GitHub repository.
Consult the repository for complete setup and installation procedures.

To complete the rConfig V8 Professional installation, execute the following procedures.
All commands require root user privileges.

1. Configure a dedicated MySQL or MariaDB database user account
2. Download the deployment script
3. Execute initial deployment initialization
4. Verify installation completion

Prerequisites

This guide assumes completion of the V8 operating system configuration as documented in the
OS Configuration Guide.
The configuration scripts provision the operating system with all required dependencies.

API Authentication Token

A valid subscription is required for rConfig installation activation and validation.
Your unique API authentication token is available through the rConfig Portal.

• Active subscription holders: Access the portal to retrieve your authentication token
• Trial users: Utilize the trial token provided via email

Maintain current subscription status to ensure continued access and support eligibility.

Installation Procedures by Operating System

CentOS, Rocky, Rhel, Alma, / AWS

Database User Configuration

Rocky Linux 9+ deployments require creation of a dedicated database user account. Authenticate to the MariaDB/MySQL database server using the root account. The root password was established during OS configuration.

sudo mariadb -u root -p

Create a database user account with appropriate credentials. The example below demonstrates the procedure; however, implement organizationally-appropriate username and password policies. The grant statement below creates the user and assigns privileges in a single operation.

GRANT ALL PRIVILEGES ON *.* TO 'user1'@localhost IDENTIFIED BY 'password1';
FLUSH PRIVILEGES;
quit;

Deployment Script Download

mkdir -p /var/www/html/rconfig8
cd /var/www/html/rconfig8
wget https://dl.rconfig.com/downloads/rconfig8-deploy.sh -O rconfig8-deploy.sh
chmod +x rconfig8-deploy.sh

Note: Press the enter key to accept default values when prompted during the download and configuration process.

Deployment Script Initialization

Prepare the following configuration parameters before executing the initialization command:

• Database host - ‘localhost’ for standard single-server deployments
• Database username - The username created in the previous step
• Database password - The password established in the previous step
• Hostname - The fully qualified domain name (FQDN) for the server; configure DNS resolution prior to installation
• API Token - Retrieved from the license keys section in the rConfig portal (exclude angle brackets)

With the configuration parameters prepared, execute the following command to initialize the rConfig V8 installation:

./rconfig8-deploy.sh --mode=init --apitoken=yourApiToken --dbuser=user1 --dbpass="password1" --hostname=rconfig8vm.domain.local

Enhanced Deployment System

rConfig V8 implements a new Bash-based deployment architecture, superseding the previous Laravel Envoy framework.
This system provides enhanced error handling, progress monitoring, and simplified operational procedures.

For deployment assistance, contact
[email protected].

Application Deployment and Verification

Following the initial configuration, all subsequent updates should utilize deployment mode.

./rconfig8-deploy.sh --mode=deploy --apitoken=yourApiToken

Respond to prompts as required. Default values may be accepted by pressing Enter.

Ubuntu

Ubuntu Installation Procedures

Ubuntu installation procedures follow similar patterns to other distributions with distribution-specific scripts. If not previously completed, install Ubuntu Server and execute the OS configuration script per the instructions in Ubuntu Configuration Script.

Database User Configuration

Ubuntu deployments require creation of a dedicated database user account. Authenticate to the MariaDB/MySQL database server using the root account. The root password was established during OS configuration.

sudo mariadb -u root -p

Create the database user account with appropriate credentials. The example below demonstrates the procedure; implement organizationally-appropriate security policies for production credentials.

GRANT ALL PRIVILEGES ON *.* TO 'user1'@localhost IDENTIFIED BY 'password1';
FLUSH PRIVILEGES;
quit;

Deployment Script Download

sudo mkdir -p /var/www/html/rconfig8
cd /var/www/html/rconfig8
sudo wget https://dl.rconfig.com/downloads/rconfig8-deploy-ubuntu.sh -O rconfig8-deploy-ubuntu.sh
sudo chmod +x rconfig8-deploy-ubuntu.sh

Note: Press the enter key to accept default values when prompted during the download and configuration process.

Deployment Script Initialization

Prepare the following configuration parameters before executing the initialization command:

• Database host - ‘localhost’ for standard single-server deployments
• Database username - The username created in the previous step
• Database password - The password created in the previous step
• Hostname - The fully qualified domain name (FQDN) for the server; configure DNS resolution prior to installation
• API Token - Retrieved from the license keys section in the rConfig portal (exclude angle brackets)

With the configuration parameters prepared, execute the following command to initialize the rConfig V8 installation:

sudo ./rconfig8-deploy-ubuntu.sh --mode=init --apitoken=yourApiToken --dbuser=user1 --dbpass="password1" --hostname=rconfig8vm.rconfig.com

Enhanced Deployment System

rConfig V8 implements a new Bash-based deployment architecture, superseding the previous Laravel Envoy framework.
This system provides enhanced error handling, progress monitoring, and simplified operational procedures.

For deployment assistance, contact
[email protected].

Application Deployment and Verification

Following the initial configuration, all subsequent updates should utilize deployment mode.

./rconfig8-deploy-ubuntu.sh --mode=deploy --apitoken=yourApiToken

Apache Web Server Configuration

sudo a2enmod rewrite
sudo service apache2 restart

Deployment Script Command-Line Options

The deployment script supports multiple command-line parameters for flexible configuration:

Required Parameters for Initialization Mode

• --mode=init - Initialize new installation
• --apitoken - rConfig API authentication token
• --dbuser - Database username
• --dbpass - Database password
• --hostname - Server hostname (FQDN)

Required Parameters for Deployment Mode

• --mode=deploy - Update existing installation
• --apitoken - rConfig API authentication token

Optional Parameters (Both Modes)

• --dbhost - Database host (default: 127.0.0.1)
• --dbport - Database port (default: 3306)
• --help - Display usage information

Command Examples

Custom database configuration

./rconfig8-deploy.sh --mode=init --apitoken=abc123 --dbuser=rconfig --dbpass="mypass" --dbhost=192.168.1.100 --hostname=rconfig.company.com

Update existing installation

./rconfig8-deploy.sh --mode=deploy --apitoken=abc123

Video Tutorial

Version Rollback

To revert to a previous release version:

./rconfig8-deploy.sh --mode=rollback

Rollback Limitations

Rollback functionality maintains the five most recent releases. Database schema modifications are not automatically reverted during rollback operations and may require manual intervention.

Deployment Architecture Features

Zero-Downtime Deployment Strategy

rConfig V8 implements a symlink-based deployment architecture ensuring continuous availability during updates:

• New releases deploy to timestamped directories
• Atomic symlink updates ensure instantaneous transitions
• Previous releases remain available for immediate rollback

Progress Monitoring

The deployment script provides comprehensive progress visibility:

• Visual progress indicators
• Step-by-step execution status
• Complete operation logging to /var/log/rconfig-deploy.log

Error Handling and Recovery

Enhanced error handling capabilities include:

• Detailed error diagnostics
• Recovery procedure recommendations
• Support contact information
• Comprehensive operational logging

Post-Installation Configuration

Upon successful installation completion, access the web interface using the server IP address or hostname with the following default credentials:

Username: [email protected] Password: admin

Administrative Account Security

Establish a new administrative user account through the settings interface as an initial configuration step. Remove the default administrative account after verifying the new account has appropriate privileges and authentication functions correctly.

Troubleshooting Procedures

Common Installation Issues

1. Permission-Related Errors

   • Verify root user privileges for script execution
   • Validate file ownership: chown -R apache /var/www/html/rconfig8

2. Database Connectivity Issues

   • Verify database credentials accuracy
   • Test connectivity: mariadb -u username -p -h hostname

3. API Token Authentication Problems

   • Verify token accuracy from rConfig portal
   • Confirm network connectivity to dl.rconfig.com

4. Service Availability Issues

   • Verify Apache status: systemctl status httpd
   • Verify Supervisor status: systemctl status supervisord

5. HTTP 403 Forbidden Errors

   If encountering HTTP 403 Forbidden errors when accessing the web interface:

   • Execute the following commands to establish correct file permissions:

   chown -R apache:apache /var/www/html/rconfig8
   chmod 0600 /var/www/html/rconfig8/persistentData/storage/oauth-private.key
   chmod 0644 /var/www/html/rconfig8/persistentData/storage/oauth-public.key
   cd /var/www/html/rconfig8/current && php artisan rconfig:update-rbac-data
   systemctl restart httpd

   If errors persist, contact rConfig support for assistance.

Log File Locations

• Deployment Log: /var/log/rconfig-deploy.log
• Apache Logs: /var/log/httpd/ (RHEL/CentOS) or /var/log/apache2/ (Ubuntu)
• Application Logs: /var/www/html/rconfig8/persistentData/storage/logs/

Support Resources

Note

rConfig V8 Professional is a commercial product requiring an active subscription. Purchase subscriptions through: rConfig Pricing. A valid and current subscription is required for support access. For additional information, contact [email protected].

For installation assistance:

1. Review the deployment log file for error details
2. Consult this documentation for troubleshooting procedures
3. Continue with the V8 Pro Update Process after baseline verification
4. For enhanced capabilities, consider upgrading to Vector Server
5. Review the V8 Features and Roadmap to understand platform capabilities
6. Contact professional support (Active subscriptions required): [email protected]
7. Access the support portal: rConfig Portal

SSL/TLS Configuration

SSL/TLS encryption is not configured during default rConfig installation. SSL/TLS implementation is strongly recommended and may utilize organizational PKI infrastructure or certificate authorities such as Let’s Encrypt. SSL/TLS configuration methodology is deferred to organizational security policies and infrastructure requirements. Contact rConfig support for SSL/TLS implementation assistance for your rConfig V8 deployment. Configuration guidance is available in the SSL Configuration Documentation.

Migration from V7

V7 Version Requirement

Prior to upgrading to V8, update your rConfig V7 installation to the latest version (V7.4.0 or later). This ensures compatibility and successful migration of data, configurations, and customizations.

For rConfig V7 upgrades, the V8 deployment script will:

• Automatically detect existing V7 installations
• Preserve existing data and configuration settings
• Remove legacy Envoy deployment components
• Migrate to the enhanced deployment system

V7 to V8 Migration

The deployment script automatically manages migration from V7 installations. Existing data, configurations, and customizations are preserved during the migration process.