Environment variables

DoctorSoft+ requires specific environment variables to connect to Supabase and configure application behavior. All environment variables must be prefixed with VITE_ to be accessible in the client-side application.

Required variables

These environment variables are required for the application to function:

`VITE_SUPABASE_URL`

VITE_SUPABASE_URL

string

required

The URL of your Supabase project.

Description: The base URL for your Supabase instance. This is used to connect to your Supabase database, authentication, and storage services. Example:

VITE_SUPABASE_URL=https://0ec90b57d6e95fcbda19832f.supabase.co

Where to find it:

Go to your Supabase Dashboard
Select your project
Navigate to Settings > API
Copy the “Project URL” value

The build will fail if this variable is not set. Ensure it’s configured before deploying.

`VITE_SUPABASE_ANON_KEY`

VITE_SUPABASE_ANON_KEY

string

required

The anonymous (public) API key for your Supabase project.

Description: The public anon key used for client-side authentication and database access. This key is safe to expose in client-side code and respects Row Level Security (RLS) policies. Example:

VITE_SUPABASE_ANON_KEY=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJib2x0IiwicmVmIjoiMGVjOTBiNTdkNmU5NWZjYmRhMTk4MzJmIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NTg4ODE1NzQsImV4cCI6MTc1ODg4MTU3NH0.9I8-U0x86Ak8t2DGaIk0HfvTSLsAyzdnz-Nw00mMkKw

Where to find it:

Go to your Supabase Dashboard
Select your project
Navigate to Settings > API
Copy the “anon public” key under “Project API keys”

The build will fail if this variable is not set. This is your project’s public key, not the service role key.

Optional variables

These environment variables have default values and are optional:

`VITE_MAX_FILE_SIZE_MB`

VITE_MAX_FILE_SIZE_MB

number

default:"10"

Maximum file upload size in megabytes.

Description: Controls the maximum size allowed for file uploads in the application. Files larger than this limit will be rejected before uploading to Supabase Storage. Default: 10 (MB) Example:

VITE_MAX_FILE_SIZE_MB=10

Usage in code: src/components/FileUpload.tsx:48 and src/FileUpload.tsx:46

If not set, the application will use the default value of 10MB and log a warning in the console.

`VITE_BUCKET_NAME`

VITE_BUCKET_NAME

string

default:"00000000-default-bucket"

The name of the Supabase Storage bucket for file uploads.

Description: Specifies which Supabase Storage bucket to use for file uploads. This bucket must exist in your Supabase project. Default: 00000000-default-bucket Example:

VITE_BUCKET_NAME=medical-documents

Usage in code: src/components/FileUpload.tsx:49 and src/FileUpload.tsx:47

Ensure the bucket exists in your Supabase project (Dashboard > Storage) and has appropriate RLS policies configured.

`VITE_APP_VERSION`

VITE_APP_VERSION

string

default:"dev"

Application version string sent in API headers.

Description: Version identifier sent in the x-application-name header with Supabase requests. Useful for tracking which version of the app is making requests. Default: dev Example:

VITE_APP_VERSION=25.40

Usage in code: src/supabase.ts:75 and src/lib/supabase.ts:75

`VITE_SUPABASE_DETECT_SESSION_IN_URL`

VITE_SUPABASE_DETECT_SESSION_IN_URL

boolean

default:"false"

Enable OAuth session detection from URL parameters.

Description: Controls whether the Supabase client should automatically detect and handle OAuth sessions from URL parameters. This is only needed if you’re using OAuth providers (Google, GitHub, etc.). Default: false (disabled for better performance) Example:

VITE_SUPABASE_DETECT_SESSION_IN_URL=true

Usage in code: src/supabase.ts:78 and src/lib/supabase.ts:78

This is disabled by default to improve performance. Only enable if you’re using OAuth authentication providers.

`VITE_OPENAI_API_KEY`

VITE_OPENAI_API_KEY

string

OpenAI API key for AI-powered features.

Description: API key for OpenAI services used in AI-powered features of the application. This is optional and only required if you’re using AI features. Example:

VITE_OPENAI_API_KEY=sk-...

Usage in code: src/services/openaiService.ts:13

This key is exposed in client-side code. Consider using a backend proxy for production to keep the API key secure.

Setting environment variables

How you set environment variables depends on your deployment platform:

Local development

Create a .env file in the root of your project:

# .env
VITE_SUPABASE_URL=https://your-project.supabase.co
VITE_SUPABASE_ANON_KEY=your-anon-key
VITE_MAX_FILE_SIZE_MB=10
VITE_BUCKET_NAME=your-bucket-name

Never commit your .env file to version control. Add it to .gitignore.

Netlify

Go to Site Settings > Build & Deploy > Environment
Click “Add a variable”
Add each environment variable and its value
Deploy or re-deploy your site

See the Netlify deployment guide for detailed instructions.

Vercel

Go to Project Settings > Environment Variables
Add each environment variable
Select which environments to apply to (Production, Preview, Development)
Save and re-deploy

See the Vercel deployment guide for detailed instructions.

Docker

Pass environment variables when running the container:

docker run -d \
  -e VITE_SUPABASE_URL=https://your-project.supabase.co \
  -e VITE_SUPABASE_ANON_KEY=your-anon-key \
  -e VITE_MAX_FILE_SIZE_MB=10 \
  -e VITE_BUCKET_NAME=your-bucket-name \
  -p 3000:3000 \
  doctorsoft-plus

See the Docker deployment guide for detailed instructions.

Build-time validation

The Vite configuration (vite.config.ts:5-27) validates environment variables at build time:

const requiredEnvVars = [
  { name: 'VITE_SUPABASE_URL', required: true },
  { name: 'VITE_SUPABASE_ANON_KEY', required: true },
  { name: 'VITE_MAX_FILE_SIZE_MB', required: false, default: '10' },
  { name: 'VITE_BUCKET_NAME', required: false, default: '00000000-default-bucket' }
];

let hasErrors = false;
for (const envVar of requiredEnvVars) {
  if (!process.env[envVar.name]) {
    if (envVar.required) {
      console.error(`ERROR: ${envVar.name} is required but not set`);
      hasErrors = true;
    } else {
      console.log(`Info: ${envVar.name} not set, will use default: ${envVar.default}`);
    }
  }
}

If required variables are missing, the build will log errors to help you identify configuration issues.

Security considerations

All VITE_ environment variables are exposed in the client-side bundle. Never store secrets or private keys in these variables.

Safe to expose:

VITE_SUPABASE_URL - Public URL
VITE_SUPABASE_ANON_KEY - Public anon key (respects RLS)
Other VITE_ prefixed configuration values

Never expose:

Service role keys
Database passwords
Private API keys (unless proxied through a backend)
Secrets or tokens

Next steps

Deploy to Netlify

Configure environment variables in Netlify

Deploy to Vercel

Configure environment variables in Vercel

Docker Deployment

Pass environment variables to Docker containers

Deployment Overview

Back to deployment overview

Deployment

Database

​Required variables

​VITE_SUPABASE_URL

​VITE_SUPABASE_ANON_KEY

​Optional variables

​VITE_MAX_FILE_SIZE_MB

​VITE_BUCKET_NAME

​VITE_APP_VERSION

​VITE_SUPABASE_DETECT_SESSION_IN_URL

​VITE_OPENAI_API_KEY

​Setting environment variables

​Local development

​Netlify

​Vercel

​Docker

​Build-time validation

​Security considerations

​Next steps

Deploy to Netlify

Deploy to Vercel

Docker Deployment

Deployment Overview

Build docs developers (and LLMs) love

Required variables

`VITE_SUPABASE_URL`

`VITE_SUPABASE_ANON_KEY`

Optional variables

`VITE_MAX_FILE_SIZE_MB`

`VITE_BUCKET_NAME`

`VITE_APP_VERSION`

`VITE_SUPABASE_DETECT_SESSION_IN_URL`

`VITE_OPENAI_API_KEY`

Setting environment variables

Local development

Netlify

Vercel

Docker

Build-time validation

Security considerations

Next steps