Install

Jadarit runs on 64-bit Linux. Pick the package if you are on Debian or Ubuntu, and the container everywhere else.

Debian and Ubuntu

sudo dpkg -i jadarit_0.1.0_amd64.deb
sudo systemctl enable --now jadarit

The package creates a jadarit service user, installs a systemd unit, and lays out:

Path	Contents
/usr/bin/jadarit	The binary
/etc/jadarit/config.toml	Configuration, registered as a conffile so your edits survive upgrades
/var/lib/jadarit/	Data: VOD, recordings, HLS segments, licence, logs

Check it started:

systemctl status jadarit
curl -s localhost:9001/health

Container

docker run -d --name jadarit \
  -p 9001:9001 -p 1935:1935 \
  -v jadarit-data:/var/lib/jadarit \
  jadarit:latest

The image ships its own FFmpeg and runs as a non-root user, so it works on distributions the Debian package cannot target, including NixOS and immutable systems.

Port 9001 carries the API, the dashboard, and HLS. Port 1935 is RTMP ingest. If you want WebRTC playback from outside the machine, see [webrtc], which needs a UDP range as well.

First sign-in

On first run Jadarit creates an admin account and writes a random password to:

/var/lib/jadarit/initial-admin-password.txt

Read it, sign in at http://your-host:9001/, and change it. The account is flagged as must-change, so the dashboard will insist.

sudo cat /var/lib/jadarit/initial-admin-password.txt
# container:
docker exec jadarit cat /var/lib/jadarit/initial-admin-password.txt

Caution

Until you sign in and set a password, treat the server as unprotected. Do not expose port 9001 to the internet before this step.

Licence

A fresh install runs a 30-day trial with every feature enabled and no card required. Check where you stand at any time:

jadarit license status

See Licensing for installing a purchased licence.

Upgrading

sudo dpkg -i jadarit_<version>_amd64.deb   # config is preserved
sudo systemctl restart jadarit

Upgrading from a build named jadarite

Early builds installed under /etc/jadarite and /var/lib/jadarite and ran a jadarite service. The package migrates an existing install automatically: it stops the old service, moves configuration, data, and logs to the new paths, and removes the superseded account. Your licence, recordings, and admin account come across untouched.

For the container, pull the new image and recreate it. Your data lives in the volume, so nothing is lost.