fix: add name to devdocs-network in docker-compose.yml

[wujunchuan]

Fix Docker Network Name for Consistent Inspection

Issue

When attempting to inspect the Docker network using docker network inspect devdocs-network, the command failed because the actual network name created by Docker Compose was devdocs_devdocs-network.

Root Cause

This discrepancy occurs because Docker Compose follows a standard naming convention for resources it creates: [project name]_[resource name]. In our original configuration, we defined the network as devdocs-network:

networks: devdocs-network: driver: bridge

However, Docker Compose automatically prefixed it with the project name, resulting in the actual network name being devdocs_devdocs-network.

Solution

This PR explicitly sets the network name using the name property in the network definition:

networks: devdocs-network: driver: bridge name: devdocs-network # Explicitly set the network name

With this change, the network will be created with exactly the name we expect, allowing docker network inspect devdocs-network to work as intended.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Summary by CodeRabbit

• Chores
  • Enhanced container network configuration by explicitly defining its naming, ensuring improved clarity and consistent behavior.

Walkthrough

The update introduces an explicit network name declaration in the docker-compose.yml file. The configuration for the devdocs-network, which continues to use the bridge driver, now includes a new line specifying name: devdocs-network. This change clarifies the network's identity without affecting its functionality.

Changes

File	Summary
docker/compose/docker-compose.yml	Added an explicit name: devdocs-network declaration to the devdocs-network configuration.

---

🪧 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 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 or @cyberagi-AI summarize to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @cyberagi-AI 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 20edbea and 6b7dad9.

📒 Files selected for processing (1)

• docker/compose/docker-compose.yml (1 hunks)

🧰 Additional context used

🪛 YAMLlint (1.35.1)

docker/compose/docker-compose.yml

[error] 80-80: no new line character at the end of file

(new-line-at-end-of-file)

🔇 Additional comments (1)

docker/compose/docker-compose.yml (1)

79-80: Explicit Network Name Configuration

The explicit definition of name: devdocs-network alongside the existing driver: bridge ensures that Docker Compose creates the network with the expected name. This directly addresses the naming discrepancy issue and allows the command docker network inspect devdocs-network to work as intended.

🧰 Tools

🪛 YAMLlint (1.35.1)

[error] 80-80: no new line character at the end of file

(new-line-at-end-of-file)