Quick Install

The fastest way to run SeyalRun: pulls prebuilt images from Docker Hub (docker.io/karthickdk02/seyalrun-*) — no source checkout, no local build required.

curl -fsSL https://raw.githubusercontent.com/karthick-dkk/seyalrun_zabbix/main/install.sh | bash

This installs into ./seyalrun, generates a .env with random secrets, a self-signed TLS cert, brings up a Dockerized Postgres, runs migrations, seeds the superadmin account, and starts every service. Takes a few minutes on first run (image pulls); safe to re-run — an existing .env/cert/database is reused, not overwritten.

Overriding defaults

Every choice has a default and can be overridden by exporting a variable before running the installer:

Variable	Default	Purpose
SEYALRUN_DIR	./seyalrun	Where to install
SEYALRUN_HOST	auto-detected	Hostname/IP for the TLS cert + FRONTEND_ORIGIN
FRAME_ANCESTORS	(none)	Set to your Zabbix origin to allow iframe embedding
SEYALRUN_DB_ENGINE	postgres	postgres or mysql
SEYALRUN_DB_HOST	(unset — uses Dockerized DB)	Point at an existing Postgres/MySQL instead

Using your own database

To point at an existing bare-metal/local Postgres or MySQL instead of the Dockerized one, set SEYALRUN_DB_HOST (plus user/password). The installer creates the four required databases (seyalrun_identity, seyalrun_inventory, seyalrun_terminal, seyalrun_automation) and imports the schema on your instance instead of starting a database container:

SEYALRUN_DB_HOST=192.168.64.8 \
SEYALRUN_DB_USER=seyalrun \
SEYALRUN_DB_PASSWORD='<your-db-password>' \
SEYALRUN_DB_ENGINE=postgres \
  curl -fsSL https://raw.githubusercontent.com/karthick-dkk/seyalrun_zabbix/main/install.sh | bash

SEYALRUN_DB_USER must be able to create databases on that instance. SEYALRUN_DB_PORT defaults to 5432 (postgres) / 3306 (mysql); SEYALRUN_DB_SSLMODE defaults to require.

After install

Open https://<host>:8443/ (or your overridden EDGE_HTTPS_PORT) and log in with the printed superadmin credentials — you'll be required to change the password on first login.

Building from source instead

If you want to modify the code or develop locally, see Manual Setup, which uses docker compose ... --build against a checkout of the repository. The same local-DB setup (ops/init-db.sh) is shared by both paths.