feat: add flower-docker extension for Celery monitoring

[emberb170d]

Flower Monitoring Extension for Celery

Adds Flower monitoring dashboard for Celery workers.

Problem

users often want Flower for local/dev monitoring.

Solution

Extension compatible with celery worker type: docker-compose service or dependency + docs. Keeps secrets in env examples only. L2 against .

What's included

• Flower monitoring dashboard via Docker Compose
• Environment variables loaded from files only (no hardcoded secrets)
• Comprehensive documentation and security guidelines
• Compatible with the celery-worker template (L2)

Files added

• • Extension overview
• • Docker Compose with flower service
• • Worker Dockerfile
• • Environment variable template
• • Usage guide
• • Extension index
• • Docs index bullet

Usage

uvx create-awesome-python-app my-worker \
  --template celery-worker \
  --addons celery-docker flower-docker \
  --yes

Then access the dashboard at http://localhost:5555.

Fixes #128

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 986762a1-8f5b-4394-87d3-cf108431e766

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[ulises-jeremias]

Flower monitoring is a welcome addition, and the extension layout itself looks right. But the branch mixes in unrelated changes: Spanish authoring-doc edits (overlapping #162), .editorconfig / .python-version files that already exist on main, and ARCHITECTURE.md edits. It's also cut from your fork's main, which makes follow-up updates awkward.

Please open a fresh feature branch off current upstream main containing only extensions/flower-docker/** (plus the registry entry) — then it should be a quick merge.

[ulises-jeremias]

Thanks @emberb170d for the Flower extension! A couple of items need work before this can be merged:

1. Missing incompatibleWith + registry entry (required per W3-5 / docs/AUTHORING.md):

• extensions/flower-docker and extensions/celery-docker both ship compose.yml + Dockerfile for the same celery-worker type and would overwrite each other.
• Please add a templates.json entry for flower-docker (slug flower-docker, type: ["celery-worker"]) with "incompatibleWith": ["celery-docker"], and add "incompatibleWith": ["flower-docker"] to the existing celery-docker entry. Validation is symmetric (scripts/ci/validate-registry.py enforces both sides list each other by slug).
• Document the colliding paths (compose.yml, Dockerfile, compose service collision on worker) in the PR description.

Current diff has no templates.json change and no incompatibleWith, so CI would fail registry validation once the extension is registered (expected behavior).

2. Branch hygiene — head is fork's main:

• This PR’s head is emberb170d/cpa-templates:main, which is your fork’s default branch. Please open future PRs from a feature branch (e.g. feat/flower-docker) so the fork’s main stays syncable with upstream and the PR can be updated without force-pushing main.
• For this PR, you can keep it open and push to the same branch, or create a new PR from a feature branch and we can close this one. No need to recreate immediately, but please use a feature branch next time.

3. Housekeeping:

• extensions/flower-docker/.dockerignore currently contains Markdown documentation rather than ignore patterns — please move that content to README.md and keep .dockerignore as actual ignore rules, or remove it if inherited from the template.
• template/compose.yml duplicates the redis+worker services from celery-docker and adds flower. If the extension depends on celery-docker being present, document the intended composition (--addons celery-docker flower-docker vs standalone). If they are mutually exclusive (incompatibleWith), the compose file should be standalone and the README should explain the choice.

Once templates.json + symmetric incompatibleWith are added, we can re-run CI (all L0/L1/L2 jobs are currently green on the unregistered state, but will need validation after registration). Adding needs-work for tracking.

[ulises-jeremias]

Superseded by #188 which adds flower-docker with proper incompatibleWith symmetric to celery-docker, valid .dockerignore, and full CI green. Thanks @emberb170d for the initial contribution! Closing #128 as well via #188.