Skip to content

Settings and options

Only owners and admins can change an environment. Every change here takes effect at the next deploy.

  • Type: dev, staging or production.
  • Resources: a preset or your own CPU cores and memory.
  • Branch: empty means the branch of the project’s main repository.
  • PostgreSQL version: fixed after the first deploy.
  • odoo.conf parameters: a name and a value per row, for example list_db. An empty value removes the parameter. A parameter you give wins over the tuned one; parameters the platform manages itself are refused.

Shows docker-compose.yml and odoo.conf as the next deploy would write them, with secrets hidden. Use it to check a change before deploying.

Choice What it means
Follow the version’s tag The image of the project’s Odoo version (for example odoo:18.0), pulled again at every deploy
Freeze at the deployed image Stay on exactly the image of the last deploy. Deploy once first
An image you name Your own build, or one from a registry of yours

Switch on Update the image every night. An environment that follows its version’s tag then updates itself at night when a newer image exists. A new image that does not start is rolled back to the old one.

Option What it does
PGTune Sets PostgreSQL’s memory and planner settings from the database’s share of the environment’s memory
PgBouncer A connection pooler between Odoo and PostgreSQL (session mode), for many workers at once
Mailtest Every email Odoo sends is caught in a test inbox (the Mailtest tab) and never delivered
Connect As Owners and admins may sign in to this Odoo as one of its users (Connect As)

Under PostgreSQL settings of your own you can add settings such as work_mem = 32MB. They win over PGTune.

The same tab holds Deploy on push and Scheduled actions.