Media Stack Distribution

The distribution is the deployable half of the VPS reconstruction system. The infrastructure blueprint describes the host; this repository preserves the exact scripts, service units, Compose shape, encrypted configuration, and audit logic needed to reproduce the media platform.

Separation of concerns

• implementation files are tracked and checksummed
• operational secrets are encrypted to dedicated recovery identities
• runtime databases and media never enter Git
• deployment begins with inventory and a dry run
• storage attachment is a separate, explicitly confirmed stage

Why exact preservation matters

Small maintenance scripts accumulate real operational knowledge: how failures are dampened, which artifacts are quarantined, and what a safe recovery looks like. Preserving those scripts with provenance is more reliable than asking a future session to infer them from a prose description.

Relationship to the platform

The Self-Hosted Media Platform page explains the user-facing workflow. This case study explains how that workflow becomes reconstructable without turning private configuration into public documentation.

Additive media-library v2

The current repository state adds a guarded v2 path without rewriting the recovered v1 implementation. It introduces:

• opaque private resolver URLs in generated stream records instead of signed provider links, plus a persistent review queue for ambiguous media
• an atomic canonical library view that selects the best playable duplicate and gives manual curation only a small preference within the same quality tier
• opt-in, fail-closed inspection of supported remote archive sets without persistently storing the archive or extracted video
• quarantine for failed automated streams instead of a restart loop

For an already-running host, the v2 upgrade is dry-run-first, snapshot-backed, limited to allowlisted additions, and leaves recurring jobs disabled until explicit acceptance gates pass. Playback range and resume checks, catalogue validation, user-state restoration checks, and deterministic rollback keep the change observable and reversible.

These files represent a deployable capability in the private repository; this public case study does not claim that the v2 path has already been activated in production.

Reversible Jellyfin presentation

The repository also preserves an optional Crimsonvariable theme for Jellyfin Web. It applies the locked palette, monospace character, restrained surfaces, and first-party brand mark through Jellyfin’s Custom CSS setting. It neither hides application controls nor changes library layout, playback, server configuration, or media paths.

The theme has no third-party stylesheet or tracking import. Clearing the Custom CSS field restores the stock interface, and the accompanying notes define the browser, mobile, accessibility, playback-control, and upgrade checks required before retaining it after a Jellyfin Web update.