Environment Variables

Welcome to the comprehensive guide for configuring your application's environment with the .env file. This document is your one-stop resource for understanding and customizing the environment variables that will shape your application's behavior in different contexts.

While the default settings provide a solid foundation for a standard installation, delving into this guide will unveil the full potential of IntelliAsk. This guide empowers you to tailor IntelliAsk to your precise needs. Discover how to adjust language model availability, integrate social logins, manage the automatic moderation system, and much more. It's all about giving you the control to fine-tune IntelliAsk for an optimal user experience.

Reminder: Please restart IntelliAsk for configuration changes to take effect — use ./intelliask restart or ./intelliask up (with the binary), or docker compose up -d (if deploying manually).

Server Configuration

Port

• The server listens on a specific port.
• The PORT environment variable sets the port where the server listens. By default, it is set to 3080.

Trust proxy

Use the address that is at most n number of hops away from the Express application. req.socket.remoteAddress is the first hop, and the rest are looked for in the X-Forwarded-For header from right to left. A value of 0 means that the first untrusted address would be req.socket.remoteAddress, i.e. there is no reverse proxy. The TRUST_PROXY environment variable default is set to 1.

Refer to Express.js - trust proxy for more information about this.

HTTP Server Timeouts

Tune the Node.js HTTP server timeouts. All values are non-negative milliseconds; 0 disables the corresponding timeout.

Credentials Configuration

To securely store credentials, you need a fixed key and IV. You can set them here for prod and dev environments.

Static File Handling

Behaviour:

Sets the Cache-Control headers for static files. These configurations only trigger when the NODE_ENV is set to production.

• Uncomment STATIC_CACHE_MAX_AGE to change the local max-age for static files. By default this is set to 2 days (172800 seconds).
• Uncomment STATIC_CACHE_S_MAX_AGE to set the s-maxage for shared caches (CDNs and proxies). By default this is set to 1 day (86400 seconds).
• Uncomment DISABLE_COMPRESSION to disable compression for static files. By default, compression is enabled.
• Uncomment ENABLE_IMAGE_OUTPUT_GZIP_SCAN to enable scanning and serving of gzipped version of images if they have been pre-compressed in the same folder, with the same name and a .gz extension. By default, gzip scan for uploaded images is disabled.
• Uncomment ENABLE_STATIC_ASSET_BROTLI to serve precompressed .br versions of static app assets when they exist. When enabled, Brotli is preferred before gzip for API-served static files.

Index HTML Cache Control

Behaviour:

Controls caching headers specifically for the index.html response. By default, these settings prevent caching to ensure users always get the latest version of the application.

MongoDB Database

Change this to your MongoDB URI if different. The database name should match your APP_TITLE (default: IntelliAsk).

If you are using an online database, the URI format is mongodb+srv://<username>:<password>@<host>/<database>?<options>. Your MONGO_URI should look like this:

• mongodb+srv://username:password@host.mongodb.net/IntelliAsk?retryWrites=true (retryWrites is the only option you need when using the online database.)

MongoDB Connection Pool Configuration

MongoDB Schema Configuration

Alternatively you can use documentDb that emulates mongoDb but it:

• does not support retryWrites - use retryWrites=false
• requires TLS connection, hence use parameters tls=true to enable TLS and tlsCAFile=/path-to-ca/bundle.pem to point to the AWS provided CA bundle file

The URI for documentDb will look like:

• mongodb+srv://username:password@domain/dbname?retryWrites=false&tls=true&tlsCAFile=/path-to-ca/bundle.pem

See also:

• MongoDB Atlas for instructions on how to create an online MongoDB Atlas database (useful for use without Docker)
• MongoDB Community Server for instructions on how to create a local MongoDB database (without Docker)
• MongoDB Authentication To enable explicit authentication for MongoDB in Docker.
• Manage your database with Mongo Express for securely accessing your Docker MongoDB database

Application Domains

To configure IntelliAsk for local use or custom domain deployment, set the following environment variables:

When deploying IntelliAsk to a custom domain, replace http://localhost:3080 with your deployed URL

• e.g. https://intelliask.example.com.

Prevent Public Search Engines Indexing

By default, your website will not be indexed by public search engines (e.g. Google, Bing, …). This means that people will not be able to find your website through these search engines. If you want to make your website more visible and searchable, you can change the following setting to false

❗Note: This method is not guaranteed to work for all search engines, and some search engines may still index your website or web page for other purposes, such as caching or archiving. Therefore, you should not rely solely on this method to protect sensitive or confidential information on your website or web page.

Logging

IntelliAsk has built-in central logging, see Logging System for more info.

Log Files

• Debug logging is enabled by default and crucial for development.
• To report issues, reproduce the error and submit the logs from ./api/logs/debug-%DATE%.log to your IntelliAsk support contact.
• Error logs are stored in the same location.

Environment Variables

Note:

• DEBUG_LOGGING can be used with either DEBUG_CONSOLE or CONSOLE_JSON but not both.
• DEBUG_CONSOLE and CONSOLE_JSON are mutually exclusive.
• CONSOLE_JSON: When handling console logs in cloud deployments (such as GCP or AWS), enabling this will dump the logs with a UTC timestamp and format them as JSON.

Note: DEBUG_CONSOLE is not recommended, as the outputs can be quite verbose, and so it's disabled by default.

Permission

UID and GID are numbers assigned by Linux to each user and group on the system. If you have permission problems, set here the UID and GID of the user running the Docker Compose command. The applications in the container will run with these UID/GID.

OpenTelemetry Tracing

IntelliAsk can emit backend OpenTelemetry traces for general API, HTTP, MongoDB, Mongoose, Redis, and outbound request visibility. Redis command-level spans are opt-in so default traces stay high-level. Use Langfuse for GenAI-specific prompt/model observability.

Real User Monitoring (Browser)

IntelliAsk can publish browser Real User Monitoring (RUM) telemetry to HyperDX-compatible OTLP collectors. RUM is disabled by default.

In publicToken mode, the browser sends telemetry directly to RUM_URL with RUM_PUBLIC_TOKEN. In proxy mode, the browser sends telemetry through IntelliAsk; the backend validates the user session, strips app authentication headers, and forwards telemetry to RUM_PROXY_TARGET_URL. Invalid or expired sessions are dropped with a 204 response so browser telemetry failures do not surface normal API authentication errors. Proxy outcomes are counted in rum_proxy_requests_total with endpoint and result labels on the IntelliAsk API /metrics endpoint.

Configuration Path - intelliask.yaml

Specify an alternative location for the IntelliAsk configuration file. You may specify an absolute path, a relative path, or a URL. The filename in the path is flexible and does not have to be intelliask.yaml; any valid configuration file will work.

Note: If you prefer IntelliAsk to search for the configuration file in the root directory (which is the default behavior), simply leave this option commented out.

Deployment Skills

Deployment Skills are loaded read-only at startup from the filesystem and exposed to users who have the Skills capability enabled.

Restart IntelliAsk after changing this directory or any files inside it. Deployment-provided Skills take precedence over persisted Skills with the same name.

Configuration Validation

By default, IntelliAsk will exit with an error (exit code 1) if the intelliask.yaml configuration file contains validation errors. This fail-fast behavior helps catch configuration issues early in deployment pipelines and prevents running with unintended default settings.

Uncaught Exception Handling

By default, IntelliAsk will exit the process when an uncaught exception occurs, which is the standard Node.js behavior. You can override this to keep the app running after uncaught exceptions.

Endpoints

In this section, you can configure the endpoints and models selection, their API keys, and the proxy and reverse proxy settings for the endpoints that support it.

General Config

Uncomment ENDPOINTS to customize the available endpoints in IntelliAsk.

Known Endpoints - intelliask.yaml

• see also: Custom Endpoints & Configuration

Web Search

The web search feature enables internet search capabilities within IntelliAsk.

Important: The exact environment variable names shown below are default references and can be customized through the intelliask.yaml configuration file to use any variable names you prefer.

For detailed configuration and customization options, see: Web Search Configuration

Note: These variable names can be customized in your intelliask.yaml configuration file. For example, you could use CUSTOM_SERPER_KEY instead of SERPER_API_KEY by configuring it in the web search settings. See the Web Search Configuration documentation for details on customizing variable names.

Anthropic

see: Anthropic Endpoint

• You can request an access key from https://platform.claude.com/
• Leave ANTHROPIC_API_KEY= blank to disable this endpoint
• Set ANTHROPIC_API_KEY= to "user_provided" to allow users to provide their own API key from the WebUI
• If you have access to a reverse proxy for Anthropic, you can set it with ANTHROPIC_REVERSE_PROXY=
  • leave blank or comment it out to use default base url

• ANTHROPIC_TITLE_MODEL is now deprecated and will be removed in future versions. Use the titleModel Endpoint Setting instead in the intelliask.yaml config instead.

Note: Must be compatible with the Anthropic Endpoint. Also, Claude 2 and Claude 3 models perform best at this task, with claude-3-haiku models being the cheapest.

Claude Fable 5 is included in the default Anthropic model list. Fable/Mythos-class models use the modern Anthropic behavior in IntelliAsk: 1M context, adaptive thinking support, prompt caching support, and thinkingDisplay handling for summarized or omitted reasoning output.

Anthropic via Vertex AI

You can also use Anthropic Claude models through Google Cloud Vertex AI. For detailed YAML configuration options, see: Anthropic Vertex AI Configuration

Note: When using Vertex AI, you must also configure GOOGLE_SERVICE_KEY_FILE (see Google Configuration) with a service account that has the Vertex AI User role.

AWS Bedrock

See: AWS Bedrock Setup

Note: You can omit the access keys to use the default AWS credentials chain (environment variables, SSO credentials, shared credentials files, or EC2/ECS Instance Metadata Service). See AWS Bedrock Setup for more details.

Claude Fable/Mythos-class models on Bedrock are inference-profile only. Use a profile ID such as us.anthropic.claude-fable-5, and enable the required Anthropic data sharing setting in the Bedrock console or Data Retention API before invoking them.

BingAI

Bing, also used for Sydney, jailbreak, and Bing Image Creator

Note: It is recommended to leave it as "user_provided" and provide the token from the WebUI.

Google

Follow these instructions to setup the Google Endpoint

Customize the available models, separated by commas, without spaces. The first will be default. Leave it blank or commented out to use internal settings.

• GOOGLE_TITLE_MODEL is now deprecated and will be removed in future versions. Use the titleModel Endpoint Setting instead in the intelliask.yaml config instead.

Note: For the Vertex AI GOOGLE_SAFETY variables, you do not have access to the BLOCK_NONE setting by default. To use this restricted HarmBlockThreshold setting, you will need to either:

• (a) Get access through an allowlist via your Google account team
• (b) Switch your account type to monthly invoiced billing following this instruction: https://cloud.google.com/billing/docs/how-to/invoiced-billing

Gemini Image Generation

Gemini Image Generation is a tool for Agents that supports both the Gemini API and Vertex AI. See: Gemini Image Generation

Note: When no API key is configured, the tool automatically falls back to Vertex AI using the service account from GOOGLE_SERVICE_KEY_FILE. The service account must have the Vertex AI User role.

OpenAI

See: OpenAI Setup

• OPENAI_TITLE_MODEL is now deprecated and will be removed in future versions. Use the titleModel Endpoint Setting instead in the intelliask.yaml config instead.
• OPENAI_REVERSE_PROXY is now deprecated and will be removed in future versions. Use a custom endpoint instead.

Assistants

See: Assistants Setup

Note: You can customize the available models, separated by commas, without spaces. The first will be default. Leave it blank or commented out to use internal settings.

Tavily

Get your API key here: https://tavily.com/#api

Environment Variables:

Traversaal

Description: LLM-enhanced search tool.

Get API key here: https://api.traversaal.ai/dashboard

Environment Variables:

WolframAlpha

See detailed instructions here: Wolfram Alpha

Environment Variables:

Zapier

Description: - You need a Zapier account. Get your API key from here: Zapier

• Create allowed actions - Follow step 3 in this getting start guide from Zapier

Note: Zapier is known to be finicky with certain actions. Writing email drafts is probably the best use of it.

Environment Variables:

OpenWeather

See detailed instructions here: OpenWeather

File Uploads

Runtime settings for uploads and server-side remote file fetches.

Streaming and Generation

Authentication and Permission Caching

Deployment Agent Plugins

Agent Plugins 1.0.0 can bundle deployment Skills and MCP servers.

Command hooks receive bounded lifecycle payloads over standard input, run with a minimal environment plus explicit allowedEnvVars, and can return event-appropriate decisions.

Code Interpreter

The Code Interpreter API provides a secure environment for executing code and managing files. See: Code Interpreter API

Search (Meilisearch)

Enables search in messages and conversations:

Note: If you're not using docker, it requires the installation of the free self-hosted Meilisearch or a paid remote plan

To disable anonymized telemetry analytics for MeiliSearch for absolute privacy, set to true:

For the API server to connect to the search server. Replace '0.0.0.0' with 'meilisearch' if serving MeiliSearch with docker-compose.

This master key must be at least 16 bytes, composed of valid UTF-8 characters. MeiliSearch will throw an error and refuse to launch if no master key is provided or if it is under 16 bytes. MeiliSearch will suggest a secure autogenerated master key. This is a ready-made secure key for docker-compose, you can replace it with your own.

To prevent IntelliAsk from attempting a database indexing sync with Meilisearch, you can set the following environment variable to true. This is useful in a node cluster, or multi-node setup, where only one instance should be responsible for indexing.

RAG API

Configure Retrieval-Augmented Generation for document indexing and context-aware responses. See: RAG API Configuration

Note: When using the default Docker setup, the .env file is shared between IntelliAsk and the RAG API. For complete configuration options, see the RAG API documentation.

Speech to Text & Text to Speech

Configure Speech-to-Text (STT) and Text-to-Speech (TTS) services. See: Speech Settings

Note: STT and TTS are primarily configured through the speech: section in intelliask.yaml. These environment variables are referenced in that configuration. See Speech Settings for full YAML configuration options.

Shared Links

Configure shared conversation links functionality.

ALLOW_SHARED_LINKS is the feature-wide switch. Role permissions now control who can create shared links, share them with authenticated users, or make them visible to everyone; see interface.sharedLinks. ALLOW_SHARED_LINKS_PUBLIC only controls whether publicly shared links can be viewed without authentication.

User System

This section contains the configuration for:

• Automated Moderation
• Balance/Token Usage
• Registration and Social Logins
• Email Password Reset

Moderation

The Automated Moderation System uses a scoring mechanism to track user violations. As users commit actions like excessive logins, registrations, or messaging, they accumulate violation scores. Upon reaching a set threshold, the user and their IP are temporarily banned. This system ensures platform security by monitoring and penalizing rapid or suspicious activities.

see: Automated Moderation

Basic Moderation Settings

Banning Settings

Login and registration rate limiting

Prevents brute force attacks and spam registrations by limiting login attempts and new account registrations.

Authentication token-submission rate limiting

These limit token validation (following a link from an email) independently from the rate limits on requesting the emails themselves, so a leaked token can't be brute-forced.

Score for each violation

Note: Non-browser access and Illegal model requests are almost always nefarious as it means a 3rd party is attempting to access the server through an automated script.

Message rate limiting (per user & IP)

Limiters

Note: You can utilize both limiters, but default is to limit by IP only.

IP Limiter:

User Limiter:

Import conversation rate limiting

Limits how often users can import conversations to prevent abuse.

Note: You can utilize both limiters, but default is to limit by IP only.

IP Limiter:

User Limiter:

Conversation forking rate limiting

Limits how often users can fork conversations to prevent abuse.

Note: You can utilize both limiters, but default is to limit by IP only.

IP Limiter:

User Limiter:

File upload rate limiting

Limits how often users can upload files to prevent abuse.

Note: These can also be configured via intelliask.yaml in the rateLimits.fileUploads section.

IP Limiter:

User Limiter:

TTS (Text-to-Speech) rate limiting

Limits how often users can use Text-to-Speech to prevent abuse.

Note: These can also be configured via intelliask.yaml in the rateLimits.tts section.

IP Limiter:

User Limiter:

STT (Speech-to-Text) rate limiting

Limits how often users can use Speech-to-Text to prevent abuse.

Note: These can also be configured via intelliask.yaml in the rateLimits.stt section.

IP Limiter:

User Limiter:

Balance

The following feature allows for the management of user balances within the system's endpoints. You have the option to add balances manually, or you may choose to implement a system that accumulates balances automatically for users. If a specific initial balance is defined in the configuration, tokens will be credited to the user's balance automatically when they register.

see: Token Usage

Managing Balances

• Run npm run add-balance to manually add balances.
  • You can also specify the email and token credit amount to add, e.g.: npm run add-balance example@example.com 1000
• Run npm run set-balance to manually set balances, similar to add-balance.
• Run npm run list-balances to list the balance of every user.

Note: 1000 credits = $0.001 (1 mill USD)

Registration and Login

see: Authentication System

• General Settings:

Quick Tip: Even with registration disabled, add users directly to the database using npm run create-user. Quick Tip: With registration disabled, you can delete a user with npm run delete-user email@domain.com.

• Session and Refresh Token Settings:

• JWT Settings:

You should use new secure values. The examples given are 32-byte keys (64 characters in hex). Use this replit to generate some quickly: JWT Keys

Social Logins

For more details: OAuth2-OIDC

Apple Authentication

For more information: Apple Authentication

Discord Authentication

For more information: Discord

Facebook Authentication

For more information: Facebook Authentication

GitHub Authentication

For more information: GitHub Authentication

Google Authentication

For more information: Google Authentication

OpenID Connect

For more information:

• Auth0
• AWS Cognito
• Azure Entra/AD
• Keycloak

OpenID Connect Token Reuse

IntelliAsk supports reusing access and refresh tokens issued by your OpenID Connect provider (like Azure Entra ID or Auth0) to manage user authentication state. When this feature is active, the refresh token passed to the user as a cookie is issued by your OpenID provider instead of IntelliAsk.

OPENID_REUSE_MAX_SESSION_AGE_MS accepts arithmetic expressions like SESSION_EXPIRY. Increase it toward the IdP access-token lifetime when your provider revokes the previous access token on refresh, so downstream consumers such as MCP servers can finish using a still-valid bearer token.

Microsoft Graph API / Entra ID Integration

When using Azure Entra ID (formerly Azure AD) as your OpenID provider, you can enable additional Microsoft Graph API features for enhanced people and group search capabilities within the permissions and sharing system.

SharePoint Integration

IntelliAsk supports direct integration with SharePoint Online and OneDrive for Business, allowing users to select and attach files from their SharePoint libraries directly within conversations. This enterprise feature leverages the existing Azure Entra ID authentication.

For detailed SharePoint configuration instructions, see: SharePoint Integration Guide

SAML

For more information:

• Auth0

LDAP/AD Authentication

For more information: LDAP/AD Authentication

Password Reset

Email is used for account verification and password reset. IntelliAsk supports both Mailgun API and traditional SMTP services. See: Email setup

Important Note: You must configure either Mailgun (recommended for servers that block SMTP) or SMTP for email to work.

Warning: Failing to set valid values for either Mailgun or SMTP will result in IntelliAsk using the unsecured password reset!

Mailgun Configuration (Recommended)

Mailgun is particularly useful for deployments on servers that block SMTP ports. When both MAILGUN_API_KEY and MAILGUN_DOMAIN are set, IntelliAsk will use Mailgun instead of SMTP.

SMTP Configuration

If Mailgun is not configured, IntelliAsk will fall back to SMTP settings.

Warning: If using EMAIL_SERVICE, do NOT set the extended connection parameters: HOST, PORT, ENCRYPTION, ENCRYPTION_HOSTNAME, ALLOW_SELFSIGNED.

See: nodemailer well-known-services

Firebase CDN

See: Firebase CDN Configuration

Amazon S3 and CloudFront

See: Amazon S3 Configuration and CloudFront with S3

Note: For Kubernetes deployments (e.g., on EKS), you can use IRSA (IAM Roles for Service Accounts) instead of providing explicit credentials. In that case, only AWS_REGION and AWS_BUCKET_NAME are required.

Azure Blob Storage CDN

See: Azure Blob Storage CDN Configuration

Note: Use either AZURE_STORAGE_CONNECTION_STRING (Option A) or AZURE_STORAGE_ACCOUNT_NAME with Managed Identity (Option B), not both.

UI

Help and FAQ Button

Behaviour:

Sets the Cache-Control headers for static files. These configurations only trigger when the NODE_ENV is set to production.

Properly setting cache headers is crucial for optimizing the performance and efficiency of your web application. By controlling how long browsers and CDNs store copies of your static files, you can significantly reduce server load, decrease page load times, and improve the overall user experience.

• Uncomment STATIC_CACHE_MAX_AGE to change the max-age for static files. By default this is set to 4 weeks.
• Uncomment STATIC_CACHE_S_MAX_AGE to change the s-maxage for static files. By default this is set to 1 week.
  • This is for the shared cache, which is used by CDNs and proxies.

App Title and Footer

Behaviour:

• Uncomment CUSTOM_FOOTER to add a custom footer.
• Uncomment and leave CUSTOM_FOOTER empty to remove the footer.
• You can now add one or more links in the CUSTOM_FOOTER value using the following format: [Anchor text](URL). Each link should be delineated with a pipe (|).

Markdown example: CUSTOM_FOOTER=[Link 1](http://example1.com) | [Link 2](http://example2.com)

Birthday Hat

Behaviour:

• The birthday hat icon will show automatically on March 1st (IntelliAsk's birthday).
• Set SHOW_BIRTHDAY_ICON to false to disable the birthday hat.
• Set SHOW_BIRTHDAY_ICON to true to enable the birthday hat all the time.

Analytics

Google Tag Manager

IntelliAsk supports Google Tag Manager for analytics. You will need a Google Tag Manager ID to enable it in IntelliAsk. Follow this guide to generate a Google Tag Manager ID and configure Google Analytics. Then set the ANALYTICS_GTM_ID environment variable to your Google Tag Manager ID.

Note: If ANALYTICS_GTM_ID is not set, Google Tag Manager will not be enabled. If it is set incorrectly, you will see failing requests to gtm.js

Conversation Import

Configure limits for conversation file imports to prevent memory issues.

MCP (Model Context Protocol)

Configure Model Context Protocol settings for enhanced server management and OAuth support.

MCP Server Configuration

Other

Redis

Redis provides significant performance improvements and enables horizontal scaling capabilities for IntelliAsk.

Note: Redis support is experimental, and you may encounter some problems when using it.

Important: If using Redis, you should flush the cache after changing any IntelliAsk settings.

For detailed configuration and examples, see: Redis Configuration Guide

Notes:

• When USE_REDIS=true, you must provide REDIS_URI or the application will throw an error.
• For Redis Cluster mode, provide multiple URIs: redis://node1:7001,redis://node2:7002,redis://node3:7003 (cluster mode is auto-detected).
• For single-endpoint managed Redis services that shard keys internally, keep USE_REDIS_CLUSTER=false and set REDIS_CLUSTER_SAFE_DELETE=true if cache clears fail with CROSSSLOT errors.
• Use rediss:// protocol for TLS connections and set REDIS_CA if your CA is not publicly trusted.
• REDIS_KEY_PREFIX_VAR and REDIS_KEY_PREFIX are mutually exclusive.
• AWS Elasticache with TLS: Elasticache may need to use an alternate dnsLookup for TLS connections. Set REDIS_USE_ALTERNATIVE_DNS_LOOKUP=true if using Elasticache with TLS. See ioredis documentation for more details.

Leader Election

Configure distributed leader election for multi-instance deployments with Redis. Leader election ensures only one instance performs certain operations like scheduled tasks.

Notes:

• Leader election requires Redis to be enabled (USE_REDIS=true).
• These settings are only relevant for multi-instance deployments.
• The leader lease must be renewed before expiration to maintain leadership.
• If lease renewal fails after max attempts, the instance will relinquish leadership.

Docker Override for Advanced Users

If you're deploying without the intelliask binary, you have two ways to customize the stack beyond editing config/.env:

Option 1: docker-compose.override.yml (auto-merged)

Create a docker-compose.override.yml file in the config/ directory (same location as the *.compose.yml files). Docker Compose automatically merges this file with the base compose files listed in COMPOSE_FILE.

Option 2: Custom compose file in COMPOSE_FILE

Create your own custom.compose.yml and explicitly add it to the COMPOSE_FILE list in config/.env:

# config/.env
COMPOSE_FILE=mongodb.compose.yml:...:custom.compose.yml

Both approaches let you:

• Override environment variables from config/.env
• Substitute bundled services with your own infrastructure (external S3, managed Redis, cloud PostgreSQL, external reverse proxy, etc.)
• Modify resource limits, ports, networks, or volumes
• Add custom sidecars or monitoring

Example: Using an external S3 bucket instead of the bundled Garage service

# config/docker-compose.override.yml  (auto-merged)
# OR config/custom.compose.yml  (add to COMPOSE_FILE manually)
services:
  codeapi-file-server:
    environment:
      - MINIO_ENDPOINT=s3.amazonaws.com
      - MINIO_USE_SSL=true
      # your credentials
      - MINIO_ACCESS_KEY=AKIAIOSFODNN7EXAMPLE
      - MINIO_SECRET_KEY=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
 
# Optionally disable the bundled Garage: `intelliask module disable garage`

Example: Using an external managed Redis

# config/docker-compose.override.yml
services:
  intelliask:
    environment:
      - USE_REDIS=true
      - REDIS_URI=redis://your-managed-redis.cloud:6379
 
  codeapi-api:
    environment:
      - REDIS_HOST=your-managed-redis.cloud
      - REDIS_PORT=6379
      - REDIS_PASSWORD=your-redis-password
 
# Remove codeapi.compose.yml's redis service by omitting redis-related volumes/networks,
# or exclude it from COMPOSE_FILE

For more info see:

• Our quick guide: Docker Override
• Official Docker documentation:
  • Understanding multiple compose files
  • Merge compose files
  • Specifying multiple compose files