mirror of
https://github.com/jhd3197/ServerKit.git
synced 2026-10-29 16:17:25 +09:00
Juan DenisandClaude Fable 5
4af3df1136
A test box's panel domain kept serving a Jun 25 bundle after the Jul 3 update — the domain's custom vhost still proxied the retired :3847 frontend container, and the old bundle's calls to deleted legacy marketplace endpoints read as 'Failed to load extensions'. It looked exactly like a browser/CDN cache problem (it wasn't — cf-cache-status was DYNAMIC; the origin itself was stale). - both stock confs: expires -1 on the SPA entrypoint (emits Cache-Control: no-cache WITHOUT discarding server-level security headers, unlike add_header-in-location) — a cached index.html references hashed assets that vanish on the next blue/green switch - update.sh refresh_config now runs report_stale_panel_vhosts: warns, naming the file, when any enabled vhost still proxies :3847; observation-only per R1, silent on a missing sites-enabled dir, added to the fresh-box loop per policy - proving tests: entrypoint no-cache asserted for both confs; stale vhost flagged (and clean one not); missing-dir silence (42 passed) Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>