-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Development Containers (Hollistic Issue) #540
Comments
I'm curious what @timheuer thinks about this? |
I think this would be great, but one thing we need to feel good about first is the 'simple' devcontainer scenario (e.g., Codespaces). We're working on validating some of that and until we feel good about that before we can be affirmitive about the other scenarios. Codespaces is on our path to validate some of the aspects of port forwarding, etc. and ensuring works with VS Code. This is currently our tracking validation issue we are using: dotnet/aspire#1178 |
@IEvangelist when we get the go-ahead, I want this one |
All yours! |
@CamSoper are you able to work on this for the GA timeline, by next week? 😬 |
@IEvangelist Yep, top priority |
@timheuer I see dotnet/aspire#1178 is still open. Do you want me to write up a "how to" with the caveat that Codespaces has certain limitations? Or are we still holding off on documenting this? cc: @IEvangelist |
I think I'd wonder what it would look like with caveats -- I'm afraid the caveats might be long and confusing, thus feeling like the documentation is more of an explanation of incomplete work? I'd be open to reviewing what that might look like though... |
Describe the issue or suggestion
So, I noticed in the documentation and playground directory in the source code that there seems to be no mention or little mention of how to use aspire in dev container based workflow.
here is one that I have been using very frequently to spin up apps
while there are definitely better ways that something like this could be done, I do want to see if some mention and examples of dev containers could be added to the documentation.
New Section To Getting Started
For example, I think that a "dev container based" getting started guide would be really useful for those who are hesitant to download anything new or in preview to their laptop.
Adding Example Dev Containers Files To Project
There are many ways to work with Dotnet aspire and there's no one way to setup your dev container. For example, if your local workflow is just using aspire to spin up a .net api that is using a local sql server, then your dev container file is going to look very different to someone that is using dcp to orchestrate containers or integrate dapr. So I think a page with some example code block examples with example scenarios would be beneficial.
stateless .net apps only (just .net project resources)
having a node js based resource (adding node feature)
container resources in app host (with notes about dind, ipv6 args, implications of dind and how that working, not being able to have a dind workflow in rancher desktop but able to with docker desktop at the moment (seems unrelated, but it has some implications on how someone might use or decide on whether or not to use aspire and it's orchestration abilities)
Dapr Examples
Aspirate Example
an example that uses bicep files (so having the appropriate extensions and features would be noted)
The text was updated successfully, but these errors were encountered: