docs: restructure install paths around user intent (WIP) - #599
Draft
viniciusdc wants to merge 1 commit into
Draft
Conversation
Reorganize the README install section by how people actually install nic: pixi (recommended, pending the prefix.dev channel), Homebrew, release archives with signature verification, and from-source for contributors. Scope the Go 1.26+ prerequisite to source builds only. Draft: the pixi path depends on #579, the install-script and Homebrew sections overlap #539, and the docs-site mirror is still pending. Part of #563.
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
2 participants
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.
Part of #563.
What
Restructures the README install section around user intent instead of leading with "build from source":
pixi addthat pins inpixi.lock, pluspixi global install.Go 1.26+prerequisite scoped to it (end users no longer need a Go toolchain).Draft / incomplete - do not merge yet
Opening as a draft on purpose. Outstanding:
nicis not on the prefix.devgithub-releaseschannel yet, so thepixi addcommands do not resolve until that lands. Verified today: the channel works (k9sresolves) butnebari-infrastructure-coreis not on it.main, which does not have them yet, so the two need reconciling at merge - whichever lands first, the other rebases onto it.Holding here until #579 and #539 settle so this documents reality rather than intent.