# Streaming runtime

This folder contains the configuration and small amount of application code needed by the local creator streaming runtime.

## Runtime files

The application expects these files in the build output under `Streaming/`:

- `mediamtx.exe` — MediaMTX streaming server
- `mediamtx.yml` — the known-good MediaMTX configuration
- `caddy.exe` — Caddy web server
- `Caddyfile` — Caddy configuration

The project file copies everything under `Streaming/` to the build output. The executable binaries are runtime dependencies and are not part of the source-code cleanup itself.

## Current stream model

A creator uses a path derived from their BrownDogGames username:

`live/<username>`

For example:

`live/spangled`

OBS publishes to the local WHIP endpoint:

`http://localhost:8889/live/<username>/whip`

Caddy exposes the public BrownDogGames streaming hostname and proxies the required WebRTC/HLS requests to the local MediaMTX instance.

## Keep this folder simple

There should be one active MediaMTX configuration and one active Caddy configuration. Do not add alternate configuration files for different creators. Creator identity belongs in the stream path and Supabase live-status data, not in duplicate runtime configurations.

Do not commit production credentials, TLS private keys, or generated build output.