@admin
Config settings
The five platform settings the admin package declares and reads live.
The admin package declares five platform settings in its manifest
(configSettings). Each is edited from the Admin widget's Config tab like any
other declared key and read live on every call, so a change applies without a
restart. How packages declare settings is on
package-system Config settings.
| Key | Default | Range | What it does |
|---|---|---|---|
qdrantProbeTimeoutMs | 3000 | 250–30000 ms | Per-call timeout of the vector database probes behind vector status and the health check. Raise it for a remote or slow vector database |
adminLogsReadMaxLines | 500 | 100–10000 lines | Line cap of one log read in the Logs tab. There is no paging, so this is the deepest history one request reaches |
updateCheck | on | — | Check the published release line periodically and notify holders of platform.config when a newer release exists. Turn off for air-gapped installs |
updateManifestUrl | the published GitHub release manifest | HTTPS, port 443 | Where the release check reads. Point it at a mirror on a publicly reachable host; a private-network address is refused |
updateCheckIntervalHours | 24 | 1–168 hours | Hours between two release checks; the cadence survives restarts |
The release check sends one anonymous HTTPS GET per interval and installs
nothing. When it finds a newer release, it raises the update.available
notification: one Inbox notice per project and version for each member holding
platform.config, opening the Admin dashboard.