Skip to content

feat(deploy): mainnet green slot for blue/green cutover (WEB-1443) - #150

Merged
v1rtl merged 1 commit into
mainnetfrom
feature/web-1443-add-blue-green-deployment-flow-for-v2-indexer
Nov 2, 2026
Merged

v1rtl merged 1 commit into
mainnetfrom
feature/web-1443-add-blue-green-deployment-flow-for-v2-indexer

Conversation

@v1rtl

@v1rtl v1rtl commented Nov 2, 2026

Copy link
Copy Markdown
Collaborator

Adds docker-compose.mainnet-green.yml, a second mainnet stack for blue/green deploys, mirroring how Sepolia runs prod and staging behind Traefik's custom-ensv2.yml.

  • Copy of docker-compose.mainnet.yml (blue) with every host- or dokploy-network-shared name suffixed -green: services, containers, network, volumes.
  • API on 5658, status port 3004. Points at its own database (zigens-mainnet-green-db via DATABASE_URL in Dokploy).
  • Runs with WEBHOOKS_ENABLED=false so webhooks are delivered once, by blue.

Routing lives in /etc/dokploy/traefik/dynamic/zigens-mainnet.yml on the Dokploy host: mainnet-graphql.ens.dev → zigens-mainnet-service, whose URL is ensv2-api-mainnet:5657 (blue) or ensv2-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

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.
@linear

linear Bot commented Nov 2, 2026 •

Copy link
Copy Markdown
WEB-1443 Add blue-green deployment flow for v2 indexer

Goal

Implement a blue-green deployment flow for the v2 indexer.

Scope

The 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 Criteria

The original acceptance criteria were not recorded. The owner should link the delivered scope and agreed success criteria; none are reconstructed as historical approvals here.

Verification

Completion 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 / Evidence

Linear 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 questions

This 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 prompt

No 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.

Review in Linear

@v1rtl
v1rtl merged commit 5361c95 into mainnet Nov 2, 2026
4 checks passed
@v1rtl
v1rtl deleted the feature/web-1443-add-blue-green-deployment-flow-for-v2-indexer branch November 2, 2026 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants