mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
Plugin Repository #144
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @anthonylavado on GitHub (Dec 22, 2018).
Looking at #257, there are some calls to
mb3admin.localthat, naturally, fail. One of these URLs is originally:https://www.mb3admin.com/admin/service/EmbyPackages.json
We should get a copy of this list for reference.
Then, we should investigate:
Then we should decide:
@bfayers commented on GitHub (Dec 22, 2018):
Looks like it contains downloads for plugins as well as some other stuff.
Is this a method to identify when a “sub module” (like a metadata provider) gets updated?
It certainly seems that way.
Does Emby use this list to download module updates?
Almost definitely
If this is not important, and we remove this call entirely from Jellyfin, what functions do we lose?
I think we lose the ability to use the plugin catalog.
@bfayers commented on GitHub (Dec 22, 2018):
To follow up my previous comment I am almost 100% certain this file is responsible for module updates.
21a8d27378/Emby.Server.Implementations/Updates/InstallationManager.cs (L208)@pw-h commented on GitHub (Dec 23, 2018):
I get errors calling to mb3admin.local as soon as i search for plugins, so indeed, mb3admin is called to get a list of plugins.
Trying to install the TVHeadend plugin, any other way to do that?
@bfayers commented on GitHub (Dec 23, 2018):
@pw-h Looking at the json file you can probably download this: https://embydata.com/admin/service/packageFiles/TVHeadEnd.dll_1.4.0.exe and save it as TVHeadEnd.dll in the plugins directory.
@thexyno commented on GitHub (Dec 23, 2018):
It'd be really cool if jellyfin could automaticly generate a packages.json when a new Github Release of a Plugin happens, maybe with a travis-ci script or something.
@bfayers commented on GitHub (Dec 23, 2018):
This definitely seems possible.
@PrplHaz4 commented on GitHub (Dec 24, 2018):
A key piece of this seems to be validating the downloaded files against a known checksum included in the EmbyPackages.json
If we host this file on our own, it will probably only have value if we are also hosting all of the plugin binaries or just pointing to the mb ones (which obviously, is not a long-term solution).
There is probably a backend process managing the plugins that generates the GUIDs and checksums and this EmbyPackages.json when a plugin is updated.
We will probably have to support two main scenarios:
@anthonylavado commented on GitHub (Jan 28, 2019):
Okay - This is becoming a little more important now.
We're thinking about plug-ins more, and users are starting to ask. We do have jellyfin-plugin-trakt as a PoC, where @cvium graciously re-wrote it to support new auth and it's actually working.
What we need to do:
@dkanada commented on GitHub (Jan 28, 2019):
I copied an example plugin entry here and collected all possible values for interesting attributes on plugins and the individual versions so we can figure out an implementation.
@JustAMan commented on GitHub (Jan 28, 2019):
@dkanada I propose to follow this up here: https://forum.jellyfin.org/t/plugin-distribution/50/10
@joshuaboniface commented on GitHub (Mar 18, 2019):
I think this is mostly working now as-is. Granted we do want to clean up the metadata a bit and work on a strategy to build these better, but that can come later.
@anthonylavado commented on GitHub (Mar 18, 2019):
@joshuaboniface Yes, this as it was originally opened, is satisfied IMO.