How infiniteavenger/jellio-plus works
Project type and purpose
• This is a Jellyfin plugin (“Jellio+”) written in C# (.NET Core) that exposes a Stremio add-on API, plus a separate React/TypeScript web UI (jellio-web) for configuring the plugin inside Jellyfin’s Dashboard.
• Purpose: Bridge Jellyfin media server libraries into Stremio; optionally send content requests to a Jellyseer service.
File structure
• Top-level:
• Jellyfin.Plugin.Jellio/ (backend plugin)
• jellio-web/ (frontend config UI)
• assets/, README.md, solution and project files
• Jellyfin.Plugin.Jellio:
• Controllers: AddonController (Stremio API), AuthController, RequestController (Jellyseer), WebController (serves config.html, index.html)
• Helpers: JSON binding, authorization filters, Jellyfin library helpers, request utility
• Models: DTOs (MetaDto, StreamDto, VideoDto), ConfigModel, SaveConfigRequest
• Web: static HTML/CSS/JS shipped to Jellyfin UI
• jellio-web:
• React app with components/form fields for configuration, hooks for storage and API calls, backendService (calls plugin’s API)
• build scripts and Vite configuration
README for additional insights
• Explains plugin registers itself through Jellyfin’s plugin system, provides a Stremio add-on endpoint URL that you paste into Stremio.
• Mentions optional Jellyseer integration (plugin calls external Jellyseer API).
Main components
a. Jellyfin Server
– Hosts the Jellio+ plugin
– Holds the media library (movies, TV shows)
b. Jellio+ Plugin (C# .NET)
– Controllers (AddonController, AuthController, RequestController, WebController)
– Helpers & Models
– Configuration store (persisted via Jellyfin’s plugin framework)
c. Static Web UI (config.html, index.html, redirect.html)
– Served by WebController inside Jellyfin Dashboard
– Built from jellio-web React app
d. Stremio Client
– Consumes the add-on manifest and streams from Plugin’s AddonController
e. Optional Jellyseer Service
– External API endpoint for media requests
f. Build/CI Pipeline
– GitHub Actions (release.yml) building plugin and jellio-web, packaging assets
Relationships & interactions
• Flow A (Browsing & Streaming):
Stremio → HTTP GET /manifest via AddonController → returns catalog items (MetaDto)
Stremio → HTTP GET /stream/{id} → Plugin authenticates with Jellyfin (AuthController/Helpers) → proxies media segments from Jellyfin → returns HLS/DASH stream to Stremio.
• Flow B (Configuration UI):
Admin user in Jellyfin UI → WebController serves config.html → React app loads → calls backendService (plugin’s REST endpoints) → fetch/save ConfigModel.
• Flow C (Jellyseer Request):
User from Stremio requests missing media → RequestController relays request to Jellyseer API with API key.
• Build Flow:
jellio-web (Vite) → produces static assets → copied into Jellyfin.Plugin.Jellio/Web → included in plugin package → deployed via Jellyfin plugin repository.
Architectural patterns & design principles
• MVC inside plugin: Controllers + Models + Helpers
• Separation of Concerns: plugin logic vs. UI layer
• Stateless HTTP API for Stremio integration
• Modular Frontend (React hooks + components)
• Plugin-based deployment using Jellyfin’s plugin framework
Detail
• Configuration file locations or storage if relevant
• Plugin’s dependency on .NET runtime and Vite build for UI