Folio Assistant Core
INGESTED COPY — not WHO, and not live. This page is rendered by folio-assistant from its own catalogue of WHO IRIS, modelled by reference: 235 nodes of a 273,559-item 361.55 GiB repository, of which 12 items are held here. The WHO logo is deliberately omitted, and the rendered covers are withheld from display for the same reason — they carry the emblem printed on the publications.
World Health
Organization
iris. Institutional Repository
for Information Sharing
Documentation•IRIS CDN Exporter: deployment

IRIS CDN Exporter: deployment

Where the IRIS CDN Exporter processes run, where they write, and where the secrets live.

The short version: GitHub Actions runs the exporter. Cloudflare holds and serves everything it exports. GitHub Pages only previews.

The pieces

PieceServiceHolds
RunnerGitHub Actions in litlfred/who-iris (.github/workflows/iris-cdn.yml)nothing between runs; each run's report goes to the workflow log
Release historygit repository on Cloudflare ArtifactsBagIt tag files, tagmanifest-sha256.txt.jws, and state/*.json (cursor, initial-load checkpoint, sizes, md5, uuids, metadata hashes, withdrawals)
BytesCloudflare R2 bucketPDFs, item records, item manifests and their JWSs, graph partitions (.nq.gz), each under sha256/<aa>/<digest>
CDNCloudflare, in front of R2 on a custom domaincached copies only, with an immutable cache policy
DID documentserved from the CDN domaindid.json with the public key(s), a did:web document
Signing keyGitHub environment secretthe P-256 private JWK
PreviewsGitHub Pages of litlfred/who-iris and WHO/who-iristhe site, reading exported data from the CDN; three materialized items for testing

Cloudflare: what to set up

  1. Workers Paid plan, $5 a month. Artifacts needs it, and it is in open beta. (changelog)
  2. Artifacts namespace and repository. Create the namespace in the dashboard. Then create the repository: npx wrangler artifacts repos create who-iris-releases --namespace <ns>. The remote is https://<ACCOUNT_ID>.artifacts.cloudflare.net/git/<ns>/who-iris-releases.git. A repository created now is capped at 1 GB (limits). That is why git holds only the release history, and the bytes go to R2.
  3. R2 bucket, for example who-iris-cdn. Storage is about $0.015 per GB-month and egress is free, so ~361 GiB costs about $5.40 a month.
  4. Custom domain on the bucket, which puts the Cloudflare CDN in front of it. Then add a Cache Rule with Cache-Control: public, max-age=31536000, immutable for sha256/*. Content-addressed objects never change, so they can be cached forever.
  5. API token with permissions for Artifacts (edit) and the R2 bucket (object read and write). Scope it to this one account.

GitHub: where each secret goes

In litlfred/who-iris, go to Settings → Environments → New environment and name it iris-cdn-release.

NameKindWhereWhat
IRIS_CDN_SIGNING_JWKsecretenvironment iris-cdn-releasethe P-256 private JWK: {"kty":"EC","crv":"P-256","x":…,"y":…,"d":…}
CLOUDFLARE_API_TOKENsecretenvironment iris-cdn-releasethe API token from step 5
R2_ACCESS_KEY_ID, R2_SECRET_ACCESS_KEYsecretenvironment iris-cdn-releaseR2's S3-compatible credentials, for uploads
IRIS_CDN_TRUST_ANCHOR_JWKvariablerepositoryWHO's signing-DID public key (JWK), so verification checks the x5c chain. Verification refuses to run without it
IRIS_CDN_DIDvariablerepositorythe DID that publishes the signing key, e.g. did:web:<cdn-domain>
IRIS_CDN_KEY_IDvariablerepositorythe key's fragment in that DID document (default release-1)
CLOUDFLARE_ACCOUNT_IDvariablerepositorynot secret
IRIS_CDN_ARTIFACTS_NAMESPACE, IRIS_CDN_ARTIFACTS_REPOvariablerepositorythe Artifacts namespace and repository from step 2
IRIS_CDN_R2_BUCKETvariablerepositorythe bucket from step 3
IRIS_CDN_ENABLEDvariablerepositorytrue turns the workflow on (on main only); anything else leaves it off

The workflow never stores the Artifacts git token. Each run mints a write token that lasts an hour (wrangler artifacts repos issue-token … --ttl 3600) and passes it to git as a Bearer header. It never goes in the remote URL.

How the signing key was created and published is outside this deployment; see key custody.

What runs when

Workflow triggerProcessEnvironment
schedule: 0 2 * * *nightly change ingestiris-cdn-release
schedule: 0 4 * * 0weekly reconciliation (Sunday)iris-cdn-release
workflow_dispatch with mode: nightly or reconcilethe same, on demandiris-cdn-release

Runs never overlap (one concurrency group), and a job times out after 350 minutes. Each run clones the release history, runs bun scripts/iris-cdn/run.ts <mode> --release release, commits and pushes only if something changed, then verifies the published release.

The initial load is not a workflow mode. It is run by hand: bun scripts/iris-cdn/run.ts initial-load --release <checkout> --budget <json-or-file>. The budget's maxBatchesPerRun bounds one run, and the next run resumes from the checkpoint in state/initial-load.json; the caller commits and pushes the checkout after each run.

Previews on GitHub Pages

The who-iris site on GitHub Pages renders pages from data it reads from the CDN. It never copies the export into the Pages artifact. The three items materialized today stay in this repository as test fixtures. That keeps Pages small, and a preview always shows what the CDN actually serves.

Still open