broad-announce/deploy/nats/nats.conf

# nats.conf — NATS server config for the broad-announce dev/playground
# environment. Mirrors what was previously set via CLI flags, plus
# the JetStream limits that 2.10 does not expose as CLI flags.
#
# Mounted at /etc/nats/nats.conf by docker-compose. Loaded via -c flag.
#
# See M11_NATS_INVESTIGATION.md for why max_store is 10G and why
# we have stream-level MaxBytes/MaxAge in broker.go (not here).

# Client port (apps connect to nats:4222)
port: 4222

# HTTP monitoring port (Prometheus + ops access)
monitor_port: 8222

# Disable per-message tracing in dev (we use structured logging elsewhere)
# trace: true

# JetStream configuration.
# max_file_store: hard cap on disk-backed storage. With 11 GiB free
#                 on parres (post-prune 2026-06-16), 10 GiB gives a
#                 safety margin while still being well above the
#                 actual stream usage (~1.1 GiB after the broker.go
#                 fix in f450196).
# max_mem_store:  hard cap on memory-backed storage. Set to 1 GiB
#                 (parres has 16 GiB total RAM; ollama + prometheus +
#                 clickhouse + grafana use the rest). Streams we
#                 declare are file-backed, so this only matters for
#                 any future memory-backed streams.
# store_dir:      where JetStream writes its files. Mounted from the
#                 natsdata docker volume.
#
# Field names verified against nats-server 2.10 schema (the
# `max_store` / `max_mem` names from 2.11+ are not valid in 2.10).
jetstream {
  store_dir:     /data/jetstream
  max_file_store: 10737418240   # 10 GiB
  max_mem_store:  1073741824    # 1 GiB
}