.env.example

# QuickKee OAuth Configuration
# Copy this file to .env.local and fill in your credentials

# =====================================
# Dropbox OAuth Configuration
# =====================================
# Register your app at: https://www.dropbox.com/developers/apps
# 1. Create a new app (Scoped access, Full Dropbox or App folder)
# 2. In the Settings tab, copy the "App key" as VITE_DROPBOX_CLIENT_ID
# 3. Add the redirect URI: https://<extension-id>.chromiumapp.org/
#    (The extension ID is shown when loading the unpacked extension in chrome://extensions)

VITE_DROPBOX_CLIENT_ID=your_dropbox_app_key_here
# Optional: Client secret (for server-side/confidential clients only)
# For browser extensions, PKCE is preferred and client_secret is optional
VITE_DROPBOX_CLIENT_SECRET=your_dropbox_app_secret_here_optional

# =====================================
# Google Drive OAuth Configuration
# =====================================
# Register your app at: https://console.cloud.google.com/apis/credentials
# 1. Create a new project (or select existing)
# 2. Enable the Google Drive API
# 3. Create OAuth 2.0 Client ID (Chrome extension type)
# 4. Copy the Client ID as VITE_GOOGLE_CLIENT_ID
# 5. Add the extension's OAuth redirect URL

VITE_GOOGLE_CLIENT_ID=your_google_client_id_here.apps.googleusercontent.com

# =====================================
# Development Notes
# =====================================
# - Environment variables prefixed with VITE_ are exposed to the client
# - Never commit real credentials to version control
# - For development, mock OAuth flows are used when credentials are not configured