File storage

During development we use Garage to store our files. On production, mirlo.spaces uses backblaze. You could theoretically (if untested) use any S3 compatible client to do this.

Garage has no web console. Point an S3 client (mc, rclone, aws s3) at localhost:9000 with the LOCAL_S3_USER and LOCAL_S3_PASSWORD you set in .env, or use docker exec blackbird-garage /garage bucket list. See object-storage.md.

See the design decisions and thinking that went into this.

For bandwidth reasons, we get a pre-signed upload URL when uploading a track, that uploads directly to the relevant Backblaze bucket (incoming/ in mirlo-audio for now).

Updating CORS on backblaze

Using the backblaze command line tool, after authenticating (b2 authorize).

b2 bucket update --cors-rules "$(<./b2-cors-rules.json)" mirlo-audio

You'll need to wait a minute for this to take effect.

CORS in development

This used to be impossible locally: setting CORS per bucket needed the paid version of MinIO, so dev uploads never used direct signed-URL uploads the way production does.

Garage implements PutBucketCors, so that restriction is gone. applyCorsPolicyLocal in src/utils/minio.ts applies CORS rules whenever a local bucket is ensured, so dev exercises the same direct-upload flow as production.