Template
akritikos
eea4ce7a0e
Refines conventions for ASP.NET API endpoints, C# documentation, Docker build arguments, MSBuild package management, and testing method naming and structure. These changes aim to enhance clarity and enforce best practices across the codebase.
1.7 KiB
1.7 KiB
description, applyTo
| description | applyTo |
|---|---|
| Use when editing Dockerfile, compose files, or Docker-related configuration. Covers guardrails for the multi-stage build and runtime image selection. | docker/**,compose*.yaml |
Docker Conventions
docker/Dockerfile is a multi-stage pipeline — stage names and purposes are visible in the file itself.
Guardrails
- Build context is always the repo root, not
docker/. COPY --linkis used intentionally for layer cache — do not replace with plainCOPY.- Cache mounts (
--mount=type=cache,target=/root/.nuget/packages) must stay on restore, build, test, and publish steps. - Stage dependency chain must be preserved (e.g.,
build→restore,test→build,publish→test). - New stages should follow the existing pattern:
FROM <parent> AS <name>.
Build Args
RUNTIME_BASE:web(ASP.NET),app(console), orself-contained. If a use case does not matchweb,app, orself-contained, do not invent a newRUNTIME_BASEvalue — flag this to the user and ask which existing value best fits their scenario.CONFIGURATION:Release(default) orDebugPUBLISHED_PROJECT: Project name to publish (without path or extension)DATABASE_PROJECT: EF Core project for migration bundlesDBCONTEXT: Optional DbContext name for migrations. If omitted, the migration bundle step must not pass--context; EF Core auto-discovers the single DbContext inDATABASE_PROJECT.
Image Selection
| Use Case | RUNTIME_BASE |
Base Image |
|---|---|---|
| ASP.NET web apps | web |
aspnet:*-alpine-composite-extra |
| Console / worker | app |
runtime:*-alpine-extra |
| Self-contained | self-contained |
runtime-deps:*-alpine-extra |