feat: mirror installer binaries to DigitalOcean Spaces - #107
Merged
Conversation
Serve the one-liner and gander --upgrade from https://release.gander.md so GitHub rate limits no longer sit on the hot path. GitHub Releases remain the Homebrew source and the fallback if the mirror is down.
DigitalOcean Spaces names are lowercase; the bucket is gander, not gander-releases.
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.
Summary
Move the one-line installer and
gander --upgradeoff GitHub’s rate-limited download/API path ontohttps://release.gander.md(DigitalOcean Spaces). GitHub Releases stay the Homebrew source of truth and the fallback if the mirror is down.gander-*binaries, checksums,install.sh, andlatest.jsonafter publishing the GitHub Release.publish-spaces.ymlre-uploadsinstall.shonmainand supportsworkflow_dispatchto backfill an existing tag.install.shdownloads from the mirror first, then GitHub, then source.gander --upgradereadslatest.jsonfirst, then the GitHub Releases API.After merge
SPACES_ACCESS_KEYandSPACES_SECRET_KEYare set ongandermd/gander-cli.gander-releasesinnyc3, set Actions variablesSPACES_BUCKET/SPACES_REGION/SPACES_ENDPOINT.release.gander.mdat the Spaces CDN (custom subdomain + cert; a CNAME alone does not mint TLS).v*tag (or empty for latest) so existing binaries are on the mirror before the next cut.The cut-release skill does not upload; it already waits for the
releaseworkflow.scripts/release.shnow HEADshttps://release.gander.md/latest.jsonafter that wait.Test plan
go test ./...,go vet ./...,go build ./...shellcheck scripts/publish-spaces.sh scripts/release.shinstall.sh --dry-runprintshttps://release.gander.md/latest/gander-…workflow_dispatchbackfill, thencurl -fsSI https://release.gander.md/latest.jsonand a platform binarycurl -fsSL https://release.gander.md/install.sh | bash -s -- --dry-run