The manifest file serves to both declare a python package as an Odoo module, and to specify a number of module metadata.
It is a file called __openerp__.py and contains a single Python dictionary, each dictionary key specifying a module metadatum.
{
'name': "A Module",
'version': '1.0',
'depends': ['base'],
'author': "Author Name",
'category': 'Category',
'description': """
Description text
""",
# data files always loaded at installation
'data': [
'mymodule_view.xml',
],
# data files containing optionally loaded demonstration data
'demo': [
'demo_data.xml',
],
}
Available manifest fields are:
classification category within Odoo, rough business domain for the module.
Although using existing categories is recommended, the field is freeform and unknown categories are created on-the-fly. Category hierarchies can be created using the separator / e.g. Foo / Bar will create a category Foo, a category Bar as child category of Foo, and will set Bar as the module’s category.
Odoo modules which must be loaded before this one, either because this module uses features they create or because it alters resources they define.
When a module is installed, all of its dependencies are installed before it. Likewise during modules loading.
If True, this module will automatically be installed if all of its dependencies are installed.
It is generally used for “link modules” implementing synergic integration between two otherwise independent modules.
For instance sale_crm depends on both sale and crm and is set to auto_install. When both sale and crm are installed, it automatically adds CRM campaigns tracking to sale orders without either sale or crm being aware of one another
odoo docs theme based on Bootstrap 3.2 documentation adapted to Sphinx output with branding and color changes.