Update from code changes: consolidate node-operator docs on base/base - #1833
Open
mintlify[bot] wants to merge 2 commits into
Open
Update from code changes: consolidate node-operator docs on base/base#1833mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Collaborator
🟡 Heimdall Review Status
|
roethke
self-requested a review
August 20, 2026 16:50
roethke
previously approved these changes
Aug 20, 2026
cb-heimdall
dismissed
roethke’s stale review
August 20, 2026 17:16
Approved review 4985275192 from roethke is now dismissed due to new commit. Re-request for approval.
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
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
Point the node-operator reference pages at the consolidated
base/baserepository and document the newNODE_TAGpinning workflow and rootdocker-compose.ymlknobs now that the public operator node image ships from this repo.Changes
run-a-base-node: switch clone target tobase/base, document pullingghcr.io/base/nodeby default vs.--build, add aNODE_TAGpinning subsection and a table of the new compose env vars (NODE_TAG,NETWORK_ENV,HOST_DATA_DIR,PROFILE), and note therust-servicesDockerfile target used by--build.snapshots: refresh the pruning-flags deep link tobase/base/.env.mainnet#L34, update the "cloned directory" wording, and show bothdocker compose upand--buildvariants for restart.troubleshooting: update repo links and directory references frombase/nodetobase/base.performance-tuning: update the "Base Node repository" link tobase/base.azul/node-upgrade: rewrite the "Both clients are available from…" note and migration steps to reflect that the operator node is now published frombase/baseinstead ofbase/node.Context
Follows base/base#4470, which cut over the public operator node from
base/nodetobase/base(rootdocker-compose.yml, new.env.mainnet/.env.sepoliatemplates, and theghcr.io/base/nodeimage built from therust-servicesDockerfile).