// Work with the Docker Compose development environment. Use when: starting or stopping services, inspecting logs, opening a shell in a container, resetting the database, or understanding the service topology.
Configure or use the aiocache caching layer. Use when: adding cache reads/writes, configuring cache backends, working with TTLs, enabling/disabling caching, or understanding the NoOpCache fallback pattern.
Create or modify Celery tasks and periodic task configuration. Use when: adding new background tasks, setting up periodic/scheduled tasks, configuring Celery workers, or understanding the Celery app setup.
Create or modify FastAPI routes. Use when: adding new API endpoints, creating Pydantic request/response models, registering routers, designing REST APIs, or following route conventions for this project.
Create or modify Jinja2 templates. Use when: adding new HTML templates, configuring the Jinja2 environment, adding custom filters or globals, rendering templates outside FastAPI, or working with template inheritance.
Complete reference for all make targets in the project. Use when: looking up the right make command for any task — setup, testing, linting, formatting, database, packaging, or cleanup.
Add or modify application configuration settings. Use when: adding new environment variables, settings fields, understanding settings conventions, working with secrets, or configuring optional vs required settings.
| name | docker-compose |
| description | Work with the Docker Compose development environment. Use when: starting or stopping services, inspecting logs, opening a shell in a container, resetting the database, or understanding the service topology. |
context7: If the
mcp_context7tool is available, resolve and load the full Docker Compose documentation before modifyingcompose.yamlor using advanced CLI options:mcp_context7_resolve-library-id: "docker compose" mcp_context7_get-library-docs: /docker/compose
The development environment runs entirely through Docker Compose. All services are defined in compose.yaml.
{%- if cookiecutter.include_fastapi == "y" %}
| www | FastAPI application server |
{%- endif %}
{%- if cookiecutter.include_celery == "y" %}
| celery-scheduler | Celery Beat scheduler for periodic tasks |
| celery-node | Celery worker for background tasks |
{%- endif %}
{%- if cookiecutter.include_quasiqueue == "y" %}
| qq | QuasiQueue multiprocessing runner |
{%- endif %}
{%- if cookiecutter.include_sqlalchemy == "y" %}
| db | PostgreSQL database |
{%- endif %}
{%- if cookiecutter.include_celery == "y" or cookiecutter.include_aiocache == "y" %}
| redis | Redis cache / task broker |
{%- endif %}
# Start all services in the background
docker compose up -d
# Start with live rebuild on file changes
docker compose up --watch
# Stop all services (preserves volumes — data is retained)
docker compose down
# Stop all services AND remove volumes (full reset — destroys all data)
docker compose down --volumes --remove-orphans
# Restart all services without destroying containers or volumes
docker compose restart
# Restart a single service
docker compose restart www
# View recent logs from all services
docker compose logs
# Follow (tail) logs from all services in real-time
docker compose logs -f
# Follow logs from a specific service
docker compose logs -f www
# List running services and their status
docker compose ps
# Open a bash shell inside a running service
docker compose exec www bash
docker compose up -d
docker compose logs -f # watch until all services are healthy
docker compose down -v
docker compose up -d
docker compose logs --tail 50 www
# or follow real-time:
docker compose logs -f www
# Run in a new container (use for migrations, one-off scripts)
docker compose run --rm www bash
# Execute in an already-running container (use for debugging live services)
docker compose exec www bash
docker/ folder..env file is loaded automatically by Compose — make sure it's populated before starting.