Next.js

This configuration is ideal for traditional hosting, Docker deployments, or development environments. Next.js standalone mode provides flexibility for various hosting providers.

🚀 Core Application Settings

BETTER_AUTH_SECRET is a random string used for encryption and generating hashes. You can generate a 32-character secure key using the following command:

# Generate a 32-character secure key
openssl rand -base64 32

📧 Email Configuration

If you need to enable email/password login functionality that requires email verification, you need to set RESEND_API_KEY. If you need newsletter functionality, you need to set RESEND_AUDIENCE_ID.

If you only enable social media login without transactional emails or newsletter functionality, you don't need to set RESEND_API_KEY and RESEND_AUDIENCE_ID.

For more information about email configuration, see:

🔐 OAuth Provider Settings

GitHub OAuth

If you need to enable GitHub login functionality, you need to set GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET.

Google OAuth

If you need to enable Google login functionality, you need to set GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET.

For more information about OAuth configuration, see:

💳 Payment Integration (Stripe)

For more information about payment configuration, see:

📁 Storage Configuration

This configuration needs to match the bucket name configured in your S3 or Cloudflare R2.

☁️ AWS S3 Configuration (if using AWS S3 services)

🌍 Cloudflare R2 Configuration (if using Cloudflare R2 services)

📊 Analytics Configuration

For more information about analytics configuration, see:

💰 Affiliate Marketing Configuration

NEXT_PUBLIC_AFFILIATE_AFFONSO_ID is the Affonso affiliate ID used to track affiliate performance.

For more information about affiliate configuration, see:

📝 Example .env File

BETTER_AUTH_SECRET=
BETTER_AUTH_URL=http://localhost:3000
NEXT_PUBLIC_APP_URL=http://localhost:3000

# ---------Database----------
DATABASE_URL=

# ---------Email----------
RESEND_API_KEY=
RESEND_AUDIENCE_ID=

# ---------Auth----------
GITHUB_CLIENT_ID=
GITHUB_CLIENT_SECRET=
GOOGLE_CLIENT_ID=
GOOGLE_CLIENT_SECRET

# ---------Payment----------
STRIPE_SECRET_KEY=sk_test_
STRIPE_WEBHOOK_SECRET=whsec_
NEXT_PUBLIC_PRICE_ID_PRO_MONTHLY=price_
NEXT_PUBLIC_PRICE_ID_PRO_YEARLY=price_
NEXT_PUBLIC_PRICE_ID_LIFETIME=price_

# ---------Storage----------

NEXT_PUBLIC_AVATARS_BUCKET_NAME=nextdevkit-avatars

# Clouflare R2
STORAGE_REGION=auto
STORAGE_ACCESS_KEY_ID=
STORAGE_SECRET_ACCESS_KEY=
STORAGE_ENDPOINT=https://xxx.r2.cloudflarestorage.com

# S3
#STORAGE_REGION=us-east-1
#STORAGE_ACCESS_KEY_ID=
#STORAGE_SECRET_ACCESS_KEY=

# ---------Analytics----------

NEXT_PUBLIC_GOOGLE_ANALYTICS_ID=G-xxx

# Umami Analytics
NEXT_PUBLIC_UMAMI_WEBSITE_ID=
NEXT_PUBLIC_UMAMI_SCRIPT_URL=

# Plausible Analytics
NEXT_PUBLIC_PLAUSIBLE_DOMAIN=
NEXT_PUBLIC_PLAUSIBLE_SCRIPT_URL=

# ---------Affiliate----------
NEXT_PUBLIC_AFFILIATE_AFFONSO_ID=

🛠️ Development vs Production

Development Environment

• Use http://localhost:3000 for local URLs
• Use Stripe test keys (starting with sk_test_)
• OAuth redirect URIs should point to localhost

Production Environment

• Use your actual domain for all URLs
• Use Stripe live keys (starting with sk_live_)
• Configure OAuth providers with production redirect URIs
• Ensure all secrets are properly secured and rotated regularly

🔧 Next Steps

After setting up your environment variables:

1. Test authentication - Verify OAuth providers work correctly
2. Test email - Confirm email sending works with your provider
3. Deploy - Deploy to your chosen hosting platform

Your Next.js application is now ready for development and deployment! 🎉