kenzuya/unshackle
1
0
Fork 2
mirror of https://github.com/unshackle-dl/unshackle.git synced 2026-11-12 20:15:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Deployed a7d6791 with MkDocs version: 1.6.1

Browse Source
This commit is contained in:
2026-09-12 21:14:05 +00:00
parent 82cbad5c3e
commit f5a17df145
8 changed files with 118 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
dev/rest-api/dashboard/index.html
+4 -2
View File
@@ -2448,8 +2448,10 @@ missing or a vault's credentials expired. This finds that before a job does.</p>
<p><code>status</code> is <code>ok</code>, <code>degraded</code> (an optional dependency is missing) or <code>failing</code> (a required one
is). Player binaries are not checked: a headless server never has one and it plays nothing.
Each check is <code>ok</code>, <code>warn</code> or <code>fail</code>. Check ids are the binary names, <code>cdm</code>,
<code>vault:&lt;name&gt;</code> (the vault's configured <code>name</code>, so two vaults of the same type stay apart), and
<code>proxies</code>.</p>
<code>vault:&lt;name&gt;</code> (the vault's configured <code>name</code>, so two vaults of the same type stay apart),
<code>bad_keys</code> and <code>proxies</code>. <code>bad_keys</code> warns when the vaults hold no <code>SQLite</code> entry, because only
that backend stores the flag for a content key a remote client proved wrong; without it the
server serves the same bad pair again.</p>
<p>The server caches the result for 30 seconds and keeps every probe shallow: a vault answers one
lookup that should miss, and no probe allocates anything. A failing probe's <code>detail</code> has the
vault's password or token masked. This is a panel, not a liveness probe - do not poll it faster