Files
zeekay 2426e15c7d docs: drop "shim" framing — this is the tenant deployment
The repo is the tenant's bridge deployment surface (brand, network,
infra wiring, contracts manifest, k8s manifests). Calling it a "shim"
underplays it — composition over inheritance is the architecture, not
shimming. Updates README + Dockerfile comments to reflect.

Recommends `vX.Y.Z-{tenant}` image-tag convention (track upstream
version) over independent semver bumping. The Dockerfile `FROM` pin
IS the contract.

Repo rename target (separate GitHub-side op):
  hanzoai/bridge-shim → hanzoai/bridge
  zooai/bridge-shim   → zooai/bridge
  partner/bridge   (already correctly named — no change)

No code, contracts, k8s, or tenant.yaml changes.
2026-05-29 10:10:31 -07:00

19 lines
810 B
Docker

# Hanzo Bridge — tenant deployment image.
#
# Zero Go code at runtime — the binary IS the upstream OSS bridge.
# We overlay our tenant.yaml at /etc/bridge/tenant.yaml and pin
# --tenant-config at the entrypoint. White-label by composition; the
# upstream binary stays brand-neutral.
#
# Pin the upstream version explicitly. NEVER use :latest, :main, or
# floating tags in production manifests per global CLAUDE.md.
FROM ghcr.io/luxfi/bridge:v1.1.40
# Tenant configuration. ConfigMap mount in K8s overrides this for
# rotating prod credentials without an image rebuild; the bake-in is
# the default and dev fallback.
COPY tenant.yaml /etc/bridge/tenant.yaml
# Re-declare the entrypoint with the tenant-config flag pinned.
ENTRYPOINT ["/usr/local/bin/bridge", "--tenant-config", "/etc/bridge/tenant.yaml"]