Skip to content
Docs | Mimic

Configuration

Mimic is configured entirely through environment variables. There is no configuration file — the mocks directory is the configuration, and everything about the server itself is set via env vars.

Core variables

Section titled “Core variables”
Variable Default Description
PORT 8080 The TCP port Mimic listens on.
RUST_LOG info Log verbosity. One of trace, debug, info, warn, error.
MIMIC_MOCKS_DIR ./mocks (or /app/mocks in the Docker image) Where mock files are read from.
MIMIC_BIND_ADDRESS 0.0.0.0 Network interface to bind — restrict to 127.0.0.1 on a shared machine.

Mimic has grown a lot more configuration since those first two variables — CORS, proxying, admin authentication, request-log redaction, scenario tags, and more each have their own env var. See the full Environment Variables reference for every variable, grouped by feature.

Setting variables with Docker

Section titled “Setting variables with Docker”

Pass -e flags on docker run:

Terminal window
docker run -d \
  --name mimic \
  -p 9000:9000 \
  -e PORT=9000 \
  -e RUST_LOG=debug \
  -v $(pwd)/mocks:/app/mocks:ro \
  ragilhadi/mimic:latest

Setting variables with Docker Compose

Section titled “Setting variables with Docker Compose”

Use the environment block in your docker-compose.yml:

services:
  mimic:
    image: ragilhadi/mimic:latest
    ports:
      - "8080:8080"
    volumes:
      - ./mocks:/app/mocks:ro
    environment:
      PORT: 8080
      RUST_LOG: info

Or load them from a .env file in the same directory as your compose file:

.env
PORT=8080
RUST_LOG=info

Docker Compose picks up the .env file automatically.

Log levels

Section titled “Log levels”
Level Use when
error Production, when you only want to hear about real problems.
warn Production with a bit more context.
info The recommended default. Logs each request and significant events.
debug Local development. Shows mock matching decisions and reload events.
trace Deep debugging. Very verbose — use only when you’re hunting a specific bug.

Setting RUST_LOG=debug is the single most useful thing to do when something isn’t working as you expect — particularly with advanced matching, where you might want to see why a particular mock did or didn’t match.