On this page
Wizarr: For developers
How Wizarr is built, for anyone who wants to change it or make one like it. It is MIT, by TheMightyTRexUK, and works with plug-in API >=1.14 <2.0.
Its files
starboard-plugin.jsoninstall.pylogo.svgtests/test_app_plugins.py, the checks it shares with the other app plug-ins
How it works
- It has no code of its own: Starboard runs the app's own image, pinned by digest, with the limits in
resources. - Its container is on the
lannetwork withpublishset.network:portlets Starboard open its page on the home network.host_portis the port Starboard tries first. When it is in use, Starboard takes the next free one and shows it on the tab. - It has no
settings,cards,actionsorhealth, so Starboard waits for its container to start after an update. - It runs read only, as a user that is not root, with no extra rights. What it writes goes in its own folder,
data/plugins/wizarr. HOME,UV_CACHE_DIRandUV_NO_SYNCkeep its Python tools from writing outside/tmp, so it runs read only.- It lists
needs: ["jellyfin"]but asks for nojellyfin:key: people give Wizarr a key they make in Jellyfin.
Containers
| Container | Network | Folders | Runs as | Starts | Limits |
|---|---|---|---|---|---|
app |
lan |
data |
10001:10001 |
always |
384 MB, 0.5 core, 128 processes |
Each image is pinned by digest in the manifest:
app:ghcr.io/wizarrrr/wizarr@sha256:08f2c6de534ec7d36d39a4f55b7c5c379021ca881dc519c702aad0ddafbdc67a
Find out more
This page on GitHub, where the help is written.