StakeSquid/ethereum-rpc-docker
1
0
Fork 0
Code Issues Pull Requests 3 Packages Projects Releases Wiki Activity

ink-mainnet: remove stale op-geth orphan compose files #44

Closed
claude wants to merge 1 commits from issue-1940 into main
pull from: issue-1940
merge into: StakeSquid:main
Conversation 1 Commits 1 Files Changed 4 -808
claude commented 2026-07-28 07:16:01 +00:00
Collaborator
Copy Link

Summary

Remove four stale op/geth/ink-mainnet-op-geth-*.yml orphan compose files that are causing Traefik /ink-mainnet routing conflicts and marking the node ERROR despite healthy kona+op-reth chain sync.

The vibe-node source already dropped ink-mainnet op-geth (after Karst→op-reth migration), but ./update.sh never prunes orphan rpc files. These four files persisted in COMPOSE_FILE, and both geth and reth compose files claiming the same Traefik path caused 404 responses → dshackle unhealthy mark.

Verification

  • Branch: issue-1940 @ 53de81c09dea
  • ./update.sh verify: clean (no errors, no geth orphans recreated, op-reth+kona present)
  • No unintended regeneration; gitlink left at main HEAD

Fix

After merge, deploy to rpc-de-14 (test host) → verify dshackle marks node healthy → close issue.

(vibe-node issue #1940)

## Summary Remove four stale `op/geth/ink-mainnet-op-geth-*.yml` orphan compose files that are causing Traefik `/ink-mainnet` routing conflicts and marking the node ERROR despite healthy kona+op-reth chain sync. The vibe-node source already dropped ink-mainnet op-geth (after Karst→op-reth migration), but `./update.sh` never prunes orphan rpc files. These four files persisted in `COMPOSE_FILE`, and both geth and reth compose files claiming the same Traefik path caused 404 responses → dshackle unhealthy mark. ## Verification - Branch: `issue-1940` @ `53de81c09dea` - `./update.sh verify`: clean (no errors, no geth orphans recreated, op-reth+kona present) - No unintended regeneration; gitlink left at main HEAD ## Fix After merge, deploy to rpc-de-14 (test host) → verify dshackle marks node healthy → close issue. (vibe-node issue #1940)
claude added 1 commit 2026-07-28 07:16:01 +00:00
ink-mainnet: remove orphaned op-geth compose files 53de81c09d 
Source already dropped ink-mainnet op-geth from config.yml, but
update.sh never prunes orphans — stale op/geth/ink-mainnet-op-geth-*.yml
files stayed in COMPOSE_FILE and fought op-reth for Traefik /ink-mainnet
(404). Delete the four orphans so only op-reth remains for that path.
sebastian commented 2026-07-29 02:43:19 +00:00
Owner
Copy Link

@claude is this still necessary?

@claude is this still necessary?
sebastian closed this pull request 2026-07-31 03:26:03 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claude cursor rob sebastian
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#44
Delete Branch "issue-1940"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?