ℹ️ .env variables are loaded automatically by Vite. Refer to this documentation for more information. Loading Environment Variables.
Good to know:
.env,.env.development, and.env.productionfiles should be included in your repository as they define defaults. .env*.local should be added to .gitignore, as those files are intended to be ignored. .env.local is where secrets can be stored.
| Key | Responsible | Type | Secret | Policy | Default value | Description | Docs |
|---|---|---|---|---|---|---|---|
VITE_APP_API_URL |
DevOps | string |
No | DEFAULT |
http://localhost:3000 |
GQL API URL URL | |
VITE_APP_ANOTHER_API_URL |
DevOps | string |
No | DEFAULT |
http://localhost:3000 |
REST API URL URL | - |
VITE_APP_GRAPHQL_PROXY_ENDPOINT |
DevOps | string |
No | REQUIRED-IN-RELEASE-ENV |
- | GQL Proxy Endpoint URL | - |
VITE_APP_REST_PROXY_ENDPOINT |
DevOps | string |
No | REQUIRED-IN-RELEASE-ENV |
- | REST Proxy Endpoint DSN | |
VITE_APP_SENTRY_DSN |
DevOps | string |
No | REQUIRED-IN-RELEASE-ENV |
- | Sentry DSN | Sentry DSN |
VITE_APP_SENTRY_ENABLED |
DevOps | boolean |
No | FEATURE-FLAG |
- | Enables/Disables Sentry monitoring | - |
DEFAULT: This environment variable has a default value that works on most common usagesREQUIRED: This environment variable must be set, otherwise the application will not start throwing an exceptionREQUIRED-IN-RELEASE-ENV: This environment variable must be set in release environments, the application will start but won't comply requirements: security, functionality, integration, performance, etcFEATURE-FLAG: This environment variable changes a feature behaviorDEPRECATED: Deprecated variables, see deprecated variables section
boolean: string variable containing a boolean valuestring: string variablefs_path: string variable containing a path in the file systememail: string variable containing an emailstring-list-by-comma: list string values extracted by: split (using,as the separator) and trim