3527e732d4
Production-ready Next.js boilerplate with: - Runtime env validation (fail-fast on missing vars) - Feature-gated config (S3, Stripe, email, OAuth) - Docker + Coolify deployment pipeline - PostgreSQL + pgvector, MinIO S3, Better Auth - TypeScript strict mode (no ignoreBuildErrors) - i18n (en/es), AI modules, billing, monitoring Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.8 KiB
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 tous-east-1S3_BUCKET: The default name of your storage bucket - you can pass different for each requestS3_ENDPOINT: The S3 endpoint URL for your storage provider - defaults tohttps://s3.amazonaws.comS3_ACCESS_KEY_ID: Your storage provider's access key IDS3_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.