Configuration

Pricore is configured through environment variables in your .env file.

Essential Configuration

Application Settings

APP_NAME=Pricore
APP_ENV=production
APP_DEBUG=false
APP_URL=https://pricore.yourcompany.com

Variable	Description	Default
APP_NAME	Application name displayed in UI	Pricore
APP_ENV	Environment (local, production)	production
APP_DEBUG	Enable debug mode (disable in production)	false
APP_URL	Public URL of your Pricore instance	-

Registration

SIGN_UP_ENABLED=false

Variable	Description	Default
SIGN_UP_ENABLED	Allow public registration without an invitation	false

By default, registration is invite-only. Users can only create accounts after receiving an organization invitation. Set SIGN_UP_ENABLED=true to allow anyone to register.

Database Configuration

Pricore supports SQLite, MySQL, and PostgreSQL:

SQLite

DB_CONNECTION=sqlite
DB_DATABASE=/path/to/database.sqlite

MySQL

DB_CONNECTION=mysql
DB_HOST=127.0.0.1
DB_PORT=3306
DB_DATABASE=pricore
DB_USERNAME=pricore
DB_PASSWORD=secret

PostgreSQL

DB_CONNECTION=pgsql
DB_HOST=127.0.0.1
DB_PORT=5432
DB_DATABASE=pricore
DB_USERNAME=pricore
DB_PASSWORD=secret

Redis Configuration

Redis is required for queues, caching, and sessions:

REDIS_HOST=127.0.0.1
REDIS_PORT=6379
REDIS_PASSWORD=null

QUEUE_CONNECTION=redis
CACHE_STORE=redis
SESSION_DRIVER=redis

Git Provider Configuration

To sync packages from Git repositories, configure your provider credentials.

GitHub

GITHUB_CLIENT_ID=your-github-client-id
GITHUB_CLIENT_SECRET=your-github-client-secret
GITHUB_REDIRECT_URI=${APP_URL}/auth/github/callback

Variable	Description	Default
GITHUB_CLIENT_ID	GitHub OAuth App client ID	-
GITHUB_CLIENT_SECRET	GitHub OAuth App client secret	-
GITHUB_REDIRECT_URI	OAuth callback URL	{APP_URL}/auth/github/callback

Create a GitHub OAuth App:

1. Go to GitHub Settings > Developer settings > OAuth Apps
2. Click "New OAuth App"
3. Set the callback URL to {APP_URL}/auth/github/callback

GitLab

GITLAB_CLIENT_ID=your-gitlab-client-id
GITLAB_CLIENT_SECRET=your-gitlab-client-secret
GITLAB_REDIRECT_URI=${APP_URL}/auth/gitlab/callback
GITLAB_INSTANCE_URI=https://gitlab.com  # or your self-hosted GitLab URL

Variable	Description	Default
GITLAB_CLIENT_ID	GitLab OAuth Application ID	-
GITLAB_CLIENT_SECRET	GitLab OAuth Application secret	-
GITLAB_REDIRECT_URI	OAuth callback URL	{APP_URL}/auth/gitlab/callback
GITLAB_INSTANCE_URI	GitLab instance URL (for self-hosted)	https://gitlab.com

Create a GitLab OAuth Application:

GitLab.com:

1. Go to GitLab User Settings > Applications
2. Click "Add new application"
3. Set the Redirect URI to {APP_URL}/auth/gitlab/callback
4. Select scopes: read_user and api
   • read_user — used for login/sign-up (reading user profile and email)
   • api — used when connecting GitLab as a git credential (reading repositories, file content, and managing webhooks). GitLab does not offer a narrower scope for webhook management.
5. Click "Save application" and copy the Application ID and Secret

Self-hosted GitLab:

1. Go to your GitLab instance > User Settings > Applications
2. Follow the same steps as above
3. Set GITLAB_INSTANCE_URI to your instance URL (e.g., https://gitlab.example.com/)

Mail Configuration

Configure mail for password resets and notifications:

MAIL_MAILER=smtp
MAIL_HOST=smtp.mailgun.org
MAIL_PORT=587
MAIL_USERNAME=your-username
MAIL_PASSWORD=your-password
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS=noreply@yourcompany.com
MAIL_FROM_NAME="${APP_NAME}"

Horizon (Queue Dashboard)

Pricore uses Laravel Horizon to manage queue workers. The following variables configure the Horizon dashboard:

HORIZON_ALLOWED_EMAILS=admin@yourcompany.com,ops@yourcompany.com
HORIZON_PATH=horizon

Variable	Description	Default
HORIZON_ALLOWED_EMAILS	Comma-separated list of emails allowed to access the Horizon dashboard (in non-local environments)	'' (empty)
HORIZON_NAME	Name displayed in the Horizon UI and notifications	-
HORIZON_DOMAIN	Subdomain to serve Horizon from (e.g., horizon.yourcompany.com)	null (same domain)
HORIZON_PATH	URI path for the Horizon dashboard	horizon
HORIZON_PREFIX	Redis key prefix for Horizon data	{app_name}_horizon:

Slack Notifications

To send notifications to Slack, configure a bot token:

SLACK_BOT_USER_OAUTH_TOKEN=xoxb-your-bot-token
SLACK_BOT_USER_DEFAULT_CHANNEL=#packages

Variable	Description	Default
SLACK_BOT_USER_OAUTH_TOKEN	Slack bot user OAuth token	-
SLACK_BOT_USER_DEFAULT_CHANNEL	Default Slack channel for notifications	-

Error Tracking (Sentry)

Pricore supports Sentry for error tracking and performance monitoring:

SENTRY_LARAVEL_DSN=https://examplePublicKey@o0.ingest.sentry.io/0
SENTRY_ENVIRONMENT=production
SENTRY_TRACES_SAMPLE_RATE=0.2

Variable	Description	Default
SENTRY_LARAVEL_DSN	Sentry DSN URL (falls back to SENTRY_DSN)	-
SENTRY_RELEASE	Release version tag sent to Sentry	-
SENTRY_ENVIRONMENT	Environment name in Sentry	APP_ENV value
SENTRY_SAMPLE_RATE	Error event sample rate (0.0 to 1.0)	1.0
SENTRY_TRACES_SAMPLE_RATE	Performance traces sample rate (0.0 to 1.0)	null (disabled)
SENTRY_PROFILES_SAMPLE_RATE	Profiling sample rate (0.0 to 1.0)	null (disabled)
SENTRY_ENABLE_LOGS	Send logs to Sentry	false
SENTRY_LOG_LEVEL	Minimum log level sent to Sentry	debug
SENTRY_SEND_DEFAULT_PII	Include personally identifiable information	false

Security Settings

Trusted Proxies

When running behind a load balancer or reverse proxy, configure trusted proxies:

TRUSTED_PROXIES=192.168.1.0/24,10.0.0.0/8

Variable	Description	Default
TRUSTED_PROXIES	Comma-separated list of trusted proxy IP addresses or CIDR ranges. Use * to trust all proxies.	'' (empty)

Two-Factor Authentication

Two-factor authentication is enabled by default. Users can enable it in their account settings.

Session Security

SESSION_LIFETIME=120  # minutes
SESSION_SECURE_COOKIE=true  # require HTTPS

Performance Tuning

Queue Workers

For production, use Laravel Horizon to manage queue workers:

# Horizon is included and configured by default
php artisan horizon

Caching

Enable config and route caching for production:

php artisan config:cache
php artisan route:cache
php artisan view:cache

Complete Example

Here's a complete production .env example:

APP_NAME=Pricore
APP_ENV=production
APP_KEY=base64:your-generated-key
APP_DEBUG=false
APP_URL=https://pricore.yourcompany.com

SIGN_UP_ENABLED=false

DB_CONNECTION=pgsql
DB_HOST=127.0.0.1
DB_PORT=5432
DB_DATABASE=pricore
DB_USERNAME=pricore
DB_PASSWORD=secure-password

REDIS_HOST=127.0.0.1
REDIS_PORT=6379

CACHE_STORE=redis
SESSION_DRIVER=redis
QUEUE_CONNECTION=redis

MAIL_MAILER=smtp
MAIL_HOST=smtp.mailgun.org
MAIL_PORT=587
MAIL_USERNAME=postmaster@yourcompany.com
MAIL_PASSWORD=your-mail-password
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS=packages@yourcompany.com
MAIL_FROM_NAME="${APP_NAME}"

GITHUB_CLIENT_ID=your-github-client-id
GITHUB_CLIENT_SECRET=your-github-client-secret

GITLAB_CLIENT_ID=your-gitlab-client-id
GITLAB_CLIENT_SECRET=your-gitlab-client-secret
# GITLAB_INSTANCE_URI=https://gitlab.example.com  # uncomment for self-hosted

HORIZON_ALLOWED_EMAILS=admin@yourcompany.com

SENTRY_LARAVEL_DSN=https://examplePublicKey@o0.ingest.sentry.io/0

TRUSTED_PROXIES=