We need a section in the TOC that covers off the interaction between apps and containers running locally in Aspire and the Traefik proxies that DCP manages. We don't necessarily need to mention DCP or traefik as they are mostly implementation details from an Aspire perspective but we need to make it clear that when a service binding is added either implicitly (via launch profiles) or explicitly via a manually added service binding that Aspire will launch a Traefik proxy on that port, and the executable, project or container will be assigned another port.

In the case of Projects we automatically inject the appropriate ASPNETCORE_URLS environment variables. For containers we randomly assign the ports using the magic of Docker. For executables it requires some integration where we will optionally inject an environment variable with the port assigned for each service binding. This means that the executable will need to use that variable to figure out what port to bind to locally in order to avoid conflicts.

Networking isn't an inner loop only consideration. We probably need pages to cover various deployment scenarios and considerations and limitations of each target environment. There is not always a 1:1 mapping between what we do locally, and what gets deployed to the target environment.

Associated WorkItem - 198655