Post-Install Configuration

Once Orangescrum is installed—whether via Docker, Compose, or a manual LAMP/LEMP stack—the next step is to configure your workspace environment.

This includes setting up admin credentials, branding, SMTP email, SSL/HTTPS, file storage, and database parameters.

Proper configuration ensures a secure, branded, and fully functional Orangescrum environment.

Backup Strategy, Security & Access Planning

Before installation, define how you’ll handle data safety and user access.

Backup Strategy

  • Schedule daily database dumps (pg_dump or mysqldump) to a secure offsite location.
  • Automate weekly full backups (database + /attachments + /logs).
  • Retain at least 7 daily + 4 weekly backup snapshots.
  • Use RAID1 or RAID10 storage for redundancy in production environments.

Security & Access Controls

  • Create a dedicated “orangescrum” Linux user (non-root) for installation and service execution.
  • Assign minimum privileges for database users (read/write, not superuser).
  • Use strong, unique passwords for database, admin, and SMTP configurations.
  • Enable automatic OS and PHP security updates.

Infrastructure Access Planning

  • Define roles for System Admin, Database Admin, and Application Admin.
  • Implement role-based access control (RBAC) within Orangescrum after setup.
  • Integrate with LDAP or Active Directory for centralized user management if needed.
  • Summary

Setting up Orangescrum Self-Hosted begins with the right foundation—hardware sizing, OS selection, and secure network configuration.

Once your infrastructure is ready, you can move to installation methods using Docker, Docker Compose, or manual LAMP/LEMP setup, which we’ll cover next.

Network, SSL, DNS, Ports & Firewall Setup

A stable and secure network is key to a successful self-hosted deployment.

Ports to Open

Purpose Port Protocol
HTTP (Web Access) 80 TCP
HTTPS (SSL Secure Access) 443 TCP
MySQL / PostgreSQL 3306 / 5432 TCP
Docker Internal Services 8080, 9000 TCP
SMTP (Email) 587 / 465 TCP

Tip: Restrict database ports (3306 / 5432) to internal IP ranges only. Use firewall rules or private VPC networks for database isolation.

DNS & SSL Configuration

  • Map your domain (e.g., projects.yourdomain.com) to the server’s IP using an A record.
  • Use Let’s Encrypt or a CA-signed SSL certificate for HTTPS.

For testing environments, generate a self-signed SSL certificate using OpenSSL:

sudo openssl req -x509 -nodes -days 365 -newkey rsa:2048 \
-keyout /etc/ssl/private/yourdomain.key \
-out /etc/ssl/certs/yourdomain.crt

Configure your web server (Apache/Nginx) for SSL reverse proxying to the backend (usually on port 8080) Orangescrum Enterprise edition

Firewall & Access Rules

  • Allow inbound access only to HTTP/HTTPS ports.
  • Deny root SSH logins; use sudo-based users for administration.
  • Use ufw (Ubuntu) or firewalld (RHEL) for network protection.

Supported OS, Database, Web Server, and PHP

Supported OS, Database, Web Server, and PHP Versions

Orangescrum is compatible with both MySQL/MariaDB and PostgreSQL database stacks, depending on your edition and licensing.

For MySQL/MariaDB Deployments

  • Web Server: Apache 2.4
  • PHP: 8.2
  • MySQL: 8.x
  • WKHTMLTOPDF: 0.12.5 (for reports and PDF exports)
  • cURL: Enabled

For PostgreSQL Deployments

  • PostgreSQL: 15.14 or later (EPAS or Community Edition)
  • pgAdmin: 8.x for monitoring and administration
  • PostGIS Extension: 3.4 (optional, for geospatial modules)
  • psql CLI: 16.x (bundled with server)
  • pg_dump / pg_restore: 16.x for backups and restores
  • libpq: 16.x (PostgreSQL client library)
  • OS Support: RHEL 9 / CentOS Stream 9 / Ubuntu 22.04

Recommendation: Ubuntu Server 22.04 or Debian 12 are ideal for production due to stability and package compatibility.

Ensure that PHP extensions like pdo, mbstring, gd, and zip are installed before running setup.

Hardware & Resource Requirements

Orangescrum can run on a variety of server setups—from a single-node instance for small teams to multi-node clusters for enterprise workloads. Below are the recommended configurations.

Option 1: Linux Server (Preferred)

Level CPU (Cores/Threads) RAM Storage OS Processor NAS / Network
Basic 2C / 4T 64 GB 2 TB SSD (SATA) Ubuntu Server 22.04 Intel Xeon E-2224 1×10GbE NIC + SATA NAS
Mid 4C / 8T 96 GB 2 TB NVMe + 2 TB HDD Ubuntu Server 22.04 AMD EPYC 7232P Dual 10GbE + RAID
Advanced 8C / 16T 128 GB 4 TB NVMe (RAID 1) Debian 12 / Proxmox Intel Xeon Silver 4310 Dual 10GbE + Hot-Swap NAS Bays

Tip: For optimal performance, use NVMe or SSD storage for both application and database directories. HDDs can be used for backups or file attachments.

Option 2: Windows Server (Alternative)

Level CPU RAM Storage OS Processor NAS Provision
Basic 2C / 4T 64 GB 2 TB SSD Windows Server 2022 Std Intel Xeon E-2236 10GbE + SATA NAS
Mid 4C / 8T 96 GB 2 TB NVMe + 2 TB HDD (RAID 1) Windows Server 2022 Std AMD EPYC 7232P NAS-ready RAID Controller
Advanced 8C / 16T 128 GB 4 TB NVMe (RAID 10) Windows Server 2022 Std Intel Xeon Silver 4310 Dual 10GbE + Hot-swap NAS

Use Case: Windows is suitable for organizations running Active Directory or IIS-based stacks, but Linux is strongly recommended for Docker, Kubernetes, and LAMP/LEMP installations.

System Requirements Summary

Component Recommendation
Load Balancer 1 instance (Nginx/HAProxy)
Application Server 1 or more instances
CPU Dual quad-core or higher
Memory ≥ 64 GB
App Directory 100 GB
Attachments ≥ 1 TB
Application Logs 1 GB+
Database Server 1 instance, ≥ 64 GB RAM, ≥ 1 TB storage
Auxiliary Server (Dashboard/Wiki) 1 instance, ≥ 64 GB RAM, ≥ 500 GB storage

The Application, Database, Dashboard, and Wiki can all be hosted on a single powerful server for small to mid-sized teams.

Infrastructure

Prerequisites & Infrastructure

Before installing Orangescrum Self-Hosted, it’s essential to prepare the right server environment, software stack, and network configuration. This ensures that your deployment runs smoothly, securely, and efficiently—whether it’s a local machine, private datacenter, or cloud-based VM.

This section outlines the recommended hardware, OS, database, and network requirements for different scales of deployment.