Web-app-odoo Role¶
Description: Open-source ERP suite for CRM, sales, accounting, inventory, HR, and website management
Variables¶
author: Evangelos Tsakoudis
description: Open-source ERP suite for CRM, sales, accounting, inventory, HR, and website management
license: Infinito.Nexus Community License (Non-Commercial)
company: Kevin Veen-Birkenbach https://www.veen.world
galaxy_tags: [‘odoo’, ‘erp’, ‘crm’, ‘business’, ‘finance’, ‘inventory’, ‘sales’, ‘hr’, ‘website’, ‘marketing’]
issue_tracker_url: https://s.infinito.nexus/issues
min_ansible_version: 2.9
platforms: [{‘name’: ‘ArchLinux’, ‘versions’: [‘all’]}, {‘name’: ‘Debian’, ‘versions’: [‘all’]}, {‘name’: ‘EL’, ‘versions’: [‘all’]}, {‘name’: ‘Fedora’, ‘versions’: [‘all’]}, {‘name’: ‘Ubuntu’, ‘versions’: [‘all’]}]
README¶
Odoo ERP¶
Description¶
Deploy and manage Odoo, a comprehensive open-source enterprise resource planning (ERP) solution within the Infinito.Nexus ecosystem. Odoo provides a fully integrated suite of business applications including CRM, sales, inventory, accounting, HR, marketing, and website tools.
Overview¶
This role automates the deployment of Odoo in a containerized Docker environment with PostgreSQL database integration, OIDC/LDAP authentication support, and full Infinito.Nexus stack integration including reverse proxy, CSP configuration, and centralized identity management.
Cosmos¶
The diagram places Odoo ERP in the Infinito.Nexus cosmos: the components it deploys (capabilities), the central services it consumes (dependencies), and its outward reach (federation and bridged external networks).
flowchart LR
subgraph deps [Dependencies]
dep_svc_bkp_volume_2_local["svc-bkp-volume-2-local 💻"]
dep_svc_db_openldap["svc-db-openldap 🐳🐝"]
dep_svc_db_postgres["svc-db-postgres 🐳🐝"]
dep_svc_db_redis["svc-db-redis 🐳🐝"]
dep_svc_net_tor["svc-net-tor 🐳🐝"]
dep_web_app_dashboard["web-app-dashboard 🐳🐝"]
dep_web_app_keycloak["web-app-keycloak 🐳🐝"]
dep_web_app_matomo["web-app-matomo 🐳🐝"]
dep_web_app_prometheus["web-app-prometheus 🐳🐝"]
dep_web_app_stalwart["web-app-stalwart 🐳🐝"]
dep_web_svc_css["web-svc-css 💻"]
dep_web_svc_logout["web-svc-logout 🐳🐝"]
end
subgraph role [web-app-odoo 🐳🐝]
svc_sso["sso"]
svc_ldap["ldap"]
svc_logout["logout"]
svc_dashboard["dashboard"]
svc_matomo["matomo"]
svc_email["email"]
svc_postgres["postgres"]
svc_odoo["odoo"]
svc_redis["redis"]
svc_css["css"]
svc_javascript["javascript"]
svc_prometheus["prometheus"]
svc_tor["tor"]
svc_container_backup["container_backup"]
end
dep_svc_bkp_volume_2_local -. "0..1" .-> svc_container_backup
dep_svc_db_openldap -. "0..1" .-> svc_ldap
dep_svc_db_postgres -. "0..1" .-> svc_postgres
dep_svc_db_redis -. "0..1" .-> svc_redis
dep_svc_net_tor -. "0..1" .-> svc_tor
dep_web_app_dashboard -. "0..1" .-> svc_dashboard
dep_web_app_keycloak -. "0..1" .-> svc_sso
dep_web_app_matomo -. "0..1" .-> svc_matomo
dep_web_app_prometheus -. "0..1" .-> svc_prometheus
dep_web_app_stalwart -. "0..1" .-> svc_email
dep_web_svc_css -. "0..1" .-> svc_css
dep_web_svc_logout -. "0..1" .-> svc_logoutSolid 1:1 edges are fixed relationships; dashed 0..1 edges are
conditional (enabled only in matching deployments); red 0..0 edges
are turned off in this role. Node markers show the role’s deploy modes
(💻 host, 🐳 compose, 🐝 swarm); ❌ marks a service that is explicitly
turned off, and ⚙️ an Ansible role dependency declared in
meta/main.yml.
Purpose¶
The purpose of this role is to provide a hands-off, production-ready Odoo ERP deployment that integrates seamlessly with the Infinito.Nexus platform. Organizations can leverage Odoo’s comprehensive business management capabilities while benefiting from centralized authentication, backup, monitoring, and security features.
Features¶
CRM & Sales Management: Track leads, opportunities, and customer relationships. Manage sales pipelines, quotations, and orders with full visibility into sales performance.
Accounting & Finance: Handle invoicing, payments, bank reconciliation, and financial reporting. Supports multi-currency and multi-company operations.
Inventory & Warehouse: Manage stock levels, transfers, and warehouse operations. Supports barcode scanning, batch picking, and advanced routing.
Website & E-Commerce: Build and manage professional websites with integrated e-commerce capabilities, forms, and online payment processing.
Project Management: Plan and track projects with Gantt charts, Kanban boards, and time tracking. Integrate with sales and invoicing for complete project billing.
Human Resources: Manage employees, recruitment, expenses, leaves, and appraisals. Optional HR modules provide comprehensive workforce management.
Marketing & Automation: Create email campaigns, marketing automation workflows, and social media management integrated with CRM data.
OIDC Authentication: Single sign-on via Keycloak integration for seamless identity management across the Infinito.Nexus ecosystem.
LDAP Authentication: Enterprise directory integration via OpenLDAP for organizations using traditional directory services.
WebSocket Support: Real-time notifications and live chat capabilities through WebSocket connections.
Quick Setup¶
Development¶
Clone, set up the workstation, and deploy Odoo ERP onto the local stack:
git clone https://github.com/infinito-nexus/core.git
cd core
make onboard
make compose-deploy mode=reinstall apps=web-app-odoo full_cycle=false
Production¶
Run the published image to provision the inventory and deploy Odoo ERP to a managed server (the mounted volume persists the inventory):
APP=web-app-odoo
HOST=<your-server>
DOMAIN=<your-domain>
TLS_MODE=self_signed
SSH_PUBLIC_KEY="<your-ssh-public-key>"
docker run --rm -it \
-v "$PWD/inventories:/etc/infinito.nexus/inventories" \
-e APP="$APP" -e HOST="$HOST" -e DOMAIN="$DOMAIN" -e TLS_MODE="$TLS_MODE" -e SSH_PUBLIC_KEY="$SSH_PUBLIC_KEY" \
ghcr.io/infinito-nexus/core/debian bash -c '
INVENTORY=/etc/infinito.nexus/inventories/production
infinito administration inventory provision "$INVENTORY" \
--inventory-file "$INVENTORY/devices.yml" \
--host "$HOST" \
--include "$APP" \
--vars "{\"TLS_MODE\": \"$TLS_MODE\", \"DOMAIN_PRIMARY\": \"$DOMAIN\", \"users\": {\"administrator\": {\"authorized_keys\": [\"$SSH_PUBLIC_KEY\"]}}}" &&
infinito administration deploy dedicated "$INVENTORY/devices.yml" \
--password-file "$INVENTORY/.password" \
--diff -vv'
Modules¶
Odoo’s functionality is delivered through a modular architecture. The following core modules are installed by default:
Module |
Description |
|---|---|
crm |
Customer Relationship Management - track leads, opportunities, and customer interactions |
contacts |
Centralized contact management for customers, vendors, and partners |
sale_management |
Sales pipeline, quotations, orders, and invoicing workflows |
account |
Full accounting suite including invoicing, payments, and financial reporting |
website |
Website builder with drag-and-drop editor and SEO tools |
project |
Project management with Kanban boards, Gantt charts, and time tracking |
stock |
Inventory and warehouse management with barcode support |
Additional modules can be enabled by declaring them as
group: optional addons in `meta/addons/ <meta/addons/>`__.
Addons¶
Odoo modules are declared as addons in
`meta/addons/ <meta/addons/>`__ per the unified addon contract
(requirement 026). The install path reads them from
applications.web-app-odoo.addons.
Addon |
Mechanism |
Default state |
Bridges |
|---|---|---|---|
crm |
module |
enabled (required) |
none |
contacts |
module |
enabled (required) |
none |
sale_management |
module |
enabled (required) |
none |
account |
module |
enabled (required) |
none |
website |
module |
enabled (required) |
none |
project |
module |
enabled (required) |
none |
stock |
module |
enabled (required) |
none |
All core modules carry required: true and group: core, so they
are always installed. The optional group is empty today.
Deployment¶
Deploy Odoo using the standard Infinito.Nexus deployment command:
make compose-deploy mode=reinstall apps=web-app-odoo
For subsequent updates:
make compose-deploy mode=update apps=web-app-odoo
Access¶
After deployment, Odoo is accessible at:
URL:
odoo.erp.{DOMAIN}(HTTPS)Admin Login: Uses configured administrator credentials
SSO Login: “Login with SSO” button (when OIDC is enabled)
Developer Notes¶
The Odoo configuration file is templated to
/etc/odoo/odoo.confCustom addons can be placed in
files/addons/and will be mounted at/mnt/custom-addonsDatabase operations use the master password for security
WebSocket connections are routed through port 8072
HTTPS OAuth Redirect Fix¶
The role includes a custom auth_oauth_https addon that fixes OAuth
redirect URIs when running behind a reverse proxy with TLS termination.
The standard auth_oauth module may incorrectly generate HTTP
redirect URIs. This addon overrides the behavior to use the
web.base.url system parameter, ensuring HTTPS is always used.
Inspecting the Container¶
make compose-exec
# Then inside the container:
odoo shell -d <database_name>
Log Access¶
docker logs odoo -f
Persona contract opt-outs¶
The shared biber and administrator persona helpers are declared
blocked in
templates/playwright.env.j2. Odoo
renders its SSO provider link only on /web/login inside the
.o_login_auth container, not on the site root the persona helper
starts from, and its logout sits behind the user menu. The full Keycloak
round trip for both users is covered by the role’s own
odoo: admin sso login, verify ui, logout and
odoo: biber sso login, verify ui, logout scenarios in
files/playwright/playwright.spec.js.
Credits¶
Implemented by Evangelos Tsakoudis. Part of the Infinito.Nexus Project and maintained by Kevin Veen-Birkenbach. Licensed under the Infinito.Nexus Community License (Non-Commercial).