Skip to content

v1.4.0 — Storage backends: The Forge + AWS S3

Latest
Latest

Choose a tag to compare

View all tags
@aronjanosch aronjanosch released this 28 Jun 10:29
· 1 commit to main since this release
v1.4.0
0f6481c

Optimizes media on The Forge Assets Library and AWS S3 in addition to local data — backfill now discovers and repoints https:// references that earlier versions skipped (fixes #2).

What's new

  • The Forge — assets stored as assets.forge-vtt.com/<you>/… URLs in your own library. Auto-detected, no setup. Bazaar/shared and other users' libraries are read-only and skipped.
  • AWS S3 — bucket URLs (virtual-hosted or path-style). Bucket must allow cross-origin GET (CORS) so the converter can read originals.
  • Single run spans every backend and media kind (WebP / WebM / Ogg) together.
  • Read-only / unsupported references are surfaced as a skip notice.

Everything from v1.3.0 (image WebP, video WebM/VP9, audio Ogg/Opus, downscale, upload-time conversion, cleanup report) carries over unchanged for local data.

Notes

  • S3 requires bucket CORS for GET from the Foundry origin. The Forge needs none.
  • Module/system-shipped assets stay opt-in; core assets never touched.
Assets 4
Loading