Skip to main content
Use the in-app Settings page for a personal instance. Use environment variables for repeatable deployments, centrally managed secrets, or instances where users must not change provider credentials.

​
Where configuration comes from

Environment variables supplied to the container take precedence over interactive setup for the corresponding deployment configuration. Set CAN_CHANGE_KEYS=false when administrators—not application users—should control provider credentials.

​
Start with persistence

Mount /app_data on durable storage. It contains presentations, uploaded assets, templates, settings, exports, the default database, authentication state, and local presentation memory.
Back up this location before upgrades. If you use an external database, back up both the database and /app_data because files and application state are not limited to database records.

​
A practical .env file

The following example enables a hosted text provider, stock images, authentication, web search, and persistent local memory:
Place .env beside the repository’s docker-compose.yml, then run:
Do not commit .env, API keys, passwords, bearer tokens, or cloud credentials. Use restricted file permissions or your deployment platform’s secret manager.

​
Configuration map

Configure by goal

Start with a feature and see the exact ports, variables, and actions it requires.

Text providers

Configure hosted models, local runtimes, gateways, and compatible endpoints.

Images and web search

Select stock or generated images and optional research providers.

ComfyUI

Connect a local or hosted ComfyUI server and API-format workflow.

Storage and processing

Configure the database, memory, document parsing, telemetry, and app data.

Authentication

Protect the UI, REST API, and MCP server with the single admin account.

​
Keep provider roles separate

The text provider writes the deck. The image provider creates or finds visuals. The search provider supplies optional web context. They can be different services, which lets you combine a local text model with stock images or a hosted text model with private SearXNG search.

​
Configuration rollout checklist

  • Mount and back up /app_data.
  • Select one text provider and test a short generation.
  • Select an image provider or explicitly disable image generation.
  • Keep web search off unless the workflow needs current information.
  • Configure authentication before exposing the instance beyond localhost.
  • Store provider credentials outside source control.
  • Restart the deployment after changing environment variables.
  • Re-run a short generation after provider or model changes.
localhost inside a container points to that container. Use a reachable Compose service name, container hostname, or host gateway such as host.docker.internal for a service running on the Docker host.