Sprue

The Forge upload service in Go (formerly the Storacha upload service).

Running locally

The repo ships a docker-compose.yaml that brings up sprue alongside PostgreSQL and MinIO for self-hosted development:

docker compose up -d postgres minio
SPRUE_STORAGE_POSTGRES_DSN="postgres://sprue:sprue@localhost:5432/sprue?sslmode=disable" \
  ./sprue serve

Postgres is the default store backend, so no extra flag is required.

Store backends

Sprue supports three store backends, selected by storage.type (or SPRUE_STORAGE_TYPE; defaults to postgres):

• memory — in-process only; all data is lost on restart. Dev/test only.
• postgres — PostgreSQL for metadata + S3-compatible storage (MinIO, Ceph, AWS S3) for blob payloads. Schema is managed by goose migrations embedded in internal/migrations/sql/ and applied on startup.
• aws — DynamoDB for metadata + S3 for blob payloads.

Notes

• Rate limits storage was not implemented. It has never been used in JS implementation, only supports blocking completely and can probably be applied at firewall.
• Plans, provisions, subscriptions, usage are not stores, they are services.
• The following dynamo tables have GSIs that do not exist in w3infra that need to be added:
  • consumer - consumerV3 and customerV2
• Using cid.Cid in new code over ipld.Link to ease transition to UCAN 1.0 when it comes.