amorfo77/mailcow-dockerized

mirror of https://github.com/mailcow/mailcow-dockerized.git synced 2026-06-06 18:39:45 +00:00

Files

T

History

FreddleSpl0it 689d753264 [Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

..

cmd/mailcow-agent

[Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

[Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

Dockerfile

[Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

go.mod

[Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

go.sum

[Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

mailcow-agent-cli

[Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

README.md

[Agent] Replace dockerapi container with Redis-based control bus

2026-05-20 20:54:51 +02:00

README.md

mailcow-agent

Each mailcow service container (postfix, dovecot, …) runs mailcow-agent as ENTRYPOINT. It supervises the original service main process and exposes its control commands over a Redis Pub/Sub bus:

mailcow.control.<service> — request channel (Backend → Agent)
mailcow.reply.<request_id> — per-request reply channel
mailcow.events.<topic> — broadcast events
mailcow.nodes.<service> (ZSET) + mailcow.node.<service>.<node_id> (HASH) — heartbeat registry
mailcow.stats.<service>.<node_id> (HASH) — per-node cpu/memory stats

Service behaviour is selected via MAILCOW_AGENT_SERVICE=<service>. The main process command is configured via MAILCOW_AGENT_MAIN_CMD (string, executed via sh -c so existing entrypoints/supervisord commands keep working).