What problem does it solve? Standard Odoo deploys stop the server, run module upgrades on every tenant database, and restart, leaving users staring at 502/503 errors for minutes per push. This Skill replaces that with a verified blue/green cutover procedure on a single docker-compose box, so addon changes ship while the serving instance keeps answering requests. ## Core Features & Use Cases - Blue/green cutover state machine: Stage new code into a green service with its own addons directory, run -u migrations against live traffic via Odoo's registry signaling, then flip an nginx upstream file with a graceful reload. - Verified operational facts: Documents measured behavior of live -u upgrades, session/filestore survival across cutovers, asset bundle flushing, and pre-warming to avoid cold recompiles. - Failure semantics and escape hatch: Defines abort-safe rollback before the flip, loud failure after the flip, and refuses cutovers for schema-breaking migrations that need a classic maintenance window. - Use Case: A team deploying Odoo 19 CE addon updates to multiple tenant databases on one VPS uses this procedure to migrate only changed modules on the green color, pre-warm assets per tenant, flip nginx, and verify zero non-200 responses throughout. ## Quick Start Ask the agent to design a zero-downtime blue/green deploy pipeline for your docker-compose Odoo instance with multiple tenant databases, including the nginx upstream cutover and per-tenant module migration steps.
