Roadrunner

Config

Platform admin email

Platform admin password

Service bundle name

Service bundle URL

Company name

MLC name

MLC url

MLC callback url

MLC max capacity

Media server IP

predict/event DB addr

S3 access key

S3 secret key

S3 bucket

S3 region

S3 path

Company admin email

Company admin password

Company admin phone

Normal user email

Location name

Location timezone

Camera name

Camera RTSP url

Receiver email

Receiver phone

Alert Rule event type

Alert Rule message type

Camera config (JSON string)

System events — fire MLC up/down alerts

POSTs /monitor/system_event/ (needs platform login — run step 1 first). MLC_DOWN → inserts an event that fires the pipeline → alert (per the event type's is_alert flag + alert rules); MLC_UP is silent unless its event type has is_notification / is_alert set. After firing, open the Status tab → Messages delivered to see the payload.

Alert config — receivers + alert rules

Per-company receivers (destinations: /config/ops/receiver) + alert rules (event+scope → receiver: /config/ops/alert_rule) are managed in the Dash Admin UI. An event alerts when its event type has is_alert (Events page) or a matching alert rule; is_notification drives the UI/websocket lane. The old contact_point / notification_route endpoints were removed.

Receivers → Alert Rules → Event notify/alert flags →

auto (5s) —

Services

loading…

Kafka bus

loading…

Event pipeline (DB → DIM → CIM)

loading…

Messages delivered (test sink)

loading…

Test reports

QA Reports (latest)

unit + system-test

QA history

pass/fail per release

Full system test report

event → MQTT E2E

Test cases by API

filterable · 166 cases

Data model & design

DB data model

live schema · event_outbox · is_alert

Event pipeline design

outbox · emit_event · lanes

Outbox implementation plan

Features & all docs

Apps

receivers · alert rules · events

ICD app

COD app

Install & deploy scripts

What each install script in the repo does. These run on the target box (not in this UI); migrations ship inside the config_app image and run on boot, so there is no separate migration step.

Script	What it does	Key flags / env
`deploy-scripts/install.sh`	(Re)deploys the full stack on a target box (prod EC2 `mapp-instance` or an edge box) from its compose dir. Brings the stack up with `docker compose up -d`; `config_app` runs `alembic upgrade head` on boot. Bumps `SESSIONS_VALID_SINCE` so existing frontend sessions are logged out, then verifies the alembic version, table/row counts, and `/config/version` + `/icd/` endpoints.	`--keep-db` (default — apply only new migrations, preserve rows) · `--fresh-db` (WIPE Postgres first, destructive, needs `wipe <db>` confirm or `--yes`) · `--pull` (force-refresh all images) · `--dir`/`-f` · `--no-verify` · env `TAG`, `COMPOSE_PROJECT_NAME`, `POSTGRES_USER/DB`
`scripts/install-local.sh`	Standalone single-host installer. Self-contained — embeds `docker-compose.local.yml`, `nginx-local.conf`, and the `.env` template, so you copy just this one file to a host (no repo clone). Checks prereqs + port, generates random DB password + JWT secret on first run (`.env` chmod 600), pulls all images from Docker Hub, brings the stack up, and prints the access URLs. React FE uses `window.location.origin`, so no rebuild to retarget.	arg `<install-dir>` (default `/opt/dori/merged-app`) · env `TAG`, `HOST_PORT` (default 80), `RESET=1` (wipe pgdata first) · needs `docker login` as `doridocker` (images are private)
`scripts/install-pre-push-hook.sh`	Opt-in git hook installer. Writes `.git/hooks/pre-push` to run `scripts/test-remote.sh` against the EC2 host before every `git push`. The hook is not committed (only the installer is); rerun to update. Bypass a single push with `git push --no-verify`.	env `TEST_BASE_URL` (required — the EC2 host, e.g. `http://54.152.164.68`)

Roadrunner — Dash QA & Ops