Setup Ansible playbook for Odoo 18 Docker server deployment

[matrixise]

Create a comprehensive Ansible playbook to automate the deployment of a new Odoo 18 server using Docker Compose.

Infrastructure Stack

• Traefik: 3.6 (reverse proxy + SSL)
• PostgreSQL: 18
• Odoo: 18 (custom image)
• fail2ban: To be verified for Docker compatibility

Tasks

• Create playbook structure
• Install Docker and Docker Compose
• Setup directory structure for Docker volumes
• Deploy docker-compose.yml with all services
• Configure Traefik reverse proxy with SSL
• Setup PostgreSQL database
• Deploy custom Odoo 18 image
• Investigate and configure fail2ban for Docker
• Configure firewall rules
• Setup backup strategy for volumes and database

[rkingkong]

This is doable, but “comprehensive playbook” is basically a full infra repo. If you’re open to a PR, the clean approach is to ship this as an Ansible role + env-specific inventories so it’s reusable (staging/prod), and keep secrets out of git via Ansible Vault.

A sane structure that works well for Odoo-on-Docker:

• roles/docker/ (install engine + compose plugin)
• roles/traefik/ (static config + dynamic routers + ACME storage perms)
• roles/postgres/ (volume dirs, init user/db, healthchecks)
• roles/odoo/ (custom image, env file, addons/filestore volumes, healthchecks)
• roles/firewall/ (ufw: allow 80/443/22, deny others)
• roles/backup/ (pg_dump + volume tar + retention + optional offsite)
• roles/fail2ban/ (optional; works via journald/nginx/traefik logs + DOCKER-USER chain)

Key things to decide up front (otherwise the playbook can’t be “correct”):

• OS target (Ubuntu 22.04/24.04?)
• Domain(s) / email for ACME
• Where Postgres lives (same compose stack vs external managed DB)
• Odoo image source (registry? build on host?) and addon paths
• Backup target (local disk only vs S3/rsync)

Re fail2ban: it can work with Docker, but you usually don’t “ban inside containers”; you ban at the host level using logs + DOCKER-USER iptables chain, or just rely on Cloud firewall + rate-limit middleware at Traefik.

If you share a minimal set of variables (domain, email, OS, image name, and whether DB is local), I can put together a baseline playbook/role layout + compose template + backup tasks that people can actually run.

[matrixise]

My apologies for the confusion - I posted my previous comment in the wrong repository.

I use this Hugo theme internally for my own site, and when I went to create an issue for my own repository, I mistakenly posted it here instead.

Sorry for polluting this repository with an unrelated comment.