You can choose from multiple authentication providers:
Pros: Easy setup, secure, no additional cost Cons: Requires Replit account
# Replit Auth Configuration
REPLIT_DOMAINS="your-domain.com"
REPL_ID="your-repl-id"
SESSION_SECRET="your-random-secret"
ISSUER_URL="https://replit.com/oidc"
AUTH_PROVIDER="replit"Pros: No external dependencies, immediate setup Cons: Less secure, single user only
# Simple Password Auth
ADMIN_USERNAME="admin"
ADMIN_PASSWORD="your-secure-password"
SESSION_SECRET="your-random-secret"
AUTH_PROVIDER="simple"Pros: Familiar to users, very secure Cons: Requires Google Developer Console setup
# Google OAuth Configuration
GOOGLE_CLIENT_ID="your-google-client-id"
GOOGLE_CLIENT_SECRET="your-google-client-secret"
GOOGLE_REDIRECT_URI="https://your-domain.com/api/auth/google/callback"
SESSION_SECRET="your-random-secret"
AUTH_PROVIDER="google"Pros: Professional grade, many features Cons: Paid service for production
# Auth0 Configuration
AUTH0_DOMAIN="your-auth0-domain"
AUTH0_CLIENT_ID="your-auth0-client-id"
AUTH0_CLIENT_SECRET="your-auth0-client-secret"
SESSION_SECRET="your-random-secret"
AUTH_PROVIDER="auth0"Your database can be hosted anywhere:
# Database Configuration (works with any PostgreSQL host)
DATABASE_URL="postgresql://user:password@host:port/database"
# Examples:
# AWS RDS: postgresql://user:pass@rds-instance.region.rds.amazonaws.com:5432/gamblecodez
# DigitalOcean: postgresql://user:pass@db-instance.region.do.com:25060/gamblecodez
# Railway: postgresql://user:pass@containers-us-west-1.railway.app:5432/railway
# Supabase: postgresql://user:pass@db.supabase.co:5432/postgres
# Local: postgresql://user:pass@localhost:5432/gamblecodezWould you like me to implement the simple password auth option so you can get started immediately without any external auth setup?