Glue module for fs_folder to use fs_storage_environment
auto_awesome What this module does
AI-generated from the code · Odoo 18.0This module lets administrators control the 'Use as default for FS contents' setting of filesystem storage configurations from the server environment file instead of the Odoo interface.
This is a technical glue module that connects filesystem storage folders with Odoo's server environment configuration system. It does not add any new menus or screens.
What it changes:
- The 'Use as default for FS contents' option on filesystem storage records (fs.storage) can now be defined in the server environment configuration file rather than being edited manually in Odoo.
- When the module is installed, existing values of that setting are preserved so they are not lost when the environment takes over.
- When the module is uninstalled, the database column for that setting is restored so the data remains available.
Where it appears in Odoo: - There are no new menus or buttons. The effect is visible on the existing filesystem storage configuration screens, where the 'Use as default for FS contents' field becomes managed by the server environment.
Business rules and automatic behaviour: - The setting is read from the server environment at startup, so it is consistent across all databases using the same configuration. - No scheduled jobs, emails, or computations are added.
Odoo areas touched:
- Filesystem storage configuration (fs.storage).
- Server environment configuration (through the fs_storage_environment dependency).
- Filesystem folders (through the fs_folder dependency).
Depends on
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-03Confirmation status: 1 confirmed, 8 with no information of 9 versions.
Sources · Odoo 18.0
Confirmed on 2026-11-03 in branch 18.0 of OCA/storage.
terminal Installation and usage
No verified informationInstallation 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.
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.