dotnet-env

Structure .NET project environments with appsettings, docker-compose, and .env files.

Updated Jun 20, 2025
One-click install
npx skills add https://github.com/emaginebr/BazzucaMedia --skill dotnet-env
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-env
Source: https://github.com/emaginebr/BazzucaMedia/tree/main/.claude/skills/dotnet-env
Command: npx skills add https://github.com/emaginebr/BazzucaMedia --skill dotnet-env

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill standardizes the setup of .NET project environments, ensuring consistent configuration, secure secret management, and streamlined deployment across Development, Docker, and Production stages.

Core Features & Use Cases

  • Environment Configuration: Manages appsettings.json files for Development, Docker, and Production.
  • Secret Management: Integrates .env files for Docker and .env.prod for Production, keeping secrets out of source control.
  • Docker Orchestration: Provides docker-compose.yml and docker-compose-prod.yml for local and production containerized deployments.
  • Deployment Pipeline: Generates a GitHub Actions workflow for automated SSH deployments to production.
  • Use Case: A new .NET project needs to be set up for local development using Docker, with a clear path to production deployment. This Skill will generate all necessary configuration files, Dockerfiles, and deployment scripts.

Quick Start

Use the dotnet-env skill to structure the development, docker, and production environments for a new .NET project named 'BazzucaMedia'.

Frequently Asked Questions about dotnet-env

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage .NET environment configurations for Docker and production?

Set up .NET Docker deployments by generating docker-compose.yml for local environments and docker-compose-prod.yml for production, utilizing .env files to inject secrets so they stay out of source control.

What is the best way to keep secrets out of source control in ASP.NET Core?

Keep secrets out of source control in ASP.NET Core by using .env files for Docker and .env.prod for production environments, ensuring secure secret handling while adhering to standard configuration conventions.

Does this approach generate a deployment pipeline for .NET production environments?

Yes, it generates a GitHub Actions workflow that automates SSH deployments to production, streamlining the pipeline from your structured Docker and production configurations directly to the server.

Can I use docker-compose for both local development and production with .NET?

Yes, you can use docker-compose for both by maintaining a standard docker-compose.yml for local development and a separate docker-compose-prod.yml for production containerized deployments with SSL configuration.

When do I need separate appsettings files for my .NET project environments?

You need separate appsettings files when structuring .NET project environments for Development, Docker, and Production, ensuring consistent configuration and secure secret management across each distinct deployment stage.