Add dedicated documentation for DCP container networking tunnel#530
Add dedicated documentation for DCP container networking tunnel#530
Conversation
…ixes #325) Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
IEvangelist
left a comment
There was a problem hiding this comment.
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
|
please also link to architecture content that contains details for DCP |
Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Addressed both review comments in 0bb13c3:
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. |
IEvangelist
left a comment
There was a problem hiding this comment.
@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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.mdxpage documenting the container tunnel, network identifiers, and enablement viaASPIRE_ENABLE_CONTAINER_TUNNEL. - Added a cross-reference from
fundamentals/networking-overview.mdxto 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. |
src/frontend/src/content/docs/fundamentals/container-networking.mdx
Outdated
Show resolved
Hide resolved
…e with architecture link Co-authored-by: IEvangelist <7679720+IEvangelist@users.noreply.github.com>
Added in 3f8702e — the intro paragraph now links DCP to |
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

fundamentals/container-networking.mdx<Steps>component (review feedback)OsAwareTabswith bash/PowerShell tabs for shell commands (review feedback)Screenshots
Updated intro with DCP link and broader language:

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