Overview

You configure IntelliAsk through two files you edit directly -- .env and intelliask.yaml. Docker service definitions are managed for you by the intelliask binary and normally don't need to be touched.

Common Change Workflow

Most configuration changes follow the same pattern:

1. Edit .env for secrets, API keys, and server-level feature flags.
2. Edit intelliask.yaml for custom endpoints, model specs, interface settings, MCP servers, agents, and advanced app behavior.
3. Restart IntelliAsk after every configuration change.
4. Check the API logs if the change does not appear in the UI.

For example, to enable OpenRouter you add OPENROUTER_KEY to .env, add an OpenRouter endpoint in intelliask.yaml, restart, then select OpenRouter from the endpoint selector.

Configuration Files

.env -- Server-level settings: API keys, database connection strings, feature flags, and authentication secrets. This is the primary configuration file for most deployments. See the .env reference for all available variables.

intelliask.yaml -- Custom AI endpoints, model settings, interface options, and advanced features like MCP servers and agents. This file is optional -- IntelliAsk works with defaults if it does not exist. It is already mounted into the stack for you, so changes take effect after a restart. See the intelliask.yaml guide for setup instructions.

*.compose.yml -- The bundled Docker service definitions (API server, database, search, and supporting services) that the intelliask binary orchestrates for you. You normally don't edit these directly.

docker-compose.override.yml -- Optional, not included by default. A suggested best-practice for advanced users who want to customize services (volume mounts, port mappings, environment overrides, or swapping in external infrastructure) without editing the bundled compose files. If you create one in config/, Docker Compose merges it automatically. See the Docker override guide.

Applying Changes

intelliask restart

Next Steps