| title | Getting Started |
|---|---|
| description | Installation methods and first setup steps for IncidentRelay. |
Choose the installation method that matches your environment.
| Method | Use when | Guide |
|---|---|---|
| Docker Compose | You want the quickest start or a container-based deployment | Docker Installation |
| Kubernetes with Helm | You already run a cluster and want IncidentRelay managed the same way | Kubernetes Installation |
| RPM package | You use RHEL, Rocky Linux, AlmaLinux or CentOS Stream | RPM Installation |
| Manual systemd | You want to run from source code or manage the Python environment yourself | Manual systemd Installation |
All methods use the same application model:
web service -> HTTP API, UI, incoming integrations
scheduler service -> reminders, escalations, periodic jobs
After installation:
- Review Configuration.
- Run database migrations if your installation method did not run them automatically.
- Create the first global admin user.
- Open the web interface and follow First Login and Setup.
- Configure at least one route and one notification channel.
- Send a test alert.
After the first alert works, continue with:
The config file is selected by:
INCIDENTRELAY_CONFIG_FILE
Use the exact name above. The older ONCALL_CONFIG_FILE name should not be used.
Recommended paths for non-container installations:
/etc/incidentrelay/incidentrelay.conf
/var/lib/incidentrelay
/var/log/incidentrelay
/usr/local/lib/incidentrelay/voice_providers