Promote develop to main: multichain explorer and chain-domain gateway routing - #13
Merged
Merged
Conversation
Three follow-ups from tonight's release and the incident after it. The artifact now packs production/linux, so a release carries its own unit files. Adopting socket activation needed the socket unit and the service drop-in on the host, and they had to be sent from a workstation checkout that happened to be on the right commit. That is the same class of mistake as building the artifact there, which this workflow exists to stop. Universe CI runs on pushes to develop again. Restricting it to main left direct pushes to develop with no CI at all between one pull request and the next, and develop is pushed to directly here. DEPLOYMENT.md gains the step that was missing and an edge section. The release tool at /usr/local/bin/universe-explorer-release is a copy, not a symlink, so it does not travel with a release; it was found running the previous release's gates against a new one while printing a normal-looking log. The edge section records the two path problems that have already caused incidents: favicon.ico and robots.txt being redirected by an inherited apache rewrite, and the tunnel's single-threaded sshd child landing in an unprotected per-session scope under memory pressure. It also records that operator access degrades before user traffic on that host, because a new SSH connection needs uncached IO that proportional weights cannot rescue while an established session does not. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add Dogecoin and Zcash explorer experience
Carry the unit files, restore develop CI, and write down the edge
The multichain frontend calls /api/v1/chains and the /api/v1/dogecoin, /api/v1/zcash, and /api/v1/bitcoin surfaces the overlay registers under the shared prefix. The gateway sent everything outside /api/v1/universe to the Bitcoin backend, which 404s the whole chain API while the site still loads. Name the overlay-owned chain prefixes explicitly, keep lookalike paths such as /api/v1/chainstats on the backend, and record the route table in DEPLOYMENT.md. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Route the chain-domain API to the overlay
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes the multichain explorer work to main for the production release:
The overlay side (backend-apis d1b34dbd) is already promoted and deployed on the indexer host.
🤖 Generated with Claude Code