Purge Fly.io proxy cache after docs release #154

Merged
eblume merged 1 commit from fix/purge-fly-cache-on-release into main 2026-02-11 13:33:26 -08:00
Owner

Summary

  • The Fly.io nginx proxy caches docs responses for 24h (proxy_cache_valid 200 1d)
  • After a release, docs.eblu.me kept serving stale content until the cache expired
  • This caused v1.5.4 to show v1.5.3 on the CHANGELOG page
  • Adds flyctl install and fly ssh console cache purge steps to the build workflow, running after the ArgoCD deploy completes

Test plan

  • Next release should show the correct version on docs.eblu.me/CHANGELOG immediately
  • Verify the fly ssh console command succeeds in the workflow logs
## Summary - The Fly.io nginx proxy caches docs responses for 24h (`proxy_cache_valid 200 1d`) - After a release, docs.eblu.me kept serving stale content until the cache expired - This caused v1.5.4 to show v1.5.3 on the CHANGELOG page - Adds `flyctl` install and `fly ssh console` cache purge steps to the build workflow, running after the ArgoCD deploy completes ## Test plan - [ ] Next release should show the correct version on docs.eblu.me/CHANGELOG immediately - [ ] Verify the `fly ssh console` command succeeds in the workflow logs
The Fly.io nginx proxy caches docs responses for 24h. After a release,
the new content wasn't visible until the cache expired. Add flyctl install
and cache purge steps to the build workflow, running after ArgoCD deploy.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
eblume merged commit 0efcce2984 into main 2026-02-11 13:33:26 -08:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
eblume/blumeops!154
No description provided.