Skip to content

Add Nitro configuration system guide#3321

Open
anegg0 wants to merge 1 commit into
nitro-cli-guidefrom
nitro-cli/configuration-system
Open

Add Nitro configuration system guide#3321
anegg0 wants to merge 1 commit into
nitro-cli-guidefrom
nitro-cli/configuration-system

Conversation

@anegg0

@anegg0 anegg0 commented May 27, 2026

Copy link
Copy Markdown
Contributor

Description

Adds a how-to page covering Nitro's configuration system at docs/run-arbitrum-node/nitro/configuration-system.mdx.

Topics covered:

  • Config sources and precedence — hardcoded defaults → S3 (--conf.s3.*) → config files (--conf.file) → config string (--conf.string) → CLI flags → environment variables.
  • Config file format — JSON, flat dot-separated keys, mapping to CLI flag names; uses koanf.
  • Environment variables--conf.env-prefix semantics, the strip → lowercase → __-_. transformation rules, and the full table of comma-split fields.
  • Mounting config in Docker-v mapping pattern + non-root user home directory.
  • --conf.dump — what gets emitted, which sensitive fields are scrubbed, and how to redirect to disk.
  • Hot reload--conf.reload-interval, the reload:"hot" tag in the Go source, and the list of top-level groups that support runtime reload.
  • S3 config loading--conf.s3.access-key, --conf.s3.secret-key, --conf.s3.region, --conf.s3.bucket, --conf.s3.object-key, plus a worked example combining S3 with a local override file.

All technical details verified against the Nitro source (cmd/nitro/config, cmd/genericconf, cmd/util/confighelpers).

Document type

  • Gentle introduction
  • Quickstart
  • How-to
  • Concept
  • FAQ
  • Troubleshooting
  • Reference
  • Third-party content
  • Not applicable

Checklist

  • I have read the CONTRIBUTE.md guidelines
  • My changes follow the style conventions outlined in CONTRIBUTE.md
  • I have used sentence-case for titles and headers
  • I have used descriptive link text (not "here" or "this")
  • I have separated procedural from conceptual content where appropriate
  • I have tested my changes locally with yarn start or yarn build
  • My code follows the existing code style and conventions
  • I have added/updated frontmatter for new documents
  • I have checked for broken links
  • I have verified that my changes don't break the build
  • Third-party docs only: Do you agree to the third-party content policy outlined within CONTRIBUTE.md?
    • Yes
    • Not applicable

Additional Notes

Split out from PR #3174 (Nitro CLI documentation guide) for focused SME review. Targets nitro-cli-guide to stack on top of the parent PR; will merge into master through it.

This PR will break the build, it's expected as it's a stacked PR. PR #3174 references /run-arbitrum-node/nitro/configuration-system from cli-flags-reference.mdx, sidebars.js, and the generator script. Those links resolve cleanly only once this PR merges back into nitro-cli-guide.

Linear: TW-693 (Nitro CLI reference — config system portion).

Covers config sources and precedence, JSON config file format,
environment variable mapping rules, Docker mounting, conf.dump,
hot reload, and S3 config loading. All technical details verified
against Nitro source code (cmd/nitro/config, genericconf, confighelpers).
@vercel

vercel Bot commented May 27, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
arbitrum-docs Ready Ready Preview May 27, 2026 12:34am

Request Review

anegg0 added a commit that referenced this pull request May 27, 2026
The configuration-system guide has been split into its own stacked
PR (#3321 — branch nitro-cli/configuration-system, base nitro-cli-guide)
for focused SME review by @Jason-W123. Removing the file here so PR
#3174 no longer duplicates that content; PR #3321 will re-add it when
it merges back into nitro-cli-guide.

Cross-references to /run-arbitrum-node/nitro/configuration-system from
cli-flags-reference.mdx, sidebars.js, and scripts/generate-cli-reference.ts
will be temporarily broken on this branch until #3321 merges.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
anegg0 added a commit that referenced this pull request May 27, 2026
…3178

This page is reviewed in the standalone stacked PR #3178 (branch
nitro-cli/node-tuning, base nitro-cli-guide) by @Jason-W123 and
@a-thomas-22. Removing it here so PR #3174 no longer duplicates the
content; PR #3178 re-adds it when it merges back into nitro-cli-guide.

Cross-references to /run-arbitrum-node/nitro/node-tuning-and-monitoring
from cli-flags-reference.mdx and scripts/generate-cli-reference.ts will
be temporarily broken on this branch until #3178 merges. Same pattern
as #3321 for configuration-system.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@anegg0 anegg0 added the nitro label May 27, 2026
anegg0 added a commit that referenced this pull request May 27, 2026
The Docker images and CLI binaries reference is being split into its
own stacked PR (branch nitro-cli/docker-and-cli-binaries, base
nitro-cli-guide) for focused SME review by @a-thomas-22. Removing the
file here so PR #3174 no longer carries it; the stacked PR re-adds it
when it merges back into nitro-cli-guide.

Cross-references from cli-flags-reference.mdx and the generator script
will be temporarily broken on this branch until the stacked PR merges.
Same pattern as #3321 (configuration-system) and #3322 (node-tuning).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

@Jason-W123 Jason-W123 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants