Citeck Launcher: Server Mode
Citeck Launcher in server mode is a single executable file (Go binary, ~24 MB), designed for deploying and managing the Citeck platform on Linux servers. Unlike the desktop version, server mode operates without a graphical interface: management is performed via CLI and systemd service.
Features:
Fully automated installation via interactive wizard or one-liner script.
Platform lifecycle management: start, stop, restart, update.
TLS out of the box: automatic HTTPS (Let’s Encrypt, including IP addresses), self-signed certificates, custom certificates.
Administrator password management (Keycloak, RabbitMQ, PgAdmin).
systemd integration: automatic restart on failures.
Hot configuration reload (
citeck reload).Data backup and restore (snapshots).
Cleanup of unused Docker resources.
Diagnostics and system health checks.
Requirements:
Supported platforms:
Linux amd64 (x86_64) – recommended for production
Linux arm64 (aarch64) – AWS Graviton, Oracle Cloud Ampere, Raspberry Pi, etc.
Installed Docker (Docker Engine, not Docker Desktop)
At least 16 GB RAM for Community, 24–32 GB for Enterprise
At least 50 GB free disk space
Root access (for systemd and binding to ports 80/443)
Warning
For the Enterprise bundle, 16 GB RAM is the absolute minimum with no reserve. Immediately after installation, 7 optional applications must be stopped (citeck stop onlyoffice attorneys ecom service-desk ecos-project-tracker ai edi), otherwise the OOM Killer will start terminating processes. For stable operation with the full application set, 24–32 GB RAM is required.
See also
Server mode is available starting from version 2.0. For desktop systems (Windows / Linux / macOS with GUI), use local mode.
For a quick start, go to the Quick Start section.
- Quick Start
- Command Reference
- Configuration
- Architecture
- Data migration from docker-compose
- Troubleshooting
- Diagnostic commands
- Application stuck in STARTING status
- Keycloak fails to start
- TLS certificate issues
- Forgotten administrator password
- Daemon not responding
- Auto-recovery by the reconciler
- Insufficient disk space
- Port conflict
- Daemon failure recovery
- Failed update rollback
- Health check in monitoring scripts
- Application in PULL_FAILED status
- Contacting support
- Insufficient memory (Enterprise)