ink-mainnet: delete 9 orphaned compose files, keep single reth variant #46
Reference in New Issue
Block a user
Delete Branch "issue-2053"
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?
Summary
Delete 9 colliding orphaned ink-mainnet compose files; keep single active
op/reth/ink-mainnet-op-reth-pruned-trace--kona.yml.Context: vibe-node config.yml removes geth from ink-mainnet catalog; these files are orphaned and collide with reth's routing (Traefik sees duplicate service names → error state). This PR cleans the asset side.
Files removed
op/geth/ink-mainnet-*.yml(3 profiles)op/erigon/ink-mainnet-*.yml(4 profiles)op/reth/ink-mainnet-op-reth-archive-*.yml(2 profiles)Kept:
op/reth/ink-mainnet-op-reth-pruned-trace--kona.yml(single active variant)Verification
Re-generated via vibe-node
./update.sh; no orphans recreated.Related