![]() ![]() In order for your add-on to be used by others, it needs to be deployed online. Creating a homepage for your add-on that includes an "Install Add-on" buttonįor developers looking for a quick way to test their new add-ons, you can either:.Publishing your add-on link to the public Add-on collection with publishToCentral.It is also possible to create an add-on without any programming language, see our static add-on example based Language, see the add-on protocol specification for more information. If you don't wish to use Node.js (and therefore not use this SDK either), you can create add-ons in any programming ![]() We've made two step by step guides: one for this SDK, and one for any programming language, which you can read here. We also have an example add-on that you can use as a guide to help you build your own add-on. Information, or dive straight into our SDK documentation for our code reference docs. Take a look at our examples list for some high-level SummaryĪt this point you should be familiar with Stremio's media structure, how add-ons work, and their basic endpoints.įeel free to proceed to the next chapter and start the guide.If you wish to install the add-on in the Desktop version of Stremio (which you can download here), you should use npm start -install DocumentationĪll our documentation is right here on GitHub. You are free to use whatever suits your needs in your implementation. This approach can also be used in add-on written in PHP or CGI for example. The file system will be used as a router. Our goal is to introduce you to the Stremio's way of using add-ons rather than fighting with a framework/language. It may be torrent info hash, HTTP URL, etc.Īll the resources in an add-on can be dynamically generated by a script or just by plain text JSON files located on your file system. Tells Stremio how to obtain the media content. This description is displayed when the user selects an item form the catalog. You can also browse the catalogs in the Discover.ĭetailed description of a meta item. Catalogs are displayed on the Srtemio Board. Every resource is accessed at a certain endpoint where your add-on should respond with proper data. The resources are basically a segmented way to build the content tree we mentioned. For this purpose in every add-on's manifest, one or more resources must be declared. ![]() The complete tree should look like that: Catalogįor Stremio to be able to display any data, it must first find it. In this case it provides streams directly. There is an option where the meta item does not contain videos. Finally, for every video there are one or more streams. The catalogs provide media collections of different types. In the root of this tree, we have catalogs. The resources are organized in a tree-like structure. Media structureĮvery add-on provides one or more resources for media content. The add-on manifest is a JSON object describing the add-on's capabilities. The add-on must adhere to the add-on API. Add-ons are not meant to be used in the same way as YouTube you don’t upload your content to a Stremio add-on.Add-ons are not meant to compete with VOD services they’re meant to integrate existing VOD services into Stremio.If an add-on is served via HTTP, CORS headers must be present. This brings ease of use and security benefits to the end user. Instead, it is hosted on the Internet just like any website. They provide the content that the users enjoy.Īn add-on in Stremio, unlike other similar apps, doesn't generally run on а client's computer (however, there are exceptions). The add-ons in Stremio are the most fundamental part of the app. ![]()
0 Comments
Leave a Reply. |