Aspire Configuration

This keeps your Aspire apps production-ready by forcing everything through explicit environment variables instead of leaning on service discovery magic. You wire up resources like Postgres or MinIO in the AppHost using WithEnvironment calls that map to config keys, then your actual app code just reads IOptions or Configuration like any normal .NET service. No Aspire client packages pollute your application projects. The payoff is that your dev setup looks exactly like what you'll deploy, every setting can be represented as an env var in Kubernetes or wherever, and you can spin up integration tests without mysterious orchestration leaking into your domain logic. It's opinionated but honest about keeping infrastructure concerns in one place.

Install to Claude Code

npx -y skills add aaronontheweb/dotnet-skills --skill aspire-configuration --agent claude-code