Back the ResourceManager with the local filesystem, S3, or a GitHub repository.
A storage provider is where stored content
lives: templates, uploaded files, and anything the ResourceManager reads or
writes. One provider is active per server, named by storage_module in the
manifest.
Provider
Package
Backing store
When to pick it
local
tai42-storage-local
A directory on the server’s own disk.
A single-process install.
s3
tai42-storage-s3
Any S3-compatible bucket, including MinIO.
A multi-replica fleet, or durable shared object storage.
github
tai42-storage-github
A branch of a GitHub repository.
Every write should be a reviewable commit.
Local storage is per-process state on one machine’s disk. A multi-replica fleet
gives each replica its own copy — use S3 or GitHub instead.
Each provider’s package, its storage_module manifest key, its STORAGE_<KIND>_*
settings, and its store-specific setup (S3 bucket policy and MinIO addressing,
GitHub token scopes and the 1 MiB / CDN-staleness limits) live on the plugin
page:
storage-local
STORAGE_LOCAL_* — a root directory on local disk.
storage-s3
STORAGE_S3_*, the bucket policy, and MinIO.
storage-github
STORAGE_GITHUB_*, token scopes, and the write/read caveats.
