Skip to content

Add dedicated documentation for DCP container networking tunnel#530

Open
Copilot wants to merge 5 commits intomainfrom
copilot/fix-issue-325
Open

Add dedicated documentation for DCP container networking tunnel#530
Copilot wants to merge 5 commits intomainfrom
copilot/fix-issue-325

Conversation

Copy link
Contributor

Copilot AI commented Mar 9, 2026

  • Create new documentation page fundamentals/container-networking.mdx
  • Add sidebar entry and cross-reference from networking-overview.mdx
  • Wrap tunnel steps in <Steps> component (review feedback)
  • Use OsAwareTabs with bash/PowerShell tabs for shell commands (review feedback)
  • Fix intro paragraph: broaden language beyond .NET, define DCP on first use with link to architecture content
  • Verify rendering with dev server — page and DCP link confirmed working
  • Run code review
  • Run CodeQL checker

Screenshots

Updated intro with DCP link and broader language:
Updated intro


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

…ixes #325)

Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix issue 325 using doc writer skill Add dedicated documentation for DCP container networking tunnel Mar 9, 2026
Copy link
Member

@IEvangelist IEvangelist left a comment

Choose a reason for hiding this comment

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

This PR looks good so far, but let's double check it for accuracy by using the .github/skills/doc-tester/SKILL.md skill. Please also consider all new comments and feedback/suggestions. @copilot

@IEvangelist
Copy link
Member

please also link to architecture content that contains details for DCP

Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Mar 12, 2026

This PR looks good so far, but let's double check it for accuracy by using the .github/skills/doc-tester/SKILL.md skill. Please also consider all new comments and feedback/suggestions. @copilot

Addressed both review comments in 0bb13c3:

  • Wrapped the tunnel steps in a <Steps> component
  • Replaced the bash-only block with OsAwareTabs showing both bash and PowerShell

Ran doc-tester validation: all 5 internal links return HTTP 200, Steps component renders numbered steps correctly, and both OS tabs (bash/PowerShell) display and switch as expected.

Copy link
Member

@IEvangelist IEvangelist left a comment

Choose a reason for hiding this comment

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

@copilot please see my comment

import { Aside, Steps } from '@astrojs/starlight/components';
import OsAwareTabs from '@components/OsAwareTabs.astro';

During local development, your Aspire app model often includes a mix of container resources and host-based services (such as .NET projects or executables). Container-to-container communication works naturally over the bridge network, but containers that need to reach services running on the host require a different approach. Aspire solves this with the **container tunnel**, a DCP capability that provides reliable, transparent container-to-host connectivity.
Copy link
Member

Choose a reason for hiding this comment

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

Instead of .NET projects or executables we should say something about C#, TypeScript, Python, as we support much more than just .NET.

Also, DCP is mentioned before it's defined in the following paragraph. We need to fix that and please also link to architecture content that contains details for DCP

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed in 3f8702e — broadened to "C#, Python, or TypeScript projects", moved the full "Developer Control Plane (DCP)" definition to the intro paragraph with a link to the architecture overview, and updated the next paragraph to use just "DCP" since it's already defined.

Updated intro

@IEvangelist IEvangelist marked this pull request as ready for review March 13, 2026 12:17
Copilot AI review requested due to automatic review settings March 13, 2026 12:17
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Adds a dedicated Fundamentals doc page explaining Aspire’s DCP container tunnel (container-to-host connectivity), and links it from existing networking documentation so readers can discover the feature and how to enable it.

Changes:

  • Added new fundamentals/container-networking.mdx page documenting the container tunnel, network identifiers, and enablement via ASPIRE_ENABLE_CONTAINER_TUNNEL.
  • Added a cross-reference from fundamentals/networking-overview.mdx to the new page.
  • Added a sidebar entry for “Container networking”.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File Description
src/frontend/src/content/docs/fundamentals/networking-overview.mdx Adds a pointer to the new container networking/tunnel documentation.
src/frontend/src/content/docs/fundamentals/container-networking.mdx New dedicated doc page describing the DCP container tunnel, network identifiers, and opt-in instructions.
src/frontend/config/sidebar/docs.topics.ts Adds the new Fundamentals sidebar entry (with translated labels).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[service discovery](/fundamentals/service-discovery/).
</Aside>

When containers need to reach host-based services, Aspire can use the **container tunnel** to provide reliable connectivity. For more information, see [Container networking](/fundamentals/container-networking/).
import { Aside, Steps } from '@astrojs/starlight/components';
import OsAwareTabs from '@components/OsAwareTabs.astro';

During local development, your Aspire app model often includes a mix of container resources and host-based services (such as .NET projects or executables). Container-to-container communication works naturally over the bridge network, but containers that need to reach services running on the host require a different approach. Aspire solves this with the **container tunnel**, a DCP capability that provides reliable, transparent container-to-host connectivity.
…e with architecture link

Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Mar 13, 2026

please also link to architecture content that contains details for DCP

Added in 3f8702e — the intro paragraph now links DCP to /architecture/overview/#developer-control-plane on first mention, and the See Also section already had that link as well.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants