-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathenv-instructions.txt
More file actions
36 lines (28 loc) · 1.46 KB
/
env-instructions.txt
File metadata and controls
36 lines (28 loc) · 1.46 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
# Instructions for setting up your .env file
Create a file named .env in the project root with the following contents:
```
# Supabase Configuration
VITE_SUPABASE_URL=your-supabase-project-url
VITE_SUPABASE_ANON_KEY=your-supabase-anon-key
# GitHub OAuth Configuration
VITE_GITHUB_CLIENT_ID=your-github-client-id
# Other Configuration
VITE_APP_URL=http://localhost:3489
VITE_POLLINATIONS_API_TOKEN=optional-pollinations-api-token
```
Replace the placeholder values with your actual Supabase, GitHub credentials, and (optionally) your Pollinations token:
1. For Supabase:
- Go to your Supabase project dashboard: https://app.supabase.com/projects
- Click on your project
- Go to Settings > API
- Copy the "Project URL" to VITE_SUPABASE_URL
- Copy the "anon public" key to VITE_SUPABASE_ANON_KEY
2. For GitHub OAuth:
- Go to GitHub Developer Settings: https://github.com/settings/developers
- Create a new OAuth App or select an existing one
- Copy the Client ID to VITE_GITHUB_CLIENT_ID
- Set the Authorization callback URL to http://localhost:3489/auth/callback
3. For Pollinations (optional but recommended if you want authenticated requests and guaranteed watermark-free images):
- Generate or retrieve your Pollinations API token
- Add it to `VITE_POLLINATIONS_API_TOKEN`
- When deploying to Cloudflare Pages, run `wrangler secret put POLLINATIONS_API_TOKEN` to mirror the value for the production proxy endpoint