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.