Documentation Deploy & operate
Installers
Services that run on your servers beside Odoo: what comes with every server, the apps you can add, and how to install, open, update and remove them.
What installers are
An installer is a service that runs on one of your servers, next to your Odoo apps, in its own Docker container. Each one is reached through the server's router at its own address.
A few come with every server and keep it working:
| Installer | What it does |
|---|---|
| Traefik | Routes your apps' domains to them and takes care of their certificates. |
| Promtail | Sends the server's and the apps' logs to your log views. |
| Node Exporter | Reports the server's CPU, memory, disk and load. |
| cAdvisor | Reports what each container uses. |
Others you add when you need them (see What you can install).
A server's installers
Open the server, then Installers. Installed lists what runs there. When installers depend on each other, they are grouped by level. Available to install lists what you can add.
Each installed card shows the service's state, how it is deployed, its domain, and the buttons you may use on it: open the service, get its password, update it, uninstall it, and more.
Installing a service
- On the server's Installers, find the service under Available to install and press Install.
- Check the dialog. Configs holds the deployment method (Docker), the server, the service, and the namespace that owns it. Dependencies holds the domain provider that gives the service its address. A service that comes as a bundle also lists the components to install with it.
- Press Create. The installer is made and its installation starts. Follow it on the installer's Operations.
What you can install
The list depends on your server: Rancher, for example, is not offered on Docker servers.
| Category | Services |
|---|---|
| Monitoring & Observability | Uptime Kuma, Grafana, Prometheus, Loki, cAdvisor, Node Exporter, Promtail |
| Development Tools | Coder, Gitea, Harbor |
| Databases | pgAdmin, MongoDB, Redis |
| Automation | n8n |
| File Management | Nextcloud, Filestash, MinIO |
| Security & Auth | Authentik, Keycloak, Vaultwarden |
| Communication | Element (Matrix), Mattermost |
| Productivity | Outline, Plausible Analytics |
| CMS & Web | Ghost, Strapi, WordPress |
| AI & Machine Learning | Ollama, Open WebUI |
| Media | Immich, Jellyfin |
| Container Management | Portainer, Rancher |
An installer's screen
Click an installer to open it. Its header has Open, the password button, Deploy, Update and More.
- Overview: its name, state, server and namespace; how it is deployed, its load balancer, Service URL and domain provider; and the projects that use it.
- URLs: the addresses it answers on, and their certificates.
- Tunnel Access: shown when SSH Tunnel Access is on (see below).
Opening a service and its password
Open opens the service in a new tab. For a service that keeps a login of its own, such as Grafana, pgAdmin or Filestash, the key button shows its password: CloudWady asks for your own password first, then shows it. Getting a password needs developer access or above.
Coder
Coder is a code editor that runs on your server. Once it is installed, the environment's toolbar has a Coder button that opens the editor in its own window; before that, the button installs it. With Platform Session Login on (Coder on Docker behind Traefik), you sign in with your CloudWady login instead of Coder's own password. The change applies on the next Update.
SSH tunnel access
SSH Tunnel Access, on an installer's Overview, also publishes the service on the server's own loopback address. Nothing outside the server can reach it there, but you can through an SSH tunnel: the way in when the service's route is down. It works for Docker installers on a server behind Traefik, and applies on the next Update or Refresh Routes.
The Tunnel Access tab then shows the commands to open the tunnel, to the people who may open a terminal on that server. Your SSH key must be on the server user it names (see SSH keys). On Windows, run the commands in PowerShell, which has OpenSSH built in.
Updating and removing
| Action | What it does |
|---|---|
| Update | Applies the installer's current settings and version to the server. |
| Deploy | Runs the full installation again. |
| Retry | Runs a failed installation again. |
| Uninstall | Removes the service from the server. |
| Delete | Removes an installer that was never installed. |
| Deploy All / Update All | On an installer with components: does the same for all of them. |
All your installers
Infrastructure → Installers lists every installer on all your servers, with filters by server, type and state, and the runs of each.
Monitoring boards
A server's Monitoring menu shows dashboards for that server: system metrics, containers, Docker logs and Odoo logs, with Fullscreen to give them the whole screen. They read what Promtail, Node Exporter and cAdvisor send, so keep those installed. Monitoring comes with the Essential, Pro and Premium plans.
Who can do what
An installer belongs to its server's environment: a server that hosts production apps is a production server (see Permissions & access).
| Action | Development or staging server | Production server |
|---|---|---|
| See installers | Viewer | Viewer |
| Get a service's password | Developer | Developer |
| Update an installer | Developer Plus | Maintainer |
| Install a service | Maintainer | Maintainer |
| Uninstall a service | Maintainer | Admin |
Was this page helpful?
Your answer helps us prioritize documentation improvements.
Thanks — your feedback helps us improve.
Type to search titles and text.
↑↓ to move ↵ to open Esc to close