Configuration
Reference for all oCore configuration options including environment variables, backend settings, and frontend build-time configuration.
oCore is configured primarily through environment variables. This section provides a complete reference for every configuration option available in the backend and frontend.
Configuration Methods
oCore loads configuration from environment variables at startup. There is no configuration file to manage. This approach works well with Docker, systemd, and CI/CD pipelines.
For Docker Compose deployments, set variables in a .env file alongside your docker-compose.prod.yml:
DATABASE_URL=postgres://ocore:password@postgres:5432/ocore?sslmode=disable
JWT_SECRET=your-secret-at-least-32-characters
APP_URL=https://ocore.example.comEnvironment Variables
Complete reference of every environment variable with type, default value, and description.
Backend Configuration
Backend-specific configuration details, validation rules, and runtime behavior.
Frontend Configuration
Frontend build-time and runtime configuration with NEXT_PUBLIC_ variables.
Quick Reference
The most commonly configured variables for a production deployment:
| Variable | Required | Purpose |
|---|---|---|
DATABASE_URL | Yes | PostgreSQL connection string |
JWT_SECRET | Yes | JWT signing key (min 32 characters) |
APP_URL | Recommended | Public URL of the dashboard |
SMTP_HOST | Recommended | Email delivery for verification and notifications |
SSH_ENCRYPTION_KEY | Production | Encryption key for stored SSH credentials |
NEXT_PUBLIC_API_URL | Yes | Backend API URL for the frontend |
See the Environment Variables page for the full list.