Skip to main content

Environment Settings

Learn how to adjust and configure your environment settings.

Opening Settings​

To open environment settings:

  1. Open the environment
  2. Click on the "Settings" tab
  3. The settings page opens

General Settings​

  1. Log Level - Configure in which level odoo should use.

    • Info - All information
    • Warning - Warnings and errors
    • Error - Only errors
    • Critical - Only critical errors
    • Debug - Detailed debug information
    • Debug SQL - Detailed debug with SQL queries
    • Debug RPC - Detailed debug with RPC calls
    • Debug RPC Answer - Detailed debug with RPC answers

  2. Code Tests - Select how your code is tested before each deployment.

    • Skip Tests - No tests are run
    • Custom Tests - Installs the changed modules to verify that they can be installed without errors
    • Odoo Unit tests - Installs the changed modules and additionally runs their Odoo unit tests, if the modules provide any
    warning

    Choosing Skip Tests speeds up deployments but increases the risk of deploying broken code to your environment.

  3. Revision - Select a specific revision to deploy

    info

    Images are built weekly during the night from Sunday to Monday. By default, every system uses the latest build. You can revert to one of the last 9 builds. If you're on a build older than the last 9, you'll remain on it and won't be automatically reset.

  4. Rebuild - Perform a rebuild of the selected environment

  5. Rebase - Change the Odoo version of the environment

  6. odoo-upgrade - Prepare and request an Odoo version upgrade for your environment.

    Configure the following fields:

    • Select version - Choose the target Odoo version.
    • Select branch - Choose the Git branch to use for the upgrade.
    • Enter Odoo enterprise key - Provide your valid enterprise key.
info

There are 2 ways to upgrade a system: through us, or directly via Odoo (upgrade.odoo.com).

For the Odoo route, you need to download a system backup, upload it there, and when it is finished and returned, import it again.

Currently, only the latest 4 versions are available (16 to 19).

Security Settings​

Connect Reason​

The Connect button lets you log into Odoo directly as one of the users of the environment. With Connect Reason enabled, everyone who uses that button has to state why they are logging in before the login is performed.

To enable the option:

  1. Open the environment
  2. Go to the "Settings" tab
  3. In the "Connect Reason" section, tick "Require a reason when connecting"

While the option is active:

  1. Clicking Connect opens the "Connect Reason" dialog asking "Why do you want to log into this system?"
  2. Enter a reason (for example Support ticket #1234) - the field is mandatory
  3. Click "Connect" to continue, or "Cancel" to abort the login

The reason is stored together with the login in the audit log of the project. Open the entry there and click "View Details" to find it in the Extra Data field as connect_reason, next to the user, timestamp, IP address, browser, and the environment that was accessed.

tip

Enable this option whenever logins as another user need to be documented - for example because of compliance requirements or as proof for your own audits. Every login is then recorded in the audit log together with its reason.

info

Connect Reason is configured per environment. Enabling it for Production does not change anything for your Staging environments.

Domain Settings​

Custom Mail Domain​

You will find a manual how to setup a custom mail domain in Odoo

info

If you want to use our mail-gateway the default attachment size is 10 MB

Custom Domain​

If available, you can configure your own domain:

  1. In "Custom Domain" section under settings
  2. Enter your domain (e.g., app.example.com)
  3. Follow the instructions for DNS configuration
  4. Click on "Save"
info

DNS configuration can take some time.
Please note that only sub-domains are possible

Submodules​

To add a submodule or a third-party module:

  1. Type the SSH-link of the GitHub-Repo in the field

  2. Click then on Save - a deploy key will be automatically generated

  3. Copy the deploy key and paste it in the "deploy keys" in your GitHub-Repo settings

  4. Add the submodule manually to your repository with:

    git submodule add https://github.com/company/repo.git`

    and checkout your specific branch or commit

  5. Push the changes to the repository and a new build is triggered in the UI

info

The registered submodule will be fetched and included on the next deployment, as long as a Deploy Key is configured.

caution

The folder name of the submodule must exactly match the name of the external repository.

Example:

✅ Correct:

git submodule add git@github.com:opaas-cloud/test.git
git submodule add git@github.com:opaas-cloud/test.git test

❌ Incorrect:

git submodule add git@github.com:opaas-cloud/test.git addons

Worker Settings​

By default, production environments include one HTTP worker and one Cron worker. Staging cron worker are disabled by default and come with one HTTP worker. You can configure the number of workers (HTTP and Cron) based on your subscription plan.

info

Worker configuration changes do not cause downtime unless you set the worker count to 0.

Next Steps​

After adjusting settings:

  1. Set up backups - Back up your data
  2. Configure monitoring - Monitor your application
  3. View logs - Monitor the application
tip

Always test changes in Staging before Production to avoid problems!