Closed mitchdenny closed 3 weeks ago
Couple of gotchas. For forwarded ports, it can take some time for Codespaces to generate the TLS cert for the endpoint. You just have to be patient. Part of explicitly forwarding the ports in the .devcontainer.json
file is to make sure that its mapped as HTTPS or HTTP as appropriate.
/azp run
@mitchdenny one place where we don't detect the codespace and print the right url is here:
We should change this too.
Yeah I was looking at this I made some tweaks last night as an experiment. I can put up a PR.
Also it seems like only certain playground examples work?
Description
This is an initial PR to enable devcontainer support in the repo. The goal is to enable the various remote development scenarios (Codespaces, SSH, etc) so that we can test them. This is important because we've added logic to the apphost that can do things like detect it is running in Codespaces and using the Aspire repo under Codespaces is a good way of casually validating everything is working.
Outstanding issues
Fixes # (issue)
Checklist
<remarks />
and<code />
elements on your triple slash comments?Does the change require an update in our Aspire docs?
Microsoft Reviewers: Open in CodeFlow