nodes.mdx: add Container image install path (#418)#19
Merged
Conversation
…t filenames don't (404 trap); tarball extracts to subdirectory (mv path was wrong)
…ry and From source) — closes part of #418
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
Closes part of `ligate-io/ligate-chain#418`. Adds a "Container image" subsection to `/nodes` Install between the existing "Pre-built binary" and "From source" sections.
Why
Each tagged chain release publishes `ghcr.io/ligate-io/ligate-chain:` (multi-arch: linux/amd64 + linux/arm64) via `.github/workflows/docker.yml`. v0.1.3 through v0.2.4 all published successfully. But this surface was never advertised on the operator docs: anyone wanting a containerised follower had to clone the chain repo and `docker build` locally (~10 min cold).
This PR closes the discoverability gap: the GHCR image is now a peer install path alongside the binary tarball and the source build.
What the new subsection covers
Sibling PR
The chain README PR (ligate-io/ligate-chain) adds the same pointer at the top of Quick start, so source-repo readers and docs-site readers both find the container option.
Test plan