rays
549ae33f06
The browser suite's daemon took its environment from the shell running it, so a shell with OTEL_EXPORTER_OTLP_ENDPOINT set would have sent its fixture scans to production's Tempo, and one with IPX_DATABASE_URL set would have run the suite against production's database. Both are now blanked for it. Production's traces carry deployment.environment.name=production, which the dashboard filters on, so a daemon run by hand stays out as well. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
32 lines
1.1 KiB
YAML
32 lines
1.1 KiB
YAML
services:
|
|
ipx:
|
|
image: 192.168.1.130:5000/ipx:latest
|
|
container_name: iPX
|
|
restart: unless-stopped
|
|
environment:
|
|
PUID: "99"
|
|
PGID: "100"
|
|
TZ: "America/Toronto"
|
|
IPX_LOG: "ipx=info"
|
|
# Traces to Tempo, in the monitoring project; ipx sends none without it.
|
|
OTEL_EXPORTER_OTLP_ENDPOINT: "http://192.168.1.130:4318"
|
|
# What the dashboard filters on, so a daemon run by hand for testing stays out of it.
|
|
OTEL_RESOURCE_ATTRIBUTES: "deployment.environment.name=production"
|
|
# IPX_DATABASE_URL=postgres://... to use Postgres; without it, /data/state.db (SQLite).
|
|
env_file:
|
|
- ipx.env # relative: Arcane resolves it inside its own container
|
|
ports:
|
|
- "8099:8099" # web UI
|
|
- "6881:6881/tcp" # BitTorrent peers
|
|
- "6881:6881/udp" # DHT
|
|
volumes:
|
|
- /mnt/fast/appdata/ipx:/config # config.toml, and the web token
|
|
- /mnt/user/ipx/:/data # state.db
|
|
- /mnt/user/ipx/downloads:/downloads
|
|
healthcheck:
|
|
test: ["CMD", "ipx", "status"]
|
|
interval: 30s
|
|
timeout: 5s
|
|
retries: 3
|
|
start_period: 10s
|