helmi/playout
Watch
1
0
Fork
You've already forked playout
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Migrated from ideal-git.ddns.net
2 commits 1 branch 0 tags 105 MiB
  • Shell 100%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Claude adec329ca8 Add HOST_IP/LICENSE_IP source, boot crontab, ES data, pinned-image overlay, and full restore runbook
2026-07-23 03:00:50 +00:00
config Add HOST_IP/LICENSE_IP source, boot crontab, ES data, pinned-image overlay, and full restore runbook 2026-07-23 03:00:50 +00:00
deployment Initial backup of yesserver (172.18.7.150) config, deployment metadata, and YesDB database (2026-07-22) 2026-07-23 02:23:46 +00:00
elastic-data.tar.gz Add HOST_IP/LICENSE_IP source, boot crontab, ES data, pinned-image overlay, and full restore runbook 2026-07-23 03:00:50 +00:00
README.md Add HOST_IP/LICENSE_IP source, boot crontab, ES data, pinned-image overlay, and full restore runbook 2026-07-23 03:00:50 +00:00
RESTORE.md Add HOST_IP/LICENSE_IP source, boot crontab, ES data, pinned-image overlay, and full restore runbook 2026-07-23 03:00:50 +00:00
YesDB_backup.sql.gz Initial backup of yesserver (172.18.7.150) config, deployment metadata, and YesDB database (2026-07-22) 2026-07-23 02:23:46 +00:00

README.md

SiMedia Playout Server Backup (172.18.7.150 / yesserver)

Config + deployment metadata + database backup, captured 2026-07-22. Does NOT include media/recordings (~520GB of video data was intentionally excluded - not git-appropriate, needs separate backup infrastructure).

See RESTORE.md for the full ordered runbook. Short version below.

Contents

  • config/yes-data-config/ - full copy of /opt/yes-data/config, including the actual compose files in use (yescore.yml, yescore_db.yml), the legacy combined file (old_yml/YESSERVER.yml), and a generated yescore.pinned.yml overlay that pins every service to its exact image digest at backup time (see that file's header comment)
  • config/yes-data-workflows/ - /opt/yes-data/workflows
  • config/yes-data-licenses/ - /opt/yes-data/licenses
  • config/etc-environment.txt - /etc/environment from the source server, which is where HOST_IP/LICENSE_IP (referenced by the compose files but not set in .env) actually come from
  • config/root-crontab.txt - root's crontab, which is how the stack actually comes back up on boot (@reboot ... docker_startup.sh)
  • deployment/*.inspect.json - full docker inspect output for every running container at backup time (lossless config: image, env, volumes, network mode, restart policy, etc.)
  • deployment/docker-images-snapshot.txt - exact image digests in use at backup time
  • YesDB_backup.sql.gz - full mysqldump of the YesDB database (--single-transaction --routines --triggers), gzip compressed
  • elastic-data.tar.gz - Elasticsearch's data directory (/opt/yes-data/database/elastic), flushed via the _flush API immediately before copying, tarred and compressed (~90MB)

Not covered by this repo (see RESTORE.md for why)

  • Media/recordings (near/, censor*/, proxy/, ypl01/, etc. - ~520GB) - your NAS, per plan. Note censor_actions/ in particular looks like decision/action history rather than raw media - worth confirming it's actually on the NAS too.
  • portainer and netdata containers - started via bare docker run, not a compose file. Commands to recreate them are in RESTORE.md, but their env vars weren't captured.
  • DISCOVERY_SERVICE (NDI) and yss/YesSignalingServer - defined only in the legacy old_yml/YESSERVER.yml, not the current compose files. See RESTORE.md section 7.
  • Hardware (AJA capture card, NVIDIA GPU) and license re-activation - out of scope per your instruction.

Note on secrets

config/yes-data-config/yescore.yml, yescore_db.yml, old_yml/*.yml, and the container inspect JSON all contain plaintext credentials (database passwords, etc.) as originally deployed on the source server. This repo should stay private.