phlix-plugin-example
Reference plugin
The smallest working Phlix plugin. Use this as a template for your own plugins. Demonstrates metadata provider patterns, event hooks, and the full plugin lifecycle.
View on GitHubA real contract, not just a suggestion. Drop a plugin in, and Phlix loads it.
Phlix plugins implement the LifecycleInterface and ship a versioned
manifest file. The plugin loader reads the manifest, validates the interface, and
registers the plugin with the server.
// manifest.json
{
"name": "my-metadata-provider",
"version": "1.0.0",
"apiVersion": "1.0",
"description": "Fetches metadata from MyAnimeList",
"author": "Your Name",
"class": "MyAnimeList\\Plugin",
"events": ["metadata.fetch", "item.created"]
}
phlix-plugin-example is the reference implementation for a Phlix plugin. It demonstrates metadata fetching, event handling, and proper manifest structure.
Reference plugin
The smallest working Phlix plugin. Use this as a template for your own plugins. Demonstrates metadata provider patterns, event hooks, and the full plugin lifecycle.
View on GitHubFetch movie/TV metadata from sources like TMDB, TVDB, Fanart.tv, or custom APIs. Plugins can supplement or replace built-in metadata fetching.
Add support for new codecs or containers. Plugins can hook into the transcoding pipeline to add custom encoding profiles.
Add new Live TV sources beyond the built-in tuner support. Plugins can provide channel lineups and EPG data.
Extend the web UI with custom pages, widgets, or dashboard panels. Plugins can add admin settings and user-facing features.