.env.local file in your project root with the following configuration.
TMDB Configuration
The Movie Database (TMDB) provides all movie and TV show data.Your TMDB API access token (Bearer token format). Get your token from TMDB API Settings.
The base URL for TMDB API v3 endpoints.
Getting a TMDB API Key
- Create a free account at themoviedb.org
- Navigate to API Settings
- Request an API key (choose “Developer” option)
- Copy your API Read Access Token (v4 auth) - this is your Bearer token
- Use this token for
VITE_TMDB_ACCESS_TOKEN
Film Fanatic uses the access token (Bearer authentication) rather than the API key. Make sure to copy the “API Read Access Token” from your TMDB settings.
Clerk Authentication
Clerk handles user authentication, sign-in, and profile management.Your Clerk publishable key (client-side safe). Find this in your Clerk dashboard under API Keys.
Your Clerk secret key (server-side only). Keep this secure and never commit to version control.
Setting Up Clerk
- Create a free account at clerk.com
- Create a new application
- Copy your publishable and secret keys from the dashboard
- Configure your Clerk instance domain (see Authentication for details)
Convex Backend
Convex provides the real-time database and backend functions.Your Convex deployment URL. This is generated when you deploy your Convex backend.
Your Convex deploy key for production deployments. This is only needed for CI/CD pipelines.
Getting Convex Credentials
- Create a free account at convex.dev
- Run
npx convex devin your project directory - Follow the prompts to create a new project
- Your
VITE_CONVEX_URLwill be automatically added to.env.local - For production, run
npx convex deployand use the production URL
Complete Example
Here’s a complete.env.local file with all required variables:
.env.local
Environment-Specific Configuration
Development
For local development, use.env.local with test/development keys:
