Environment Variables

Installer-managed deployments keep /etc/arivu/arivu.env focused on machine configuration. Routine public URL, signup, cookie, model-provider, email, and X settings can be changed by an admin at runtime.

Core Runtime

Variable	Default	Purpose
`ARIVU_ADDR`	`:8080`	HTTP listen address
`ARIVU_DB`	`arivu.sqlite3`	SQLite database path
`APP_URL`	`http://localhost:8080`	Public URL and callback base
`SECRET_KEY`	development fallback	Sessions and encrypted runtime settings
`ADMIN_EMAILS`	empty	Comma-separated administrator emails
`SIGNUPS_ENABLED`	`true`	Public account registration
`COOKIE_SECURE`	`false`	Secure browser cookies, required behind production HTTPS
`ARIVU_FETCH_USER_AGENT`	`Arivu/2.0`	Server-side bookmark fetch identity

Generate a unique production secret and keep it outside version control:

SECRET_KEY=$(openssl rand -hex 32)

Changing SECRET_KEY invalidates sessions and affects encrypted runtime settings. Use the installer’s SQLite-consistent backup command instead of copying a live WAL database by hand.

Complete Browser Capture and Assets

The production installer owns the isolated native capture runtime and writes its machine configuration. Fresh supported installs enable it by default after presenting the plan; --browser-capture=false keeps the core-only direct-capture path. Use arivu-installer reconfigure rather than hand-editing the runtime command, socket, protocol, or limits.

Complete capture runs separately from the core Go application and does not use the signed-in user’s browser profile or cookies. The installer verifies and manages its pinned runtime through upgrades and rollback. Asset maintenance has a configurable garbage-collection grace period, and installer backups include the adjacent asset store with SQLite.

Optional Model Provider

Variable	Purpose
`AI_PROVIDER`	Provider mode
`AI_API_KEY`	Provider credential, optional for keyless local endpoints
`AI_MODEL`	Model identifier
`AI_BASE_URL`	Provider endpoint

Admins normally configure the equivalent Model Provider, Model, API Key, and Base URL fields in Admin settings. Runtime changes do not require a service restart. Remote base URLs must use HTTPS; localhost endpoints are allowed for development.

Legacy GEMINI_API_KEY, GEMINI_MODEL, and GEMINI_BASE_URL values still backfill Gemini deployments. Gemini-specific embeddings and image OCR remain optional. Arivu’s core workflow works without any provider.

Email

Variable	Purpose
`RESEND_API_KEY`	Password reset and optional reminder email
`RESEND_FROM_EMAIL`	Verified sender address

X Integration

Variable	Purpose
`X_INTEGRATION_ENABLED`	Enable optional X bookmark sync
`X_CLIENT_ID`	OAuth client ID
`X_CLIENT_SECRET`	OAuth client secret
`X_REDIRECT_URI`	Optional callback override
`X_API_BASE_URL`	Optional controlled endpoint override
`X_AUTHORIZE_URL`	Optional authorization endpoint override

See X Bookmarks Integration.

CLI

ARIVU_API supplies the default API base URL for CLI login:

ARIVU_API=https://your-domain.example/api ./arivu login \
  --email you@example.com \
  --password your-password

Minimal Production Profile

ARIVU_ADDR=127.0.0.1:8080
ARIVU_DB=/var/lib/arivu/arivu.sqlite3
APP_URL=https://your-domain.example
COOKIE_SECURE=true
SIGNUPS_ENABLED=false
ADMIN_EMAILS=admin@your-domain.example
SECRET_KEY=replace-with-a-unique-random-secret

Add only the optional provider and integration credentials you actually use.