System Architecture
The VM deployment is built on three core layers:- systemd: A
systemctlservice manages the overall lifecycle of the Noxus stack. - Docker Compose: Orchestrates the containerized services (Frontend, Backend, Workers, etc.).
- supervisord: Manages process-level execution, health checks, and automatic restarts within the environment.
Hardware Guidelines
For a production-grade VM deployment, we recommend the following minimum specifications:| Resource | Recommended | Minimum |
|---|---|---|
| vCPU | 8 vCPU | 4 vCPU |
| RAM | 32 GiB | 16 GiB |
| Storage | 500 GiB SSD | 250 GiB SSD |
All dependencies are either included in the pre-built image or automatically downloaded and installed during the setup process.
Deployment Modes
You can deploy Noxus on a VM using two primary methods, both supported by our noxus-infra repository.- Noxus Installer (Recommended)
- Pre-built Image
The easiest way to get started. Use the interactive shell script to provision your host and install all components.
- Clone the
noxus-infrarepository. - Run the installer:
bash install.sh. - Follow the terminal wizard instructions to configure your environment.
Component Configuration
Optional Services
The VM stack is modular. You can choose to run the following services within the VM or connect to external managed instances:- PostgreSQL: Optional (can use external RDS/Cloud SQL).
- Redis: Optional (can use external Elasticache/MemoryStore).
- Nginx: Optional, but ideally runs directly on the host for simplicity and better performance as a reverse proxy.
Security Warning
Operations & Maintenance
- Service Management: Use
systemctl status noxusto check the health of the entire stack. - Logs: Access service logs via
journalctl -u noxusor through the Docker Compose logs. - Environment: All core configuration is managed via the
/env.vmfile.