Felix FaerberandClaude Opus 4.7
7fcd9df9d3
Bind two ready-to-use dashboards at grafana.t4t-gateway.com: - Logs — All services: per-service log volume timeseries + live tail, with a service selector and a free-text search box. - Hosted-gateway API — errors & PSS inbox: error rate, ack/deliver counters, and a live tail filtered to PSS inbox traffic so the webhook fallback is observable. Datasources + dashboard providers are mounted via Docker configs from hostinger/grafana/ so they survive grafana container restarts and live in git rather than the Grafana UI. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
DevOps
This repo manages the two environments for the Token4Token hosted gateway:
local/— docker-compose files for running development and testing environments locally. Tests run inside Docker, no host-side Bun needed.hostinger/— Docker Swarm stack files for the remote production cluster on Hostinger.
The layout mirrors cipherdolls/devops.
Local development
cd local
make up # bring the dev stack up (postgres, redis, bee, anvil, api, worker)
make logs # tail
make down # clean shutdown
The dev compose mounts ../../hosted-gateway/src so file changes hot-reload
inside the container (bun run --watch).
Local testing
Every E2E spec runs inside Docker against a fresh stack (anvil fork of Gnosis, deployed contracts, a t4t-provider container against a stub Ollama).
cd local
make test SPEC=accounts # run one spec
make test-all # run every spec sequentially
make test brings up postgres + redis + anvil + bee + t4t-provider + hosted
api + worker, then runs the bun test container against them. After the run
it tears everything down (-v --remove-orphans).
Hostinger / production
Stack files in hostinger/ are applied via docker stack deploy from the CI
pipeline. Not relevant for local development.