How do I add Redis, Gotenberg or ClamAV to my Odoo instance?

Some needs aren't solved inside Odoo but next to Odoo: pooling sessions, producing better PDFs, scanning the attachments you receive. Hodiploy lets you start those services alongside your ERP, in a few clicks, on your own server.

Where it happens

1. Log in to Hodiploy from your Client Area
2. On the instance's row, open the "Actions" menu, then "Edit"
3. Scroll down to the "Addon services" section
4. Tick the service you want, then save

Services are set like the rest of the form: ticking a box describes what you want, and saving is what applies it. Once started, the service runs alongside the ERP without touching your data or your code, and the screen reminds you the name your Odoo will reach it under.

The services on offer

Redis

Shared sessions and cache. Useful as soon as your instance runs with several workers.

On the Odoo side you need the session_redis module from odoo-cloud-platform (Camptocamp), added to your modules. It is configured through environment variables and refuses to start if the configuration is inconsistent, which beats a silent half-working start.

Hostname: redis

Gotenberg

HTML and office document conversion to PDF, by a dedicated service. Useful when wkhtmltopdf renders an ambitious layout badly, or to convert Office documents without installing LibreOffice into your ERP image.

On the Odoo side it is used from your own modules, or from a module that already knows how to talk to Gotenberg.

Hostname: gotenberg

ClamAV

Antivirus scanning of attachments uploaded by your users. The request comes up as soon as a client receives files from the outside, and it is sometimes mandatory in regulated sectors.

On the Odoo side you need a module that submits attachments to the daemon before saving them.

Hostname: clamav

How your Odoo reaches them

By name, never by IP address, and without specifying a port.

The name is the only stable thing: a service's IP address changes every time its container is recreated, so writing it into your configuration would be scheduling an outage for later. The port depends on the module using the service and on how you configure it: that's for your module to know, not for this page to freeze.

No port is published to the internet. An addon service talks to your ERP over the instance's internal network, and to nobody else. There is nothing to open in your firewall and no new exposed surface: these services are unreachable from outside the machine, including by you.

Versions and updates

By default, a service follows the version we recommend, and so picks up security fixes every time your instance is updated. That's the right setting for a service nobody watches day to day.

If you need things to stand still, you can pin an exact version when enabling it. The service then stays exactly where you put it, even when we move our recommendation forward. The trade-off is real: no security fix will reach it either, until someone changes that version.

Resources

Each service starts with deliberately modest CPU and memory ceilings, so that a background service never starves your ERP. Those ceilings come, like everything else, out of your server's capacity: if you enable several services on an already busy machine, keep some headroom, or grow the server.

And in backups?

Each service is treated according to what it actually holds, and the detail matters:

• Redis: its sessions are backed up. It's small, and it saves logging all your users out after a restore.
• Gotenberg: nothing to back up, it converts and forgets.
• ClamAV: its signature database is deliberately not backed up. It re-downloads itself on start, and you wouldn't want to restore a stale signature database anyway.

You'll find these pieces in the "Backups & import" screen, under "Addon services", and they download like any other.

Disabling a service

Untick the service, then save. That removes the container but keeps its data: someone shutting a service down for the duration of a fix doesn't expect to find it empty the next day, and nothing would distinguish "I'm switching it off" from "I'm deleting it". The data goes with the instance, like the rest.

What's not on the list, and why

Tools with a web interface (Metabase, OnlyOffice, n8n and friends) aren't there: the "no published port" rule would make them unreachable, and serving them properly would take a subdomain and dedicated configuration per service. That's a subject of its own, and one we're happy to discuss.

The asynchronous job runner (queue_job) is not an addon service: it's a second container of your ERP, with the same image and the same configuration. It's handled differently.

A need that isn't covered?

This list is deliberately short: each entry solves a problem we've seen on real instances. If yours isn't there, contact us and let's talk about it.

Updated on: 24/08/2026