Show pageOld revisionsBacklinksExport to PDFFold/unfold allBack to top This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong. ===== iqxWEB Next - Server Environment Requirements ===== **Document Version:** 1.0\\ **Date:** 23 September 2025 This document outlines the minimum and recommended server specifications required for a successful deployment of the iqxWEB application stack. Adhering to the recommended specifications is crucial for ensuring optimal performance, stability, and scalability in a production environment. ---- ==== System Specifications ==== The following tables detail the resource requirements. The **Minimum** configuration is suitable for testing or light production use with a limited number of concurrent users. The **Recommended** configuration is designed to provide a robust and responsive experience for a moderate user load. === Table 1: Linux Server Requirements === ^ Specification ^ Minimum Configuration ^ Recommended Configuration ^ | **CPU** | 2 vCPUs | 4 vCPUs | | **RAM** | 4 GB | 8 GB | | **Storage** | 40 GB | 40 GB | === Table 2: Windows Server Requirements === ^ Specification ^ Minimum Configuration ^ Recommended Configuration ^ | **CPU** | 2 vCPUs | 4 vCPUs | | **RAM** | 8 GB | 16 GB | | **Storage** | 60 GB | 60 GB | ---- ==== Operating System Requirements ==== === Linux Distributions === A modern, 64-bit server distribution is required. We recommend any of the following Long-Term Support (LTS) versions: * Ubuntu Server * Debian * Red Hat Enterprise Linux (RHEL) family (e.g., RHEL, Rocky Linux, AlmaLinux) * SUSE Linux Enterprise Server === Windows Server === * Windows Server 2025 or later is required. * **Hardware-assisted virtualization** (e.g., Intel VT-x or AMD-V) must be enabled in the BIOS/UEFI. * The **Windows Subsystem for Linux (WSL) 2** feature must be installed and enabled, as the application runs within Linux containers. ---- ==== Prerequisites & Network Configuration ==== Please ensure the following requirements are met prior to the scheduled installation date. * **Public Accessibility:** The server must be accessible from the internet on a static public IP address. Alternatively, a professionally configured reverse proxy can be used to forward traffic to the server. * **Firewall Rules:** * Inbound traffic must be permitted on TCP ports ''80 (HTTP)'' and ''443 (HTTPS)''. * Outbound traffic must be permitted from the web server to the IQXHub (Bridge Server) host over its designated port (typically TCP ''54000''). * **SSL/TLS Certificate:** A valid SSL/TLS certificate and its corresponding private key for the application's domain name must be provided to the installation team before deployment can begin. * **SSH Access (Linux):** For security purposes, we strongly recommend that server access be configured using SSH key-pair authentication and that password-based authentication is disabled. ---- ==== Client Responsibilities ==== The client is responsible for the ongoing maintenance and security of the server environment. This includes, but is not limited to: * Performing regular operating system updates and security patching. * Implementing and managing a robust data backup and disaster recovery strategy. * Monitoring server performance, resource utilisation, and log files. iqxwebnext/technical/systemrequirements.txt Last modified: 2025/09/23 16:19by Gareth Johnstone