Files
insights/livestream/docker-compose.integration.yml
zeekay 1b367e2b62 chore: rebase the tree onto upstream master
The tree was a debranded snapshot of upstream taken around 2026-02-20, and
upstream has moved about five months since. This replaces it with upstream
master, mechanically re-derived: bin/debrand does the rename, and the
pipeline and squashed migrations are restored from the shipped tree.

Not a merge. The previous import replaced the tree wholesale in a single
commit, so there is no shared content history to merge against. Reproducing
the rename on the new tree is what actually converges.

What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints,
compose files, LLM.md, and insights/migrations. The squashed initial
migration is load-bearing — the live database records it by name, so
upstream's ~918 individual migrations cannot come back.

Nine products are dropped as unreferenced. Twenty-one more that we do not run
are kept anyway because the core app still imports them; unpicking those is a
refactor and does not belong in a rebase.

This base does not build yet, and the reasons are not in the rename:
upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against
our 4.2, and the dependency manifests still name upstream packages that we
republish under our own names. Those are decisions, not renames.
2026-08-01 15:44:40 -07:00

83 lines
2.4 KiB
YAML

# 3-node Redis cluster for integration tests.
# All nodes use host networking so they can discover each other via 127.0.0.1.
#
# Usage:
# docker compose -f docker-compose.integration.yml up -d
# docker compose -f docker-compose.integration.yml logs redis-cluster-init --follow
# go test ./events/ -tags=integration -run TestRedisShardedPubSub -v -timeout 30s
# docker compose -f docker-compose.integration.yml down -v
services:
redis-node-1:
image: redis:7.2
network_mode: host
command: >
redis-server
--port 7001
--cluster-enabled yes
--cluster-config-file /data/nodes.conf
--cluster-node-timeout 5000
--appendonly yes
volumes:
- redis-data-1:/data
healthcheck:
test: ['CMD', 'redis-cli', '-p', '7001', 'ping']
interval: 1s
timeout: 3s
retries: 10
redis-node-2:
image: redis:7.2
network_mode: host
command: >
redis-server
--port 7002
--cluster-enabled yes
--cluster-config-file /data/nodes.conf
--cluster-node-timeout 5000
--appendonly yes
volumes:
- redis-data-2:/data
healthcheck:
test: ['CMD', 'redis-cli', '-p', '7002', 'ping']
interval: 1s
timeout: 3s
retries: 10
redis-node-3:
image: redis:7.2
network_mode: host
command: >
redis-server
--port 7003
--cluster-enabled yes
--cluster-config-file /data/nodes.conf
--cluster-node-timeout 5000
--appendonly yes
volumes:
- redis-data-3:/data
healthcheck:
test: ['CMD', 'redis-cli', '-p', '7003', 'ping']
interval: 1s
timeout: 3s
retries: 10
redis-cluster-init:
image: redis:7.2
network_mode: host
depends_on:
redis-node-1:
condition: service_healthy
redis-node-2:
condition: service_healthy
redis-node-3:
condition: service_healthy
command: >
redis-cli --cluster create
127.0.0.1:7001 127.0.0.1:7002 127.0.0.1:7003
--cluster-replicas 0 --cluster-yes
volumes:
redis-data-1:
redis-data-2:
redis-data-3: