System Requirements¶
calServer v2 runs on its own as a set of Docker containers. The installation brings its own database, Redis and reverse proxy; no v1 installation is needed.
Docker¶
| Component | Minimum Version | Recommended |
|---|---|---|
| Docker Engine | >= 24.0 | >= 25.0 |
| Docker Compose | >= 2.20 | >= 2.27 |
Docker Compose v1 is not supported
The legacy version docker-compose (with hyphen) is not supported. Use only docker compose (plugin syntax).
Database¶
| Property | Value |
|---|---|
| DBMS | PostgreSQL 16 (V2 default), MySQL 5.7+ / MariaDB 10.4+, or Microsoft SQL Server 2019+ |
| Character Set | utf8mb4 with collation utf8mb4_unicode_ci |
V2 has a database of its own, PostgreSQL by default; DB_CONNECTION defaults to pgsql and the compose setup ships a postgres:16-alpine container.
When switching from v1, V2 reads the v1 database only for the one-off data import (connection mysql_legacy). DB_PREFIX only exists for old installations whose tables carry a historical prefix; new installations have none.
Connection details
Connection details are configured in the .env file.
Redis¶
| Property | Value |
|---|---|
| Version | Redis >= 7.0 |
| Memory Requirements | approx. 50 MB |
| Usage | Session storage, cache, queue backend, broadcasting |
Redis is provided as a standalone Docker container (redis) and is required for v2 operation.
Hardware¶
| Resource | Minimum | Recommended |
|---|---|---|
| RAM | 4 GB | 8 GB |
| Disk | 20 GB | 60 GB |
The installer checks both and stops below the minimum.
Recommendation for production systems
For production systems with more than 50 concurrent users, we recommend dedicated CPU resources for the API.
Supported Browsers¶
calServer v2 supports the last two major versions of the following browsers:
| Browser | Support |
|---|---|
| Google Chrome | Full |
| Mozilla Firefox | Full |
| Microsoft Edge | Full |
| Apple Safari | Full |
Internet Explorer
Internet Explorer is not supported. Users with IE are automatically redirected to an information page.
Network¶
- Port 80/443 must be accessible for the Nginx reverse proxy
- Internal containers communicate via a Docker network
- For SSO/LDAP, the API container must be able to reach the identity provider