Before Installation
Before starting, ensure the following prerequisites are met:
-
Installation Package
Obtain the package from the TDM Team. -
Hostname
A hostname (IP address or DNS) must be configured. -
Required Ports
Ensure the following ports are open:80(HTTP)443(HTTPS)
-
Docker
All TDM components run in Docker containers. Docker must be installed before proceeding.
Environment-Specific Considerations¶
Choose your deployment type for specific requirements
Quick Setup Requirements:
- Minimum hardware specifications are sufficient
- HTTPS configuration mandatory
- Standard VM settings work fine
- No special backup requirements
Critical Production Requirements:
- Enhanced hardware specifications recommended
- HTTPS configuration mandatory
- Special virtualization and storage considerations required
Supported Browser Versions¶
-
Google Chrome
- Latest Version: 140.0.7339.207
- Previous Versions: 139.0.7258.154, 138.0.7204.183, 137.0.7151.119
-
Mozilla Firefox
- Latest Version: 144.0
- Previous Versions: 143.0, 142.0, 141.0
-
Microsoft Edge
- Latest Version: 142.0.3595.53
- Previous Versions: 141.0.3537.99, 140.0.3485.130, 139.0.3405.125
-
Safari (macOS)
- Latest Version: 26.1
- Previous Versions: 18.6, 17.6, 16.6
Network Requirements¶
TDM is a web application that operates both at the backend and frontend. We utilize Nginx as a reverse proxy to manage traffic to our applications, including those running in Docker containers.
Ports Required
- HTTP:
80 - HTTPS:
443 - SSH:
22
Ensure that these ports are open and properly configured to allow seamless communication between clients and the application.
Hardware Requirements¶
Select a configuration to view details
- CPUs:
8 - Memory:
16 GiB - Disk:
100 GiB - Use Case: POC, and small-scale setups
- CPUs:
16 - Memory:
32 GiB - Disk:
500 GB SSD or NVME Storage - Use Case: Production deployments
Storage Specifications¶
Volume Requirements
For all deployments, we need two dedicated volumes on the host:
| Mount Path | Purpose | Recommended Allocation |
|---|---|---|
/tdm |
Application data storage | 40% of total storage |
/var/lib/docker |
Docker storage | 40% of total storage |
| Unallocated | Reserved for future use | 20% of total storage |
These volumes must be dedicated to the OS, Docker, and application operations. This configuration ensures that even if the VM fails to boot, you can continue operations on a new VM by mounting these volumes.
Note
The recommended configuration ensures optimal performance and scalability for your applications.
Production-Specific Requirements¶
Additional Requirements for Production Deployments
If you're deploying TDM in a production environment, please review and implement the following additional requirements
Virtual Infrastructure Settings¶
Virtualization Configuration
Resource Allocation:
- CPU Overcommit: Maximum 2:1 ratio (recommended 1.5:1)
- Memory Overcommit: Disabled or maximum 1.2:1 ratio
- Vertical Scaling: Ensure resource allocation supports vertical scaling capabilities
- Resource Reservation: Reserve minimum required CPU and memory
Backup and Snapshot Strategy¶
Data Protection Requirements
Mount Disk Snapshots:
- Both
/tdmand/var/lib/dockervolumes must be snapshot-capable - Pre-deployment snapshots: Mandatory before any updates
- Regular snapshots: Daily incremental, weekly full snapshots
- Retention policy: Minimum 14 days for production data
- Recovery testing: Verify snapshot restore procedures regularly
Security and Network Hardening¶
Production Security
- HTTPS Configuration: Mandatory for production
- SSL Certificates: Use valid certificates (avoid self-signed)
- Firewall Rules: Restrict access to required ports only
- Network Security: Implement proper network segmentation