forked from CopilotKit/CopilotKit
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdocker-compose.record.yml
More file actions
51 lines (51 loc) · 2.17 KB
/
Copy pathdocker-compose.record.yml
File metadata and controls
51 lines (51 loc) · 2.17 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
# Record-mode override for aimock. Layer on top of docker-compose.local.yml
# to flip aimock from replay-only into record+replay against real OpenAI /
# Anthropic. Recorded fixtures land on the host at
# `showcase/aimock/d5-recorded/recorded/` (one file per LLM call).
#
# Usage:
# docker compose -f showcase/docker-compose.local.yml \
# -f showcase/docker-compose.record.yml \
# --profile infra up -d aimock langgraph-python
#
# When recording is finished, switch back to base compose (no override) and
# load any new fixtures from `d5-recorded/` via an additional `--fixtures`
# entry on the aimock command.
#
# Authorization headers from the integration container are forwarded to the
# real provider — no key needs to be set on aimock itself.
services:
aimock:
volumes:
# RW mount so aimock can write `recorded/<provider>-<ts>-<uuid>.json`
# under this dir. Existing baseline fixtures stay :ro from the base
# compose; only the recording dir is writable.
- ./aimock/d5-recorded:/showcase-fixtures/d5-recorded:rw
# Read-only mounts for depth-organized fixture directories so aimock
# can short-circuit on already-matched prompts from shared/d4/d6.
- ./aimock/shared:/showcase-fixtures/shared:ro
- ./aimock/d4:/showcase-fixtures/d4:ro
- ./aimock/d6:/showcase-fixtures/d6:ro
command: [
"--port",
"4010",
"--host",
"0.0.0.0",
"--record",
"--provider-openai",
"https://api.openai.com",
"--provider-anthropic",
"https://api.anthropic.com",
# Load ONLY the recorded dir as the fixture source. The baseline
# depth-organized fixtures (shared/d4/d6) are intentionally NOT
# loaded — if they were, aimock would short-circuit on
# already-matched prompts and never proxy them to the real
# provider, defeating the recording pass.
#
# First --fixtures path is the recording destination base; aimock
# writes to `<base>/recorded/<provider>-<ts>-<uuid>.json`.
"--fixtures",
"/showcase-fixtures/d5-recorded",
"--fixtures",
"/showcase-fixtures/shared",
]