Skip to content

Changelog

2026-06-09

Initial cproxy config integration

Established PutOriginURLs (PATCH, in-memory) and PurgeContent as the working origin-switch flow. Confirmed on cproxy v1.1.1.rc1:

  • PATCH /api/config — works, switches originUrls
  • PUT /api/config/origins — 404s on this version, not available until v1.1.5.rc1
  • PUT /api/config with full JSON body — works for structural changes

Decision: CoreAPI/Postgres is the source of truth for origin state. PATCH changes are in-memory only on the node, so domain/distribution re-applies the saved config to each node on startup rather than relying on the node's own persistence.

Debugged a crash loop where the cproxy entrypoint's envsubst was overwriting the mounted config from its template at startup — fixed by mounting the config as cproxy-new.yml and using a command override (cp cproxy-new.yml cproxy.yml && ./cproxy) instead of letting the entrypoint template over it.

Quickstart: compose/services/cproxy_bkk_1