Storage Configuration

Environment variables

All storage configuration lives in packages/infra/storage/src/env.ts. The getStorageEnv() function reads these values from process.env.

R2_ACCESS_KEY_ID and R2_SECRET_ACCESS_KEY are always required. The remaining variables have sensible defaults for the dev environment.

1Password integration

Credentials are stored in the octospark-services vault with separate items per environment.

# Read dev credentials
op read "op://octospark-services/dev/R2_ACCESS_KEY_ID"
op read "op://octospark-services/dev/R2_SECRET_ACCESS_KEY"

# Inject into a command
op run --env-file=.env.dev -- pnpm dev

Vault structure

The same R2 API token works across all environments because it is scoped to all buckets on the Cloudflare account.

R2 buckets

Three buckets are provisioned via Wrangler CLI:

wrangler r2 bucket create octospark-dev
wrangler r2 bucket create octospark-staging
wrangler r2 bucket create octospark-prod

Verify with wrangler r2 bucket list.

Local development

Set the R2 credentials in your .env file or inject them via 1Password before running the API or worker:

# Option 1: Add to .env (gitignored)
R2_ACCESS_KEY_ID=your-key
R2_SECRET_ACCESS_KEY=your-secret

# Option 2: Inject from 1Password
op run --env-file=.env.dev -- pnpm dev

The storage package throws a clear error if credentials are missing, guiding you to set them up.

S3 client configuration

The underlying S3Client is configured for R2 compatibility:

Related pages