How mr-joep/feeb-streaming-server works
OBS Hosting provisions an individual OBS container for each streamer. A browser user signs up through the public site or portal; a portal admin approves the account, and the client dashboard can then request deployment. The controller coordinates node and regional ingest capacity and publishes the OBS Blade address; phones send streams through ingest to the client’s OBS. The controller also supports account and server administration, settings, mail, and remote viewing. The README documents these product interactions; unsampled subsystem internals are represented only at supported directory paths.
Main entry points: deploy.php Deployment coordinator · public Portal pages · index.php Marketing pages · api.php Node API
Components 24
Public website
- Marketing pages
website/app/public/index.php - Site content
website/app/public - Shared site UI
website/app/includes - Signup form
website/app/includes/signup-form.php
Controller portal
- Portal pages
controller/app/public - Account approval
controller/app/lib/accounts.php - Portal sessions
controller/app/lib/bootstrap.php - Admin management
controller/app/public/admin.php - Client dashboard
controller/app/public/dashboard.php - Controller database
Deployment infrastructure
- Deployment coordinator
controller/app/lib/deploy.php - Server API client
controller/app/lib/api.php - Node API
node/public/api.php - Node dashboard
node/public/index.php - Node manager core
node/lib/common.php
Streaming and access
- Ingest API
ingest/app/api.php - Ingest setup
ingest/app/pages.php - Go-irl services
ingest/app/supervisor.php - Client OBS container
image - OBS remote view
node
Other components
- Browser user
- Streamer phone
- Cloudflare DNS
- SMTP mail service
Connections 26
- Browser user → Marketing pages: visits
- Marketing pages → Shared site UI: renders with
website/app/public/index.php - Marketing pages → Signup form: offers signup
website/app/public/index.php - Shared site UI → Site content: frames pages
website/app/public/index.php - Signup form → Portal pages: links signup
website/app/includes/signup-form.php - Browser user → Portal pages: uses portal
- Portal pages → Portal sessions: uses sessions
controller/app/public/admin.php - Portal pages → Account approval: handles account actions
controller/app/public/admin.php - Admin management → Account approval: decides accounts
controller/app/public/admin.php - Admin management → Deployment coordinator: manages deployments
controller/app/public/admin.php - Client dashboard → Deployment coordinator: requests deployment
controller/app/public/dashboard.php - Portal sessions → Controller database: reads and writes
controller/app/lib/bootstrap.php - Account approval → SMTP mail service: sends account mail
controller/app/lib/accounts.php - Deployment coordinator → Server API client: calls server APIs
controller/app/lib/deploy.php - Deployment coordinator → Ingest API: provisions ingest
- Deployment coordinator → Node API: provisions OBS
- Deployment coordinator → Cloudflare DNS: publishes Blade address
- Ingest API → Ingest setup: uses pages
ingest/app/api.php - Ingest API → Go-irl services: manages go-irl
- Node API → Node manager core: uses manager core
node/public/api.php - Node dashboard → Node manager core: uses manager core
node/public/index.php - Node API → Client OBS container: manages containers
- Streamer phone → Go-irl services: sends SRTLA
- Go-irl services → Client OBS container: feeds SRT
- Browser user → OBS remote view: views OBS remotely
- Portal pages → OBS remote view: proxies remote view