sloanops.admin/3031023-xyz-public
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Enable reachable Gitea npm cache

Browse Source
This commit is contained in:
Kevin
2026-09-04 02:50:04 -04:00
parent 052fa31d87
commit 09a491b16b
7 changed files with 17 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/decap-cms-pilot.md
+6 -8
View File
@@ -81,14 +81,12 @@ the pilot:
- The existing branch preview workflows remain in place. Local output checks
now prove preview robots rules and page metadata stay no-index and that the
admin response has a no-index header rule.
- Validation, preview, and production workflows use clean `npm ci` installs with
`--prefer-offline --no-audit --no-fund`. Do not enable `setup-node`'s npm cache
until the Actions runner cache service is reachable from job containers. The
September 4 pilot test timed out against the runner's auto-detected private
address during both cache restore and cleanup. Give `act_runner` a fixed
`cache.host` and `cache.port` reachable from its job containers, publish that
port (or attach runner and jobs to a shared network), restart the runner, and
then restore the lockfile-keyed `cache: npm` configuration.
- Validation, preview, and production workflows cache npm's download store by
`package-lock.json` while retaining clean `npm ci` installs with
`--prefer-offline --no-audit --no-fund`. The runner advertises its cache on a
fixed host and port reachable from job containers, avoiding the timeout caused
by its former auto-detected private address. Warm jobs reuse dependency
tarballs without caching `node_modules`.
The pilot dependencies are active: the public client ID, exact-origin CORS
policy, `cms-pilot` branch, and both protection rules have been verified.