AiderDockerArchitecture

Docker Aider Conventions

Aider conventions for Docker and containerization: file naming, structure, and container patterns.

CONVENTIONS.md

- Name Dockerfiles by target: Dockerfile (production), Dockerfile.dev (development)
- Use docker-compose.yml for local dev; docker-compose.override.yml for personal overrides
- Add docker-compose.override.yml to .gitignore; commit only docker-compose.yml
- Name compose services consistently with the domain concept they serve
- Use .env.example for documenting required environment variables
- Tag production images with semantic versions, not just latest
- Store registry credentials in CI secrets; never in Dockerfiles or compose files
- Document the expected port mappings and volume mounts in README

How to use with Aider

Create a `CONVENTIONS.md` file in your project root. Aider reads this and respects your conventions when generating changes.

← All Aider rules All Docker rules →

#docker#aider#conventions#compose#coding-rules

Related Rules

Python Aider Conventions

AiderPython

Aider AI coding conventions for Python: CONVENTIONS.md patterns for automated refactoring and clean Python code.

Code Style

python · aiderCopy Ready

Next.js Aider Conventions

AiderNext.js

Aider conventions for Next.js: file naming, route organization, and App Router conventions.

Architecture

nextjs · aiderCopy Ready

SQL Aider Conventions

AiderSQL

Aider conventions for SQL and database migrations: naming, formatting, and migration patterns.

Database

sql · aiderCopy Ready

Security Aider Conventions

Aidersecurity

Aider conventions for security: secure coding patterns, vulnerability prevention, and security review checklist.

Security

security · aiderCopy Ready