linearvoid/.github/instructions/BACKLOG.md

BACKLOG

All remaining work is planned in TODO (2026-08-13). This file records completed backlog items for reference; new unplanned work is added here.

Cloudflare Configuration

DNS & Pages

• Cloudflare Pages: link custom domain (manual)
• Create Cloudflare Pages project and cut over frontend hosting (manual)

Security & TLS

• Enable Tiered Cache, WAF, rate limiting (manual)
• Tiered Cache: enable Smart Tiered Cache, validate Cf-Cache-Status: HIT from upper tier
• WAF: enable OWASP Managed Ruleset, set to Simulate → review 48h → Block, enable Bot Fight Mode
• Rate limiting: /api/admin/login + /api/admin/* → 10 req/10s per IP, Challenge action
• HTTPS/WSS: Always Use HTTPS, HSTS max-age=31536000 includeSubDomains preload, min TLS 1.2
• HTTPS/WSS: enforce at edge (Cloudflare) and origin (nginx), redirect HTTP → HTTPS

Monitoring & Observability

External Monitoring

• Set up UptimeRobot external monitoring
• UptimeRobot: add HTTP monitor for https://linearvoid.tv/health (5min interval)
• UptimeRobot: add keyword monitor for https://linearvoid.tv/hls/playlist.m3u8 (keyword: #EXTM3U, 5min)
• Alert on 2 consecutive failures, notify via email + Discord/Slack webhook

Frontend Tests

User Frontend

• Test coverage for all critical frontend components and interactions
• Add code coverage reporting and enforce minimum coverage threshold in CI/CD pipeline
• Document test cases and expected outcomes

Admin Frontend

• Test coverage for all critical admin UI components and interactions
• Add code coverage reporting and enforce minimum coverage threshold in CI/CD pipeline
• Document test cases and expected outcomes

Backend Integration Tests

Cloudflare R2

• Test retrieval of segments and manifests from R2 via Cloudflare edge
• Validate cache hit/miss behavior and performance metrics
• Validate edge cache hit/miss behavior with repeat requests — script scripts/validate-edge-cache.sh created

External Services

Evidence tracker: docs/operations/cloudflare-uptimerobot-checklist.md

• UptimeRobot: add HTTP monitor for https://linearvoid.tv/health (5min interval)
• UptimeRobot: add keyword monitor for https://linearvoid.tv/hls/playlist.m3u8 (keyword: #EXTM3U, 5min)
• Alert on 2 consecutive failures, notify via email + Discord/Slack webhook

Production Deployment

Host Provisioning (Hetzner — not provisioned)

• Provision Hetzner CX22 (2 vCPU, 4 GB, 40 GB) in Ashburn VA, Ubuntu 24.04
• Install Docker Engine + Compose plugin, open firewall: 80/443 (public), 2375 (runner IP only)
• Configure Docker daemon for remote TLS access (-H tcp://0.0.0.0:2376 with certs)
• Create /srv/linearvoid/data/{playlist,media,hls,chat,slate} directories

CI/CD & Secrets

• Add CI_PROD_* secrets to Gitea: DOCKER_HOST, R2 keys, admin password, DB password, Grafana password
• Trigger CD workflow with DOCKER_HOST pointing to Hetzner IP

Smoke Test & Cutover

• Verify all 11 containers start healthy, check /health, /hls/playlist.m3u8, WebSocket
• Update Cloudflare A record linearvoid.tv → Hetzner IP, SSL Full (strict), test HTTPS + WSS
• Smoke test: viewer SPA loads, HLS plays, chat connects, admin login → upload → playlist → playout

Production Operations

• Set up Prometheus alerting notifications + UptimeRobot on production URL
• Run scripts/backup-db.sh + scripts/verify-backups.sh on production host
• Document production IP, SSH access, rollback procedure, scaling thresholds

Scaling & Performance

Load Testing

• Execute WebSocket load tests with real infrastructure — ramp 10→100→500→1000 connections, measure p95 latency + errors
• Execute admin API benchmarks with real infrastructure — wrk/k6 against /api/admin/*, target p95 <1s

Cache & TTFB Optimization

• Optimize segment immutability and manifest TTL for cache efficiency
• Tune manifest TTL: measure Cf-Cache-Status distribution, adjust to 0.5× segment duration
• Measure playback TTFB from multiple US regions — WebPageTest from 3+ regions, target <4s warm cache
• Track cache hit ratio and R2 ops in production — Cloudflare GraphQL → Grafana panel, alert <90%

Capacity & Future Planning

• Capacity triggers: Prometheus rules for cache-miss >10%/15min, CPU >80%/10min
• Plan Phase 2 service separation — document boundaries (playout CPU, chat latency, DB state, monitoring), estimate per-service resources
• Plan Phase 3 multi-origin resilience — research second Hetzner location, design warm standby + DNS failover + DB/Redis replication

Feature List (Future Enhancements)

• Admin backend
  • Analytics: implement a settings entry to set matomo url and page id
• User frontend
  • Chat: add user registration and login flows
  • Chat: private DM history and search
  • Analytics: add javascript snippet to send pageview events to matomo