OdooWiki OCA HUB

Storage Backend Environment

storage_backend_environment folder_open OCA/storage open_in_new
Storage License: LGPL-3

Glue module for storage_backend to use server_environment

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Lets administrators configure storage backends (type and directory path) from the server configuration file instead of typing them in Odoo, so those settings are managed outside the database.

This module connects storage backends with the server environment feature. Once installed, the storage backend type and its directory path can be defined in the server configuration file rather than being entered manually on the storage backend record in Odoo.

  • The fields backend_type and directory_path on storage.backend become environment-managed: their values come from the server configuration.
  • When the module is installed, existing values in those fields are preserved so that data already entered in the database is not lost.
  • If the module is uninstalled, the database columns that were removed by the server environment mechanism are restored, so the information becomes editable in Odoo again.

It does not add menus, buttons, reports or scheduled jobs. It only changes how the storage backend configuration is sourced, which is useful when the same database is deployed on several servers with different storage locations. The module touches the storage.backend model and depends on the storage backend and server environment modules.

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.