Propose & Evaluate New Components For Aspire #1570
Replies: 11 comments 13 replies
-
cc @eerhardt |
Beta Was this translation helpful? Give feedback.
-
I would like to vote for Elastic search as well |
Beta Was this translation helpful? Give feedback.
-
I would vote for the local mail server (also with an example on how to use it with identity framework to send actual verification emails) |
Beta Was this translation helpful? Give feedback.
-
MQTT would be pretty useful for IOT projects :D |
Beta Was this translation helpful? Give feedback.
-
Are azure components like for example:
Also good candidates for new hosting components? |
Beta Was this translation helpful? Give feedback.
-
i vote for Elasticsearch😥 |
Beta Was this translation helpful? Give feedback.
-
Some AWS S3-compatible local service |
Beta Was this translation helpful? Give feedback.
-
I'm interested in Hashicorp Vault and started looking at this recently, but I'm not sure how to proceed. At this point it starts the container and I've built extension methods for the relevant volumes, but I'd like to run it in a production mode. That's where I'm stuck because I need some kind of hook to run after the container starts so I can initialize it, configure auth, etc., then persist the relevant information to the service discovery. |
Beta Was this translation helpful? Give feedback.
-
Hangfire with Hangfire.Redis.StackExchange would be a nice addition. |
Beta Was this translation helpful? Give feedback.
-
I wrote one for API Gateway KrakenD: |
Beta Was this translation helpful? Give feedback.
-
See the https://github.com/CommunityToolkit/Aspire/issues for these integration proposals! |
Beta Was this translation helpful? Give feedback.
-
I didn't feel like writing out a bunch of individual issues for each and every component, so I am just going to list some ideas out for some components that I think would be nice to haves for Aspire and am looking for feedback on potential ideas, push back on certain ones, which ones seem the easiest or realistic, or whatever is on your mind. Anyway here's what I've came up with.
I didn't feel like writing out a bunch of individual issues for each and every component, so I am just going to list some ideas out for some components that I think would be nice to haves for Aspire and am looking for feedback on potential ideas, push back on certain ones, which ones seem the easiest or realistic, or whatever is on your mind. Anyway here's what I've came up with.
Database
Storage
Secrets / Config
Messaging
Feature Flags
Emails
Data Aggregating
Api Gateways
Feature Flags
Emails
Search
Container Registries
CI/CD
Devtools
CLIs
Note
Some of these I think I would are more suited to be more additions / iterations to what's in place like search and emails.
Some of these I items aren't necessarily tied to a typical 'developer' workflow, but things that I do or have done locally and that I think would be nice to haves like cloud cli and or rancher. Just so that a non dev could easily spin up some dev ops containers and resources and see the relationship between the resources, the same way aspire is doing for .web, api, db, cache, and queue applications right now.
Beta Was this translation helpful? Give feedback.
All reactions