docs: use 127.0.0.1 for localhost on consensus node page

[jcstein]

The config has 127.0.0.1, so this PR updates documentation to use the same so it is clear not to change it to localhost.

Overview

Summary by CodeRabbit

• Documentation
  • Updated the guide to use explicit IP addresses for local port configurations, replacing ambiguous references with clear, standardized values for improved clarity in setup instructions.

[coderabbitai]

Walkthrough

This pull request updates the Celestia app guide by changing the IP addresses for ports 2121 and 26657 from localhost to the explicit 127.0.0.1. The change is made to ensure clarity in the binding address used by the app nodes. There are no modifications to the exported or public entity declarations.

Changes

File	Change Summary
how-to-guides/celestia-app.md	Updated IP addresses for ports 2121 and 26657 from localhost to 127.0.0.1 in Celestia app nodes.

Suggested reviewers

• lukecd

Poem

I'm a bunny with a spring in my step,
Hop, hop—IP fixes I adeptly prep.
From "localhost" I hopped away,
To a clear "127.0.0.1" in bright display.
With twitching whiskers, I celebrate this day,
Skipping lightly over changes on my way!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[Copilot]

Pull Request Overview

This PR updates the documentation to specify the use of "127.0.0.1" instead of "localhost" in the Celestia app configuration for consistency with the config file.

• Updated the P2P port address from "localhost" to "127.0.0.1".
• Updated the RPC port address from "localhost" to "127.0.0.1".

[github-actions]

PR Preview Action v1.6.0
🚀 View preview at https://celestiaorg.github.io/docs-preview/pr-1956/
Built to branch main at 2025-03-28 22:37 UTC. Preview will be ready when the GitHub Pages deployment is complete.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

how-to-guides/celestia-app.md (1)

132-132: Align descriptive text with explicit IP address for port 26657.

Although the IP address has been updated to 127.0.0.1, the description still refers to "localhost." For consistency and clarity, consider updating the descriptive text (e.g., "false (only open to 127.0.0.1)") so that it fully reflects the explicit address used.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 5fdba14 and 7048841.

📒 Files selected for processing (1)

• how-to-guides/celestia-app.md (1 hunks)

🔇 Additional comments (1)

how-to-guides/celestia-app.md (1)

130-130: Clarify explicit IP usage for port 2121.

The IP address for port 2121 has been changed from localhost to 127.0.0.1, which improves clarity by explicitly showing the intended binding address. This update aligns the documentation with the configuration settings.