3 Commits

Include renames

Author	SHA1	Message	Date
jason	6a3a9bde14	🚀 Enable shared act_runner cache-server 🚀 ... Turned on the act_runner Actions cache instead of leaving it disabled. The standalone `cache-server` process was already being launched unconditionally by zz-act_runner.sh but had no `external_secret`, so it was refusing to start (the binary requires a non-empty secret even though its own `cache.enabled` field is unused). Wired a shared, randomly generated secret through the existing REPLACE_* templating pattern so the "gitea" runner, the cache-server, and the extra runner-N daemons spawned by start-runners all share one cache backend. - rootfs/tmp/etc/act_runner/default_config.yaml: cache.enabled: true; added external_server (pointed at the local cache-server) and external_secret placeholders - rootfs/tmp/etc/act_runner/cache_server.yaml: cache.enabled: true; added external_secret placeholder (required for the binary to start) - rootfs/usr/local/etc/docker/init.d/zz-act_runner.sh: added __gen_cache_secret() (mirrors __gen_auth_token's persisted-token pattern, stored at $CONF_DIR/tokens/cache_secret); substitutes REPLACE_RUNNER_CACHE_SECRET into both the runner config and the cache-server config; exports RUNNER_CACHE_HOST/PORT/SECRET for start-runners; bumped version stamp - rootfs/usr/local/bin/start-runners: generates a shared runners-cache.yaml from the exported cache env vars and passes --config to both `act_runner register` and `act_runner daemon` for every runner-N instance, so they use the same external cache server instead of an unshared per-process local cache - TODO.AI.md: logged pre-existing script-lint findings (missing `--` before grep queries throughout zz-act_runner.sh, a UUOC in start-runners, an unpinned/stale docker.yaml CI workflow, and forbidden OCI labels in the Dockerfile) surfaced incidentally by the lint pass for this change but out of scope for it	2026-08-03 11:57:10 -04:00
jason	895520eb77	🐛 Fix runner config filenames, cache-server, and registration log 🐛 ... Three more bugs found during full component verification: 1. RUNNER_CONFIG_DEFAULT pointed to config.yaml but the actual template filename is default_config.yaml — gitea named runner never registered because the file-existence check always failed. 2. CACHE_CONFIG_FILE pointed to cache.yaml but the actual template filename is cache_server.yaml — cache-server launch always skipped silently. 3. act_runner v1.0.6 requires cache.external_secret on both the cache-server and any runner using external_server; neither config had it, so cache-server exited immediately and runner registration failed when external_server was present in default_config.yaml. 4. Registration log redirect was 2>/dev/stdout >>"$log" (stderr went to original stdout, not the log); corrected to >>"$log" 2>&1. - rootfs/usr/local/etc/docker/init.d/zz-act_runner.sh: - RUNNER_CONFIG_DEFAULT: config.yaml → default_config.yaml - CACHE_CONFIG_FILE: cache.yaml → cache_server.yaml - fix registration log redirect: >>"$RUNNER_LOG_FILE" 2>&1 - rootfs/tmp/etc/act_runner/default_config.yaml: remove external_server (no shared secret configured; each runner uses its own internal cache) - rootfs/tmp/etc/act_runner/cache_server.yaml: set enabled: false (cache-server requires external_secret; disabled until a proper shared-secret setup is added) Verified: 6 daemons on fresh start (1 gitea named + 5 runners), all with 22 labels; clean reconnect on restart with no re-registration. rootfs/tmp/etc/act_runner/cache_server.yaml rootfs/tmp/etc/act_runner/default_config.yaml rootfs/usr/local/etc/docker/init.d/zz-act_runner.sh	2026-05-24 15:16:16 -04:00
jason	fbe18132f8	🦈🏠🐜❗ Initial Commit ❗🐜🦈🏠	2025-09-16 23:50:36 -04:00