@andrian.yablonskyy/thub-coordinator 1.0.12 → 1.0.13

package/README.md

@@ -44,7 +44,7 @@ The Coordinator loads a plain **JSON** config file (no YAML support). Resolution
   "jobs": { "defaultTimeoutSec": 1800, "maxTimeoutSec": 14400 },
   "retention": { "logRetentionDays": 14, "artifactRetentionDays": 30 },
   "artifacts": { "maxUploadMb": 512, "linkTtlHours": 168 },
-  "updates": { "checkIntervalHours": 6, "registry": null }
+  "updates": { "checkIntervalMin": 15, "registry": null }
 }
 ```
 
@@ -161,7 +161,7 @@ Server-rendered Pug templates styled with Bootstrap 5.3, with a little vanilla J
 
 The Coordinator's own version (`ver. X.Y.Z`) is shown under the TestHub logo, top left of every page.
 
-**Versions and self-update.** The Coordinator checks the npm registry for the latest Coordinator, Agent and Client every `updates.checkIntervalHours` (default 6, `0` disables; `updates.registry` for a private mirror) and on **Check for updates**. A newer Coordinator shows as an **Update app to X.Y.Z** button in the navbar for admins (a badge under the logo for viewers); Agents and Resources show each one's version with an **update available** or pending **→ vX.Y.Z** badge. Admins request self-updates per agent/resource (**Update**, which becomes **Cancel update**) or with **Update all agents** / **Update all clients**, always to the latest version:
+**Versions and self-update.** The Coordinator checks the npm registry for the latest Coordinator, Agent and Client every `updates.checkIntervalMin` (default 15 minutes, `0` disables; the older `checkIntervalHours` is ignored; `updates.registry` for a private mirror) and on **Check for updates**. A newer Coordinator shows as an **Update app to X.Y.Z** button in the navbar for admins (a badge under the logo for viewers); Agents and Resources show each one's version with an **update available** or pending **→ vX.Y.Z** badge. Admins request self-updates per agent/resource (**Update**, which becomes **Cancel update**) or with **Update all agents** / **Update all clients**, always to the latest version:
 - Clients get a `self-update` command on their next heartbeat and install it through their root `thub-client-update` helper, once none of the host's instances is busy.
 - Agents install it at the start of their next run (`GET /api/v1/agents/me/update`), then re-run the command on the new version.
 - The Coordinator itself: the **Update app** button writes `<dataDir>/update-request.json`; the root `thub-coordinator-update.path` unit (installed by `sudo npm i -g`) runs `npm i -g` for it, and the postinstall restarts the service (the dashboard and API are briefly down). Logs: `journalctl -u thub-coordinator-update`. Without that unit, use `thub-admin self-update` on the host.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@andrian.yablonskyy/thub-coordinator",
-  "version": "1.0.12",
+  "version": "1.0.13",
   "description": "TestHub Coordinator — job queue, resource registry, scheduler, heartbeat monitor, log/artifact store and web dashboard",
   "main": "src/server.js",
   "engines": {

package/src/config.js

@@ -54,10 +54,13 @@ const DEFAULTS = {
     linkTtlHours: 168
   },
   // New-version check of the Coordinator/Agent/Client packages (README
-  // §10.2). 0 disables the periodic check; registry null = the public npm
-  // registry (or npm_config_registry).
+  // §10.2), every 15 minutes so a new Coordinator's "Update app" button
+  // shows up promptly. 0 disables the periodic check; registry null = the
+  // public npm registry (or npm_config_registry). The old
+  // `checkIntervalHours` (6) is no longer read — installed configs still
+  // carry it from their defaults.
   updates: {
-    checkIntervalHours: 6,
+    checkIntervalMin: 15,
     registry: null
   }
 };

package/src/services/updates.js

@@ -22,7 +22,7 @@ const fs = require('node:fs'),
 // as root when the dashboard writes an update request (README §10.2).
 const UPDATE_PATH_UNIT = '/etc/systemd/system/thub-coordinator-update.path';
 
-// Latest published versions, refreshed every `updates.checkIntervalHours`
+// Latest published versions, refreshed every `updates.checkIntervalMin`
 // and on demand from the dashboard. Kept in memory only — a restart just
 // checks again.
 function createUpdatesService({ config }){
@@ -96,12 +96,12 @@ function createUpdatesService({ config }){
   }
 
   function start(){
-    const hours = Number(config.updates.checkIntervalHours);
-    if (!(hours > 0)){
+    const minutes = Number(config.updates.checkIntervalMin);
+    if (!(minutes > 0)){
       return;
     }
     checkNow().catch(() => {});
-    const timer = setInterval(() => checkNow().catch(() => {}), hours * 3600 * 1000);
+    const timer = setInterval(() => checkNow().catch(() => {}), minutes * 60 * 1000);
     timer.unref?.();
   }