Files
claudemesh/.context/turbostarter-framework-context/sections/web/storage/configuration.md
Alejandro Gutiérrez d3163a5bff feat(db): mesh data model — meshes, members, invites, audit log
- pgSchema "mesh" with 4 tables isolating the peer mesh domain
- Enums: visibility, transport, tier, role
- audit_log is metadata-only (E2E encryption enforced at broker/client)
- Cascade on mesh delete, soft-delete via archivedAt/revokedAt

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-04 21:19:32 +01:00

1.8 KiB

title, description, url
title description url
Configuration Learn how to configure storage in TurboStarter. /docs/web/storage/configuration

Configuration

Currently, TurboStarter supports all S3-compatible storage providers, including AWS S3, DigitalOcean Spaces, Cloudflare R2, and Supabase Storage.

For a concrete example using Supabase Storage as an S3-compatible provider, see the Supabase recipe.

The setup process is straightforward - you just need to configure a few environment variables in both your local environment and hosting provider:

S3_REGION=
S3_BUCKET=
S3_ENDPOINT=
S3_ACCESS_KEY_ID=
S3_SECRET_ACCESS_KEY=

Let's break down each required variable:

  • S3_REGION: The AWS region where your storage is located - defaults to us-east-1
  • S3_BUCKET: The default name of your storage bucket - you can pass different for each request
  • S3_ENDPOINT: The S3 endpoint URL for your storage provider - defaults to https://s3.amazonaws.com
  • S3_ACCESS_KEY_ID: Your storage provider's access key ID
  • S3_SECRET_ACCESS_KEY: Your storage provider's secret access key

You can learn more about S3 service configuration in the official AWS documentation or your specific storage provider's documentation.