OdooWiki OCA HUB

OCA/server-env

OCA community repository with 14 Odoo modules confirmed in the OdooWiki catalogue (versions 12.0, 13.0, 14.0, 15.0, 16.0, 17.0, 18.0, 19.0). Reviewed on 2026-11-03.

Open on GitHub

Confirmed modules per version

12.0
8 modules
13.0
4 modules
14.0
10 modules
15.0
7 modules
16.0
7 modules
17.0
7 modules
18.0
7 modules
19.0
3 modules
20.0
0 modules

Modules in the repository

  • Auth SAML environementOdoo 14, 15, 18
    auth_saml_environment

    Lets administrators configure SAML single sign-on settings (identity provider metadata, certificates, entity ID) from server environment configuration files instead of typing them in Odoo, and adds file-path fields for the SAML certificates.

  • carrier_environment

    Lets you store carrier account credentials (account, password, file format) in server environment configuration files instead of the Odoo database, so production and test servers can use different carrier settings.

  • Encryption dataOdoo 12, 14, 16, 17, 18
    data_encryption

    This module stores sensitive data such as passwords and credentials in encrypted form, separated by environment (for example production or pre-production). It is a technical building block: it has no menu of its own and is meant to be used by other modules.

  • Mail configuration with server_environmentOdoo 12, 13, 14, 15, 16, 17, 18, 19
    mail_environment

    Lets you manage incoming and outgoing mail server settings from external configuration files instead of typing them in Odoo, so production and test environments can use different mail servers.

  • mail_environment_google_gmail

    Lets administrators store the Google Gmail authorization code and refresh token for outgoing mail servers in server environment configuration files instead of typing them in Odoo.

  • mail_environment_office365

    Lets administrators configure the Office365 outgoing mail server authentication through server environment variables instead of typing it in Odoo. It extends the existing mail server settings with one extra environment-driven field.

  • payment_environment

    Lets administrators store payment acquirer settings (such as the enabled/disabled state) in server environment configuration files instead of the Odoo database, so sensitive or environment-specific values stay outside the database.

  • pos_environment

    Lets administrators add a custom header and footer text to Point of Sale receipts, so tickets printed in test, pre-production or production environments can be told apart.

  • server configuration environment filesOdoo 12, 13, 14, 15, 16, 17, 18, 19
    server_environment

    Lets administrators move sensitive or environment-specific settings (paths, credentials, server addresses) out of the Odoo database and into configuration files or environment variables, and view the active configuration from a dedicated screen.

  • server_environment_autocreate

    Automatically creates records in Odoo when a matching configuration section is found in the server environment file, using the server_environment module.

  • Server Environment Data EncryptionOdoo 12, 14, 16, 17, 18
    server_environment_data_encryption

    Lets administrators store environment-specific configuration values (like API keys or credentials) in encrypted form inside Odoo, and edit them for each environment from the production server.

  • server_environment_files_sample

    This module is an example configuration file repository used together with the server_environment module. It adds no screens or features by itself; it only provides sample environment configuration files.

  • server_environment_iap

    Lets administrators define IAP account credentials (service name and account token) in server environment configuration files instead of typing them in Odoo, so production and test environments can use different IAP accounts.

  • Server Environment Ir Config ParameterOdoo 12, 13, 14, 15, 16, 17, 18, 19
    server_environment_ir_config_parameter

    Lets Odoo system parameters be driven by the server configuration file instead of the database. Parameters defined there are marked as environment-defined and become read-only in the interface.

Data imported from GitHub: every listed version is confirmed (branch, module directory and installable manifest checked on the review date). Active support and OCA certification are not assessed.