blossom-server 6.x serves HTTP Range requests natively, so the nginx
podsteadr-blossom-gateway app added for 4.4.1 is removed and
podsteadr-blossom publishes 8098 again (unauthenticated port count
unchanged). New v6 config mirrors the podsteadr repo: a single "*" rule
with a 100-year expiration (6.x prunes for real), unused endpoints off,
and BLOSSOM_REQUIRE_CONFIG=1 so a bad config fails startup instead of
falling back to week-long video retention.
Migration from 4.x was verified on a copy of a production data set
(25 blobs); the 4.4.1 wrong-size rows it surfaced are fixed by the
podsteadr repo's scripts/fix-blossom-sizes.py, noted in the manifest.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ssmithxandClaude Opus 5.5
af3753fb69