fix: correct API_URL in Docker and typo in documentation

[sergeypanin1994]

• Replaced tcp:// with http:// in API_URL for proper Docker functionality
• Fixed typo: graphql → GraphQL in the E2E Testing section

Summary by CodeRabbit

• Documentation
  • Updated Docker instructions with corrected API URL protocol
  • Fixed capitalization of "GraphQL" in README text

[coderabbitai]

Walkthrough

The pull request introduces minor modifications to the README.md file, specifically updating the Docker container run command by changing the API_URL protocol from tcp to http. Additionally, a small terminology correction was made, capitalizing "GraphQL" in the documentation. These changes aim to improve the accuracy of the application's setup instructions and maintain consistent technical terminology.

Changes

File	Change Summary
README.md	- Updated Docker run command to use http protocol for API_URL - Corrected capitalization of "GraphQL" in test description

Suggested Reviewers

• dshiell

🐰 A Docker command's gentle tweak,
GraphQL's case, no more a mistake!
With protocol shifted just right,
Our README now shines so bright 🌟
A rabbit's documentation delight! 🔧

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 75996d9 and 5289044.

📒 Files selected for processing (1)

• README.md (2 hunks)

🔇 Additional comments (2)

README.md (2)

36-36: LGTM! Correct capitalization of GraphQL.

The capitalization has been updated to the proper form "GraphQL", which is the correct way to reference this query language.

---

21-21: LGTM! Protocol change looks correct.

The change from tcp:// to http:// for the API_URL is appropriate as the API is likely serving HTTP traffic. This aligns with common web API practices.

Let's verify this is the correct protocol by checking the API implementation:

✅ Verification successful

Protocol change from tcp:// to http:// is correct and verified

The change is verified to be correct because:

• The API_URL is used with Tendermint37Client which supports HTTP protocol
• HTTP is the standard protocol for Tendermint RPC endpoints in production environments
• The Docker setup correctly points to the host machine's HTTP endpoint

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check API implementation to confirm HTTP protocol usage
# Look for HTTP server/router setup in the codebase

# Search for HTTP server setup patterns
rg -l "http.Server|gin.Default|echo.New|mux.NewRouter"

# Search for TCP server patterns to ensure we're not missing anything
rg -l "net.Listen|tcp.Listen"

Length of output: 88

---

Script:

#!/bin/bash
# Broader search for API and server configurations
echo "=== Searching for API configurations ==="
fd -e js -e ts -e py -e go -e java -e rb | xargs rg -l "api|server|port"

echo -e "\n=== Checking Docker configurations ==="
fd "Dockerfile|docker-compose" --type f

echo -e "\n=== Looking for package configurations ==="
fd "package.json|requirements.txt|go.mod" --type f

Length of output: 3364

---

Script:

#!/bin/bash
# Check Dockerfile and API configurations
echo "=== Dockerfile contents ==="
cat Dockerfile

echo -e "\n=== API URL usage ==="
rg "API_URL|apiUrl" --type ts --type js

Length of output: 2484

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @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.