docs: record release retention policy after bastion cleanup

This commit is contained in:
enne2
2026-10-11 01:36:18 +02:00
parent 7893dc9149
commit 15efd03515
+9
View File
@@ -63,6 +63,15 @@ Staging excludes native addons, source MDL assets, unused world weapon scenes, e
Upload new immutable directory first, never overwrite an existing hash. Then atomically replace root index.html. Keep previous releases for open tabs/rollback. Do not delete them during routine deployment.
Retention policy after cleanup on 2026-10-11: keep the live release plus the immediately
preceding one; the eight older directories (fd65770c62e811fe, 31564f79b9f5e299,
ee476ce70108b55d, 6de9bbe8915fd82e, ab6054111f5919a8, 4e181f0fe5d02cc9, 7d55da56077f8eee,
7d3c1fb9d96da215) were removed with explicit approval. Releases went 527 MB -> 108 MB and
free space on the bastion 1.1 GB -> 1.5 GB. Deleting a release makes the matching
`index-before-*.html` backup unreproducible; those files are references, not served pages.
Verify after any cleanup: root still200 with the live base href, live PCK byte-identical,
previous release still served, removed release returns404.
Nginx snippet source: tools/nginx-zombie-fps.conf. Installed at /etc/nginx/snippets/zombie-fps.conf and included only by enne2.net's HTTPS server in /etc/nginx/conf.d/enne2.conf. gzip_static on, Vary Accept-Encoding, correct application/wasm MIME. Root HTML no-cache; versioned files public,max-age=31536000,immutable. Other /pub/ sites unchanged. No Brotli module installed.
Protected configuration backup: /etc/nginx/zombie-fps-backup-9d706e724b0a/.