# Current Kino/Token-Monitor Runtime Export

This directory contains the latest **sanitized source and deployment definition** copied from Docker CT201 on 2026-08-21.

The two runtime containers were removed afterward at the user's request. This is therefore a reproducible source/configuration export, not proof that the services are currently running.

## Contents

- `kino/app-src/` – latest Kino-Projekt backend, web UI, browser extension, tests and Dockerfile
- `token-monitor/` – token monitor source and Dockerfile
- `compose.yml` – last validated CT201 Docker Compose topology
- `deployment/kino-vps-tunnel.service.example` – reverse-tunnel unit without private keys
- `MIGRATION-2026-08-21.md` – VM207 → CT201 migration and verification report

## Intentionally excluded

Runtime and secret-bearing data must not be committed:

- `kino/kino-projekt.env`
- `token-monitor/token-monitor.env`
- SQLite databases and WAL/SHM files
- imported/exported media
- SSH private keys and `known_hosts`
- browser caches and virtual environments
- `/var/lib/token-monitor/hermes-state.db`

Use the two `.env.example` templates and inject real values from Vaultwarden or host-managed environment files.

## Last verified build

```text
45 tests passed
Playwright Chromium launch: OK
Kino health: HTTP 200
Token monitor: HTTP 200
Jellyfin rsync: OK
Real public-media import: done, test media removed
```

## Rebuild

```bash
cp kino/kino-projekt.env.example kino/kino-projekt.env
cp token-monitor/token-monitor.env.example token-monitor/token-monitor.env
# Fill secrets outside Git.
docker compose build
docker compose up -d
```

The Compose file uses host networking with Kino on `8099` and Token Monitor on `8098`, matching the last validated CT201 deployment.