Skip to content
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

[New article]: Article for incoming Python support in .NET Aspire 8.1 #1048

Open
mitchdenny opened this issue Jun 6, 2024 · 3 comments
Open
Labels
doc-idea Indicates issues that are suggestions for new topics [org][type][category] ⌚ Not Triaged Not triaged

Comments

@mitchdenny
Copy link
Member

Proposed topic or title

Build .NET Aspire apps with Python

Location in table of contents.

Getting started (similar to Node.js, but suggestions welcome)

Reason for the article

In .NET Aspire 8.1 we are adding support to start Python executables as a first-class API. This is the PR:

dotnet/aspire#4142

Article abstract

Basically, the same as the Node.js application but for Python instead.

Relevant searches

python

@mitchdenny mitchdenny added the doc-idea Indicates issues that are suggestions for new topics [org][type][category] label Jun 6, 2024
@dotnet-bot dotnet-bot added the ⌚ Not Triaged Not triaged label Jun 6, 2024
@jamesmontemagno
Copy link
Member

I wonder if this doc and also the Node.js/npm doc should live under orchestration and be more pointed:

Add a Node.js app
Add a npm app
Add a Python app

Something like that?

@davidfowl
Copy link
Member

davidfowl commented Jun 14, 2024

Yes that would be ideal. Do we put it under frameworks? Other languages? What’s a good TOC?

@jamesmontemagno
Copy link
Member

jamesmontemagno commented Jun 14, 2024

It could be

  • App Host (Orchestration)
  • Resource Orchestration
    • .NET Projects
    • Containers
    • Executables
    • Node.js apps
    • npm apps
    • Python apps

I see this section: https://learn.microsoft.com/en-us/dotnet/aspire/fundamentals/app-host-overview?tabs=docker#built-in-resource-types and I think it could be it's own subsection based on what is in there. I'm not sold on "Resource Orchestration", but I think would be good.

Or it could just be:

  • Overview
  • Orchestrate .NET Projects
  • Orchestrate Containers
  • Orchestrate Executables
  • Orchestrate Node.js apps
  • Orchestrate npm apps
  • Orchestrate Python apps
  • Networking overview
  • Use external parameters
  • Persist data using volumes
  • Create custom resource type

I think it depends on how large this will grow, but I think maybe the flat style would work today....

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-idea Indicates issues that are suggestions for new topics [org][type][category] ⌚ Not Triaged Not triaged
Projects
None yet
Development

No branches or pull requests

4 participants