How jsalvador-zsh/odoo-production-template works
Project type and purpose
• This is a full-stack production deployment template for Odoo 18, orchestrated via Docker Compose, with an “infra as code” layout and a complete monitoring suite (Prometheus, Grafana, AlertManager, exporters).
• Purpose: deploy Odoo ERP in production securely (Nginx + SSL), backed by PostgreSQL and Redis, and monitor everything.
File structure
• Top-level:
• .env.template, docker-compose.yml.template, docker-compose-monitoring.yml.template → environment and orchestration
• install.sh, setup-monitoring.sh → bootstrap scripts
• config/odoo.conf.template, nginx/nginx.conf.template → runtime configs
• monitoring/: subfolders for Prometheus, Grafana, AlertManager, exporters, scripts
• nginx/: reverse-proxy templates (SSL certs)
• No dedicated “frontend” directory – the Odoo container serves the UI.
README for insights
• Confirms the architecture: Nginx → Odoo → PostgreSQL + Redis
• Monitoring: Prometheus scrapes exporters, Grafana for dashboards, AlertManager for alerts
• Lists ports, services, dashboards, alert rules, environment variables.
Detail
• External dependencies: SSL certificates (nginx/ssl), environment variables (.env).
• Build scripts (install.sh) as a note or sub-system that provisions the entire stack.
• Don’t overthink – break the stack into as many discrete, logical services as you have in the file tree.