Repository navigation
Conversation
A second mainnet stack next to docker-compose.mainnet.yml with -green names, port 5658 and its own database. Traefik's dynamic config points mainnet-graphql.ens.dev at one slot or the other, the same way Sepolia's custom-ensv2.yml does.
WEB-1443 Add blue-green deployment flow for v2 indexer
GoalImplement a blue-green deployment flow for the v2 indexer. ScopeThe original ticket names the blue-green deployment outcome but does not identify the repository, environments, cutover mechanism or delivered configuration. Linear records this issue as Done on 28 October 2026. Preserve that status; this refinement requests durable completion context rather than asserting new implementation requirements. Acceptance CriteriaThe original acceptance criteria were not recorded. The owner should link the delivered scope and agreed success criteria; none are reconstructed as historical approvals here. VerificationCompletion evidence is not present in the issue or comments. Link the actual deployment/cutover checks, recovery or rollback validation, indexer continuity checks and independent review performed. These are evidence requests, not claims of completed or failed verification. Context / EvidenceLinear state history records In Progress from 29 September to 28 October 2026, followed by Done. The previous execution-gap note still said In Progress; that stale statement has been removed. Open questionsThis issue is now Done. Please add the implementation PR/configuration, deployed environment and evidence of cutover, recovery/rollback and indexer continuity checks, and identify the independent reviewer. The old description incorrectly still said In Progress; missing evidence is not a claim that those checks failed. The repository, historical scope, estimate and Release Type/Change Risk decisions are not documented in this issue. Suggested AI coding promptNo new implementation is requested by this refinement. Locate the delivered indexer deployment change and document its actual scope and verification evidence. Repository and configuration paths remain unverified. |
Adds
docker-compose.mainnet-green.yml, a second mainnet stack for blue/green deploys, mirroring how Sepolia runs prod and staging behind Traefik'scustom-ensv2.yml.docker-compose.mainnet.yml(blue) with every host- ordokploy-network-shared name suffixed-green: services, containers, network, volumes.zigens-mainnet-green-dbviaDATABASE_URLin Dokploy).WEBHOOKS_ENABLED=falseso webhooks are delivered once, by blue.Routing lives in
/etc/dokploy/traefik/dynamic/zigens-mainnet.ymlon the Dokploy host:mainnet-graphql.ens.dev→zigens-mainnet-service, whose URL isensv2-api-mainnet:5657(blue) orensv2-api-mainnet-green:5658(green). A cutover edits that URL; Traefik reloads it without restarting anything.Merging redeploys blue (auto-deploy on
mainnet). That redeploy also drops the old Dokploy-domain labels, so the Traefik file router is the only one for the host.Refs WEB-1443