R2D2-MERIDIAN/docker-compose.harness.yml
Joshua Belke 6c261c9117
Some checks failed
control plane / chart (push) Has been cancelled
control plane / test (push) Has been cancelled
control plane / browser-e2e (push) Has been cancelled
control plane / Build control plane image (linux/amd64) (push) Has been cancelled
control plane / Build control plane image (linux/arm64) (push) Has been cancelled
control plane / Publish signed control plane image (push) Has been cancelled
helm chart / lint + unittest + render matrix (push) Has been cancelled
helm chart / install on kind (gated) (push) Has been cancelled
helm chart / publish chart to GHCR (push) Has been cancelled
Meridian Harness / Build (aarch64-unknown-linux-musl) (push) Has been cancelled
Meridian Harness / Build (x86_64-unknown-linux-musl) (push) Has been cancelled
Meridian Harness / Publish rolling release (push) Has been cancelled
Meridian Harness / Publish tagged release (push) Has been cancelled
Harbor Meridian Orchestra / Python tests and lint (push) Has been cancelled
CI / Detect Changed Paths (push) Has been cancelled
CI / Dead Token Reference Guard (push) Has been cancelled
Docker image / Build (linux/amd64) (push) Has been cancelled
Docker image / Build (linux/arm64) (push) Has been cancelled
Docker image / Build public push gateway (linux/amd64) (push) Has been cancelled
Docker image / Build public push gateway (linux/arm64) (push) Has been cancelled
CI / Rust Lint (push) Has been cancelled
CI / Unit Tests (push) Has been cancelled
CI / Desktop Core (push) Has been cancelled
CI / Desktop Smoke E2E (1) (push) Has been cancelled
CI / Desktop Smoke E2E (2) (push) Has been cancelled
CI / Desktop Smoke E2E (3) (push) Has been cancelled
CI / Desktop Smoke E2E (4) (push) Has been cancelled
CI / Desktop (push) Has been cancelled
CI / Desktop E2E Relay (push) Has been cancelled
CI / Desktop E2E Integration (1/2) (push) Has been cancelled
CI / Desktop E2E Integration (2/2) (push) Has been cancelled
CI / Desktop E2E Integration (push) Has been cancelled
CI / Backend Integration (relay e2e) (push) Has been cancelled
CI / Relay E2E (push) Has been cancelled
CI / Web (push) Has been cancelled
CI / Mobile (push) Has been cancelled
CI / Security (push) Has been cancelled
CI / Server Cross-Compile (push) Has been cancelled
CI / Server Cross-Compile-1 (push) Has been cancelled
CI / Windows Rust (x86_64-pc-windows-msvc) (push) Has been cancelled
CI / Desktop Build (macOS) (push) Has been cancelled
Docker image / Merge release multi-arch manifest (push) Has been cancelled
Docker image / Merge debug multi-arch manifest (push) Has been cancelled
Docker image / Publish public push gateway image (push) Has been cancelled
fix(repo): point the repo slug at the real remote, not the guessed one
The rebrand baked in `github.com/r2d2/meridian`, chosen before the remote
existed. The canonical remote is `git.office.ilab.zone/RAID/R2D2-MERIDIAN` — a
different host, org, and repo name. ~150 references move: OCI image.source
labels, Helm chart sources, CI repository vars, Cargo `repository` metadata,
NIP-11 `software`, the docs and release scripts.

The container registry is unchanged and confirmed correct:
`registry.r2d2.office.ilab.zone`.

Three sets are deliberately left on github.com:

- **The link-preview fixtures.** `linkPreview.ts` gates on
  `normalizeHostname(parsed) !== "github.com"`, so the 33 URLs in
  `linkPreview.test.mjs` and two e2e specs are exercising a GitHub
  link-preview *feature*, not this repo's identity. Repointing them at a host
  the parser rejects would have turned passing tests red for no reason.
- **`raw.githubusercontent.com/aaif-goose/…`**, which is the third-party Goose
  installer.
- **Two API-shaped URLs** — the Releases API in `web/src/shared/lib/
  meridian-download.ts` and the raw-file URL in
  `managed_agents/discovery.rs`. Gitea/Forgejo spells these differently
  (`/api/v1/repos/…` with `limit=` and a different payload;
  `/raw/branch/<ref>/<path>`), so swapping only the host yields a URL that
  404s *while looking correct*. Neither endpoint could be probed, so both keep
  a `DANGLING` marker and are tracked in meridian-kir rather than guessed at.
  The download path already fails soft: a non-ok response falls back to
  `MERIDIAN_RELEASES_URL`, which now resolves to the Gitea releases page.

The discovery.rs marker is a one-line trailing comment because that file is
already over the size ratchet and may not grow — the explanation lives in the
bead, which is where it belongs. Line count is unchanged at 1858.

Verified: just ci exit 0.
Signed-off-by: Joshua Belke <joshua@innovationhub-act.org>
2026-08-05 13:00:51 -04:00

89 lines
2.7 KiB
YAML

# =============================================================================
# Isolated test-relay backing stack — GUI read-model overhaul harness (Dawn).
#
# A SEPARATE Compose project (`meridian-harness`) so the shared :3000 relay and the
# default `meridian-*` dev stack are never touched. No fixed container_names (they
# collide across projects) and alternate host ports. Mirrors Eva's evaperf-*
# isolation pattern.
#
# Bring up: docker compose -p meridian-harness -f docker-compose.harness.yml up -d
# Ports: postgres 5471 · dragonfly 6471 · minio 9471/9472
# Relay (run separately by scripts/start-isolated-test-relay.sh):
# main 3030 · health 8088 · metrics 9202
# =============================================================================
services:
postgres:
image: postgres:17-alpine
environment:
POSTGRES_USER: meridian
POSTGRES_PASSWORD: meridian_dev
POSTGRES_DB: meridian
PGDATA: /var/lib/postgresql/data
ports:
- "5471:5432"
volumes:
- harness-postgres-data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U meridian"]
interval: 5s
timeout: 5s
retries: 10
start_period: 10s
dragonfly:
image: docker.dragonflydb.io/dragonflydb/dragonfly:v1.39.0
ulimits:
memlock: -1 # Disable memlock limit
command:
# Dragonfly refuses to start unless maxmemory >= 256MiB per proactor thread.
# One thread keeps this isolated harness lean at 256mb; going to 2 threads would require 512mb.
- "--maxmemory=256mb"
- "--proactor_threads=1"
- "--dbfilename="
ports:
- "6471:6379"
networks:
default:
aliases:
- redis
healthcheck:
test: ["CMD", "/usr/local/bin/healthcheck.sh"]
interval: 5s
timeout: 3s
retries: 10
start_period: 5s
minio:
image: minio/minio:latest
command: server /data --console-address ":9001"
environment:
MINIO_ROOT_USER: meridian_dev
MINIO_ROOT_PASSWORD: meridian_dev_secret
ports:
- "9471:9000"
- "9472:9001"
volumes:
- harness-minio-data:/data
healthcheck:
test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
interval: 5s
timeout: 5s
retries: 10
start_period: 10s
minio-init:
image: minio/mc:latest
depends_on:
minio:
condition: service_healthy
entrypoint: >
/bin/sh -c "
mc alias set local http://minio:9000 meridian_dev meridian_dev_secret &&
mc mb --ignore-existing local/meridian-media &&
mc anonymous set none local/meridian-media
"
restart: "no"
volumes:
harness-postgres-data:
harness-minio-data: