[REM] sale_amazon: update not necessary anymore

task-2694222

.gitattributes

@@ -0,0 +1,2 @@
+# Include RST files in language statistics on GitHub.
+*.rst linguist-detectable

.github/CODEOWNERS

@@ -1,11 +0,0 @@
-# All changes to technical files (build environment and Sphinx extensions) have to be approved
-/extensions/         @odoo/doc-review
-.gitignore           @odoo/doc-review
-commit_template.txt  @odoo/doc-review
-conf.py              @odoo/doc-review
-Makefile             @odoo/doc-review
-requirements.txt     @odoo/doc-review
-
-# All changes to legal material have to be approved
-/content/legal/     @odoo/legal
-/content/legal.rst  @odoo/legal

.gitignore

@@ -1,10 +1,10 @@
 *.pyc
-.*
 *.mo
+.*
+!.gitattributes
 
 # Sphinx build files
 _build/
-extensions/odoo_theme/static/style.css
 
 # Dependencies
 odoo

.tx/config

@@ -47,6 +47,11 @@ file_filter = locale/<lang>/LC_MESSAGES/services.po
 source_file = locale/sources/services.pot
 source_lang = en
 
+[odoo-14-doc.theme]
+file_filter = locale/<lang>/LC_MESSAGES/sphinx.po
+source_file = locale/sources/sphinx.pot
+source_lang = en
+
 [odoo-14-doc.user_settings]
 file_filter = locale/<lang>/LC_MESSAGES/settings.po
 source_file = locale/sources/settings.pot
@@ -55,4 +60,4 @@ source_lang = en
 [odoo-14-doc.websites]
 file_filter = locale/<lang>/LC_MESSAGES/websites.po
 source_file = locale/sources/websites.pot
-source_lang = en
+source_lang = en

Makefile

@@ -1,8 +1,16 @@
 # Makefile for Sphinx documentation
 
-# Pass WORKERS=auto for parallel build
+# Pass WORKERS=1 for single-worker build
 ifndef WORKERS
-  WORKERS = 1
+  WORKERS = auto
+endif
+
+ifndef BUILD_DIR
+  BUILD_DIR    = _build
+endif
+
+ifndef CURRENT_LANG
+  CURRENT_LANG = en
 endif
 
 SPHINX_BUILD   = sphinx-build
@@ -11,13 +19,14 @@ SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSIO
                  -D versions=$(VERSIONS) -D languages=$(LANGUAGES) -D language=$(CURRENT_LANG) \
                  -D is_remote_build=$(IS_REMOTE_BUILD) \
                  -A google_analytics_key=$(GOOGLE_ANALYTICS_KEY) \
+                 -A plausible_script=$(PLAUSIBLE_SCRIPT) \
+                 -A plausible_domain=$(PLAUSIBLE_DOMAIN) \
 				 -j $(WORKERS)
 SOURCE_DIR     = content
-BUILD_DIR      = _build
 
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
-  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/14.0
+  HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
 endif
 ifneq ($(CURRENT_LANG),en)
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/$(CURRENT_LANG)
@@ -37,10 +46,9 @@ help:
 clean:
 	@echo "Cleaning build files..."
 	rm -rf $(BUILD_DIR)/*
-	rm extensions/odoo_theme/static/style.css
 	@echo "Cleaning finished."
 
-html: extensions/odoo_theme/static/style.css
+html: $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Starting build..."
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b html $(SPHINXOPTS) $(SOURCE_DIR) $(HTML_BUILD_DIR)
 	@echo "Build finished."
@@ -60,16 +68,17 @@ gettext:
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) locale/sources
 	@echo "Generation finished."
 
-extensions/odoo_theme/static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
+$(HTML_BUILD_DIR)/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
 	@echo "Compiling stylesheets..."
-	pysassc $(subst .css,.scss,$@) $@
+	mkdir -p $(HTML_BUILD_DIR)/_static
+	python3 -m pysassc extensions/odoo_theme/static/style.scss $(HTML_BUILD_DIR)/_static/style.css
 	@echo "Compilation finished."
 
 #=== Development and debugging rules ===#
 
-fast: SPHINXOPTS += -A collapse_menu=True -j auto
+fast: SPHINXOPTS += -A collapse_menu=True
 fast: html
 
-static: extensions/odoo_theme/static/style.css
-	cp -r extensions/odoo_theme/static/* _build/html/_static/
-	cp -r static/* _build/html/_static/
+static: $(HTML_BUILD_DIR)/_static/style.css
+	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
+	cp -r static/* $(HTML_BUILD_DIR)/_static/

README.md

@@ -4,11 +4,11 @@
 
 ### Requirements
 
-- [Git](https://www.odoo.com/documentation/14.0/contributing/documentation/introduction_guide.html#install-git)
-- [Python 3.6, 3.7, or 3.8](https://www.odoo.com/documentation/14.0/contributing/documentation/introduction_guide.html#python)
-- Python dependencies listed in the file [`requirements.txt`](https://github.com/odoo/documentation/tree/14.0/requirements.txt).
-- [Make](https://www.odoo.com/documentation/14.0/contributing/documentation/introduction_guide.html#make)
-- A local copy of the [odoo/odoo repository in 14.0](https://github.com/odoo/odoo/tree/14.0) (Optional)
+- [Git](https://www.odoo.com/documentation/master/contributing/documentation.html#install-git)
+- [Python 3.7 or 3.8](https://www.odoo.com/documentation/master/contributing/documentation.html#python)
+- Python dependencies listed in the file [`requirements.txt`](https://github.com/odoo/documentation/tree/master/requirements.txt).
+- [Make](https://www.odoo.com/documentation/master/contributing/documentation.html#make)
+- A local copy of the [odoo/odoo repository in master](https://github.com/odoo/odoo/tree/master) (Optional)
 
 ### Instructions
 
@@ -23,7 +23,7 @@
 
 2. Open the file `documentation/_build/html/index.html` in your web browser to display the render.
 
-3. See [this guide](https://www.odoo.com/documentation/14.0/contributing/documentation/introduction_guide.html#preview-your-changes)
+3. See [this guide](https://www.odoo.com/documentation/master/contributing/documentation.html#preview-your-changes)
    for more detailed instructions.
 
 Optional: to fully build the developer documentation with inline docstrings for documented Python
@@ -34,15 +34,11 @@ be shown.
 ## Contribute to the documentation
 
 For contributions to the content of the documentation, please refer to the
-[Introduction Guide](https://www.odoo.com/documentation/14.0/contributing/documentation/introduction_guide.html).
+[Introduction Guide](https://www.odoo.com/documentation/master/contributing/documentation.html).
 
 To **report a content issue**, **request new content** or **ask a question**, use the
 [repository's issue tracker](https://github.com/odoo/documentation-user/issues) as usual.
 
-If you have a pull request that is ready for review, request one from the
-[odoo/doc-review](https://github.com/orgs/odoo/teams/doc-review) team.
-
-
 ## Learn More
 
 To learn more about Odoo, in addition to the documentation, have a look at

conf.py

@@ -1,9 +1,12 @@
 import re
 import os
+import shutil
 import sys
 from pathlib import Path
 
+import docutils
 from pygments.lexers import JsonLexer, XmlLexer
+from sphinx.ext import graphviz
 from sphinx.util import logging
 import sphinx
 
@@ -19,7 +22,7 @@ copyright = 'Odoo S.A.'
 # `version` if the version info for the project being documented, acts as replacement for |version|,
 # also used in various other places throughout the built documents.
 # `release` is the full version, including alpha/beta/rc tags. Acts as replacement for |release|.
-version = release = '14.0'
+version = release = 'master'
 
 # The minimal Sphinx version required to build the documentation.
 needs_sphinx = '3.0.0'
@@ -53,42 +56,72 @@ add_function_parentheses = True
 
 #=== Extensions configuration ===#
 
+source_read_replace_vals = {
+    'GITHUB_PATH': f'https://github.com/odoo/odoo/blob/{version}',
+    'GITHUB_ENT_PATH': f'https://github.com/odoo/enterprise/blob/{version}',
+}
+
 # Add extensions directory to PYTHONPATH
 extension_dir = Path('extensions')
 sys.path.insert(0, str(extension_dir.absolute()))
 
 # Search for the directory of odoo sources to know whether autodoc should be used on the dev doc
-odoo_dir = Path('odoo')
+odoo_sources_candidate_dirs = (Path('odoo'), Path('../odoo'))
+odoo_sources_dirs = [
+    d for d in odoo_sources_candidate_dirs if d.is_dir() and (d / 'odoo-bin').exists()
+]
 odoo_dir_in_path = False
-if not odoo_dir.is_dir():
+
+if not odoo_sources_dirs:
     _logger.warning(
-        f"Could not find Odoo sources directory at {odoo_dir.absolute()}.\n"
-        f"The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
-        f"In order to fully build the 'Developer' documentation, clone the repository with "
-        f"`git clone https://github.com/odoo/odoo` or create a symbolink link."
+        "Could not find Odoo sources directory in neither of the following folders:\n"
+        "%(dir_list)s\n"
+        "The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
+        "In order to fully build the 'Developer' documentation, clone the repository with "
+        "`git clone https://github.com/odoo/odoo` or create a symbolic link.",
+        {'dir_list': '\n'.join([f'\t- {d.resolve()}' for d in odoo_sources_candidate_dirs])},
     )
 else:
-    sys.path.insert(0, str(odoo_dir.absolute()))
+    if (3, 6) < sys.version_info < (3, 7):
+        # Running odoo needs python 3.7 min but monkey patch version_info to be compatible with 3.6.
+        sys.version_info = (3, 7, 0)
+    odoo_dir = odoo_sources_dirs[0].resolve()
+    source_read_replace_vals['ODOO_RELPATH'] = '/../' + str(odoo_sources_dirs[0])
+    source_read_replace_vals['ODOO_ABSPATH'] = str(odoo_dir)
+    sys.path.insert(0, str(odoo_dir))
+    import odoo.addons
+    odoo.addons.__path__.append(str(odoo_dir) + '/addons')
     from odoo import release as odoo_release  # Don't collide with Sphinx's 'release' config option
-    odoo_version = odoo_release.version if 'alpha' not in odoo_release.version else 'master'
+    odoo_version = odoo_release.version.replace('~', '-')  # Change saas~XX.Y to saas-XX.Y
+    odoo_version = 'master' if 'alpha' in odoo_release.version else odoo_version
     if release != odoo_version:
         _logger.warning(
-            f"Found Odoo sources directory but with version '{odoo_version}' incompatible with "
-            f"documentation version '{version}'.\n"
-            f"The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
-            f"In order to fully build the 'Developer' documentation, checkout the matching branch"
-            f" with `cd odoo && git checkout {version}`."
+            "Found Odoo sources in %(directory)s but with version '%(odoo_version)s' incompatible "
+            "with documentation version '%(doc_version)s'.\n"
+            "The 'Developer' documentation will be built but autodoc directives will be skipped.\n"
+            "In order to fully build the 'Developer' documentation, checkout the matching branch"
+            " with `cd odoo && git checkout %(doc_version)s`.",
+            {'directory': odoo_dir, 'odoo_version': odoo_version, 'doc_version': version},
         )
     else:
-        _logger.info(f"Found Odoo sources directory matching documentation version {release}.")
+        _logger.info(
+            "Found Odoo sources in %(directory)s matching documentation version '%(version)s'.",
+            {'directory': odoo_dir, 'version': release},
+        )
         odoo_dir_in_path = True
 
+# Mapping between odoo models related to master data and the declaration of the
+# data. This is used to point users to available xml_ids when giving values for
+# a field with the autodoc_field extension.
+model_references = {
+    'account.account.type': 'addons/account/data/data_account_type.xml',
+    'res.country': 'odoo/addons/base/data/res_country_data.xml',
+    'res.currency': 'odoo/addons/base/data/res_currency_data.xml',
+}
+
 # The Sphinx extensions to use, as module names.
 # They can be extensions coming with Sphinx (named 'sphinx.ext.*') or custom ones.
 extensions = [
-    # Parse Python docstrings (autodoc, automodule, autoattribute directives)
-    'sphinx.ext.autodoc' if odoo_dir_in_path else 'autodoc_placeholder',
-
     # Link sources in other projects (used to build the reference doc)
     'sphinx.ext.intersphinx',
 
@@ -101,27 +134,37 @@ extensions = [
     # Youtube and Vimeo videos integration (youtube, vimeo directives)
     'embedded_video',
 
-    'exercise_admonition',
+    'custom_admonitions',
 
     # Redirection generator
     'redirects',
 
-    # Code switcher (switcher and case directives)
-    'switcher',
+    # Content tabs
+    'sphinx_tabs.tabs',
 
     # Strange html domain logic used in memento pages
     'html_domain',
 ]
+
 if odoo_dir_in_path:
     # GitHub links generation
     extensions += [
         'sphinx.ext.linkcode',
         'github_link',
+        # Parse Python docstrings (autodoc, automodule, autoattribute directives)
+        'sphinx.ext.autodoc',
+        'autodoc_field',
     ]
+else:
+    extensions += [
+        'autodoc_placeholder',
+    ]
+extensions.append('sphinx.ext.graphviz' if shutil.which('dot') else 'graphviz_placeholder')
 
 todo_include_todos = False
 
 intersphinx_mapping = {
+    'pillow': ('https://pillow.readthedocs.io/en/stable/', None),
     'python': ('https://docs.python.org/3/', None),
     'werkzeug': ('https://werkzeug.palletsprojects.com/en/1.0.x/', None),
 }
@@ -130,13 +173,27 @@ github_user = 'odoo'
 github_project = 'documentation'
 
 locale_dirs = ['../locale/']
+templates_path = ['../extensions']
 
-# custom docname_to_domain to devide the translations of applications in subdirectories
+# custom docname_to_domain to divide the translations of applications in subdirectories
 sphinx.transforms.i18n.docname_to_domain = (
     sphinx.util.i18n.docname_to_domain
 ) = lambda docname, compact: docname.split('/')[1 if docname.startswith('applications/') else 0]
 
-supported_languages = {
+# The version names that should be shown in the version switcher, if the config option `versions`
+# is populated. If a version is passed to `versions` but is not listed here, it will not be shown.
+versions_names = {
+    'master': "Master",
+    'saas-15.2': "Odoo Online",
+    'saas-15.1': "Odoo Online",
+    '15.0': "Odoo 15",
+    '14.0': "Odoo 14",
+    '13.0': "Odoo 13",
+}
+
+# The language names that should be shown in the language switcher, if the config option `languages`
+# is populated. If a language is passed to `languages` but is not listed here, it will not be shown.
+languages_names = {
     'de': 'Deutsch',
     'en': 'English',
     'es': 'Español',
@@ -150,6 +207,9 @@ supported_languages = {
 # The specifications of redirect rules used by the redirects extension.
 redirects_file = 'redirects.txt'
 
+sphinx_tabs_disable_tab_closing = True
+sphinx_tabs_disable_css_loading = True
+
 #=== Options for HTML output ===#
 
 html_theme = 'odoo_theme'
@@ -174,7 +234,7 @@ html_permalinks = True  # Sphinx >= 3.5
 # Additional JS & CSS files that can be imported with the 'custom-js' and 'custom-css' metadata.
 # Lists are empty because the files are specified in extensions/themes.
 html_js_files = []
-html_css_files = []
+html_css_files = ["css/js.css"]
 
 # PHP lexer option to not require <?php
 highlight_options = {
@@ -192,7 +252,7 @@ latex_elements = {
     'tableofcontents': '',  # no TOC
 
     # Output manually in latex docs
-    'releasename': '14.0',
+    'releasename': release,
 }
 
 latex_additional_files = ['static/latex/odoo.sty']
@@ -232,6 +292,22 @@ latex_logo = 'static/img/odoo_logo.png'
 # If true, show URL addresses after external links.
 latex_show_urls = 'True'
 
+# https://github.com/sphinx-doc/sphinx/issues/4054#issuecomment-329097229
+def source_read_replace(app, docname, source):
+    """Substitute parts of strings with computed values.
+
+    Since the RST substitution is not working everywhere, i.e. in directives'
+    options, we need to be able to input those values when reading the sources.
+    This is using the config `source_read_replace_vals`, mapping a name to its
+    replacement. This will look for the name surrounded by curly braces in the source.
+
+    Meant to be connected to the `source-read` event.
+    """
+    result = source[0]
+    for key in app.config.source_read_replace_vals:
+        result = result.replace(f"{{{key}}}", app.config.source_read_replace_vals[key])
+    source[0] = result
+
 
 def setup(app):
     # Generate all alternate URLs for each document
@@ -240,12 +316,34 @@ def setup(app):
     app.add_config_value('versions', None, 'env')
     app.add_config_value('languages', None, 'env')
     app.add_config_value('is_remote_build', None, 'env')  # Whether the build is remotely deployed
+    app.add_config_value('source_read_replace_vals', {}, 'env')
+    app.connect('source-read', source_read_replace)
 
     app.add_lexer('json', JsonLexer)
     app.add_lexer('xml', XmlLexer)
 
     app.connect('html-page-context', _generate_alternate_urls)
 
+    # Add a `condition` option on directives to ignore them based on config values
+    app.add_config_value('odoo_dir_in_path', None, 'env')
+    def context_eval(expr):
+        return eval(expr, {confval.name: confval.value for confval in app.config})
+
+    def patch(to_patch):
+        to_patch.option_spec['condition'] = context_eval
+        original_run = to_patch.run
+        def new_run(self):
+            if not self.options.get('condition', True):
+                return []
+            return original_run(self)
+        to_patch.run = new_run
+
+    for to_patch in (
+        sphinx.directives.code.LiteralInclude,
+        docutils.parsers.rst.directives.tables.CSVTable,
+    ):
+        patch(to_patch)
+
 
 def _generate_alternate_urls(app, pagename, templatename, context, doctree):
     """ Add keys of required alternate URLs for the current document in the rendering context.
@@ -277,15 +375,18 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
 
         The entry 'version' is added by Sphinx in the rendering context.
         """
-        # If the list of versions is not set, assume that the project has no alternate version
-        _alternate_versions = app.config.versions and app.config.versions.split(',') or []
-        context['alternate_versions'] = [
-            (_alternate_version, _build_url(_version=_alternate_version))
-            for _alternate_version in sorted(_alternate_versions, reverse=True)
-            if _alternate_version != version and (
-                _alternate_version != 'master' or pagename.startswith('developer')
-            )
-        ]
+        context['version_display_name'] = versions_names[version]
+
+        # If the list of versions is not set, assume the project has no alternate version
+        _provided_versions = app.config.versions and app.config.versions.split(',') or []
+
+        # Map alternate versions to their display names and URLs.
+        context['alternate_versions'] = []
+        for _alternate_version, _display_name in versions_names.items():
+            if _alternate_version in _provided_versions and _alternate_version != version:
+                context['alternate_versions'].append(
+                    (_display_name, _build_url(_alternate_version))
+                )
 
     def _localize():
         """ Add the pairs of (lang, code, url) for the current document in the rendering context.
@@ -296,19 +397,22 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
         """
         _current_lang = app.config.language or 'en'
         # Replace the context value by its translated description ("Français" instead of "french")
-        context['language'] = supported_languages.get(_current_lang)
+        context['language'] = languages_names.get(_current_lang)
 
         # If the list of languages is not set, assume that the project has no alternate language
-        _alternate_languages = app.config.languages and app.config.languages.split(',') or []
-        context['alternate_languages'] = [
-            (
-                supported_languages.get(_alternate_lang),
-                _alternate_lang.split('_')[0] if _alternate_lang != 'en' else 'x-default',
-                _build_url(_lang=_alternate_lang),
-            )
-            for _alternate_lang in _alternate_languages
-            if _alternate_lang in supported_languages and _alternate_lang != _current_lang
-        ]
+        _provided_languages = app.config.languages and app.config.languages.split(',') or []
+
+        # Map alternate languages to their display names and URLs.
+        context['alternate_languages'] = []
+        for _alternate_lang, _display_name in languages_names.items():
+            if _alternate_lang in _provided_languages and _alternate_lang != _current_lang:
+                context['alternate_languages'].append(
+                    (
+                        _display_name,
+                        _alternate_lang.split('_')[0] if _alternate_lang != 'en' else 'x-default',
+                        _build_url(_lang=_alternate_lang),
+                    )
+                )
 
     def _build_url(_version=None, _lang=None):
         if app.config.is_remote_build:

content/administration.rst

@@ -1,14 +1,22 @@
-==============
-Administration
-==============
+:nosearch:
+:show-content:
+:hide-page-toc:
+:show-toc:
+
+====================
+Install and Maintain
+====================
+
+These guides provide instructions on how to install, maintain and upgrade Odoo databases.
+
+.. seealso::
+    :doc:`History of Versions <administration/maintain/supported_versions>`
 
 
 .. toctree::
+    :titlesonly:
 
     administration/install
-    administration/deployment
-    administration/update
-    administration/db_upgrade
+    administration/maintain
+    administration/upgrade
     administration/odoo_sh
-    administration/db_management
-    administration/enterprise

content/administration/db_management.rst

@@ -1,10 +0,0 @@
-===================
-Database Management
-===================
-
-
-.. toctree::
-
-    db_management/db_online
-    db_management/db_premise
-    db_management/hosting_changes

content/administration/db_management/db_online.rst

@@ -1,233 +0,0 @@
-
-.. _db_online:
-
-==========================
-Online Database management
-==========================
-
-To manage your databases, access the `database management page
-<https://www.odoo.com/my/databases>`__ (you will have to sign in). Then click
-on the `Manage Your Databases <https://www.odoo.com/my/databases/manage>`__
-button.
-
-.. image:: media/databases.png
-    :align: center
-
-Make sure you are connected as the administrator of the database you
-want to manage - many operations depends on indentifying you remotely to that
-database.
-
-Several actions are available:
-
-.. image:: media/db_buttons.png
-    :align: center
-
-* :ref:`Upgrade <upgrade_button>`
-    Upgrade your database to the latest Odoo version to enjoy cutting-edge
-    features
-* :ref:`Duplicate <duplicate_online>`
-    Make an exact copy of your database, if you want
-    to try out new apps or new flows without compromising
-    your daily operations
-* :ref:`Rename <rename_online_database>`
-    Rename your database (and its URL)
-* **Backup**
-    Download an instant backup of your database; note that we
-    back up databases daily according to our Odoo Cloud SLA
-* :ref:`Domains <custom_domain>`
-    Configure custom domains to access your
-    database via another URL
-* :ref:`Delete <delete_online_database>`
-    Delete a database instantly
-* Contact Support
-    Access our `support page <https://www.odoo.com/help>`__
-    with the correct database already selected
-
-.. _upgrade_button:
-
-Upgrade
-=======
-
-.. warning:: Upgrading your database to a newer version of Odoo is a complex operation
-    that require time and caution. It is extremely important that you
-    fully test the process before upgrading your production database.
-
-Odoo releases new versions regularly (at least once a year), and upgrading your
-database to enjoy new Odoo features is part of the Odoo Online experience.
-
-The upgrade process can take some time, especially if you use multiple apps or
-apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In general,
-the 'smaller' the database, the quickest the upgrade. A single-user
-database that uses only CRM will be processed faster than a multi-company,
-multi-user database that uses Accounting, Sales, Purchase and Manufacturing.
-
-Unfortunately, it is impossible to give time estimates for every upgrade request,
-since Odoo.com will test manually every database upgrade at least once and will
-need to correct/adapt changes made to the standard Odoo Apps (e.g. through Studio
-or through a Success Pack) on a case-by-case basis. This can make the process
-slower, since requests are treated in the order they arrive. This is especially
-true in the months following the release of a new major version, which can lengthen
-the upgrade delay significantly.
-
-The upgrade process is quite simple from your point of view:
-
-1. You request a test upgrade
-2. Once all tests have been validated **by you**, you upgrade your actual database
-
-The process to request a test or a production (*actual*) upgrade is the same.
-
-First, make sure to be connected to the database you want to upgrade and access the
-`database management page <https://www.odoo.com/my/databases>`__.
-
-.. note:: You have to have an active session with access to the Settings app
-    in the database you want to upgrade for the button to be visible.
-
-On the line of the database you want to upgrade, click
-on the "Cog" menu. If an newer version of Odoo is available, you will see an 'Upgrade'
-button.
-
-.. image:: media/upgrade1.png
-    :align: center
-
-You have the possibility to choose the target version of the upgrade. By default,
-we select the highest available version available for your database; if you were
-already in the process of testing an upgrade, we will automatically select the
-version you were already testing (even if we released a more recent version during
-your tests).
-
-.. image:: media/upgrade_test.png
-    :align: center
-
-By clicking on the "Test upgrade" button, an upgrade request will be generated.
-Only one request can be made at time for each database; if a request has already
-been made, you will see an 'Upgrade Queued' note instead and asking another
-request will not be possible.
-
-A test upgrade will create a copy of your database, upgrade it and make it
-available to you automatically once successful. If this is the first test you
-request for this particular database, a manual testing phase will be done by
-Odoo.com - this could take time (up to several weeks). Subsequent requests
-will not go through that manual testing step and will usually be made
-available in a few hours. Once the test database is available, you should
-receive an e-mail with the URL of the test database.
-
-**Testing your database is the most important step of the upgrade process!**
-Even though we test all upgrades manually, we do not know your work processes.
-A change in standard worfklows of Odoo in new versions might require you to
-change internal processes, or some of the customizations you made through Odoo
-Studio might not work properly. *It is up to you to make sure that everything
-works as it should!* You can report issues with your test database through our
-`Support page <https://www.odoo.com/help>`__.
-
-Make sure to do one last test of your upgrade right before the final upgrade
-(e.g. the day before) to ensure everything will run smoothly. Downgrading is
-not possible and post-poning an upgrade is always easier than being prevented
-to work by an upgrade issue after the fact!
-
-Once you are ready and you have validated all your tests, you can click
-again on the Upgrade button and confirm by clicking on Upgrade (the button
-with the little rocket!) to switch your production database to the new version.
-Your database will then be taken offline within the next 10 minutes and will be
-upgraded automatically; you receive a confirmation
-e-mail once the process is completed.
-
-.. image:: media/upgrade_prod.png
-    :align: center
-
-.. warning::
-   Your database will be taken offline during the upgrade (usually between 30min up to several hours
-   for big databases), so make sure to plan your migration during non-business hours.
-
-.. _duplicate_online:
-
-Duplicating a database
-======================
-
-.. note:: Database duplication, renaming, custom DNS, etc. is not available
-    for trial databases on our Online platform. Paid Databases and "One App
-    Free" database can duplicate without problem.
-
-
-In the line of the database you want to duplicate, you will have a few
-buttons. To duplicate your database, just click **Duplicate**. You will
-have to give a name to your duplicate, then click **Duplicate Database**.
-
-.. image:: media/db_duplicate.png
-    :align: center
-
-.. danger:: If you do not check the "For testing purposes" checkbox when
-  duplicating a database, all external communication will remain active:
-
-  * Emails are sent
-
-  * Payments are processed (in the e-commerce or Subscriptions apps, for
-    example)
-
-  * Delivery orders (shipping providers) are sent
-
-  * Etc.
-
-  Make sure to check the checkbox "For testing purposes" if you want these
-  behaviours to be disabled.
-
-After a few seconds, you will be logged in your duplicated database.
-Notice that the url uses the name you chose for your duplicated
-database.
-
-.. note::
-   Duplicate databases expire automatically after 15 days.
-
-   .. image:: media/dup_expires.png
-      :align: center
-
-.. _rename_online_database:
-
-Rename a Database
-===================
-
-To rename your database, make sure you are connected to the database you want
-to rename, access the `database management page <https://www.odoo.com/my/databases>`__
-and click **Rename**. You will have to give a new name to your database,
-then click **Rename Database**.
-
-.. image:: media/rename.png
-    :align: center
-
-.. _delete_online_database:
-
-Deleting a Database
-===================
-
-You can only delete databases of which you are the administrator.
-
-.. danger:: When you delete your database all the data will be permanently lost.
-    The deletion is instant and for all the Users. We advise you to do an
-    instant backup of your database before deleting it, since the last automated
-    daily backup may be several hours old at that point.
-
-
-From the `database management page <https://www.odoo.com/my/databases>`__,
-on the line of the database you want to delete, click on the "Delete" button.
-
-.. image:: media/delete_button.png
-    :align: center
-
-
-Read carefully the warning message that will appear and proceed only if you
-fully understand the implications of deleting a database:
-
-.. image:: media/delete_warning.png
-    :align: center
-
-After a few seconds, the database will be deleted and the page will
-reload automatically.
-
-.. note::
-    * If you need to re-use this database name, it will be immediately available.
-
-    * It is not possible to delete a database if it is expired or linked
-      to a Subscription. In these cases contact
-      `Odoo Support <https://www.odoo.com/help>`__
-
-    * If you want to delete your Account, please contact
-      `Odoo Support <https://www.odoo.com/help>`__

content/administration/db_upgrade.rst

@@ -1,415 +0,0 @@
-
-.. |assistance-contact| replace::
-   If you need Odoo assistance on this matter, please contact your Odoo Account Manager or contact
-   our `Sales department`_.
-.. _Sales department: mailto:sales@odoo.com
-
-.. _db-upgrade:
-
-=======
-Upgrade
-=======
-
-.. _db-upgrade/overview:
-
-Overview
-========
-
-.. _db-upgrade/process:
-
-The upgrade process
--------------------
-
-This documentation is for our *On-Premise* (self-hosted) and *Odoo.sh* customers. If you are hosted
-Online, please check our :ref:`instruction page for our Online (SaaS) customers <upgrade_button>`.
-
-.. _db-upgrade/definition:
-
-Definition
-~~~~~~~~~~
-
-An upgrade is switching to a newer version of Odoo (e.g., Odoo 13.0 to Odoo 14.0)
-
-An upgrade does not cover:
-
-* changing :ref:`Editions <db-upgrade/faq/editions-change>` (i.e., Community to Enterprise edition)
-* switching :ref:`hosting type <db-upgrade/faq/hosting-types-switch>` (i.e., On-Premise to Online or
-  Odoo.sh)
-* migration from another ERP to Odoo
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/process-workflow:
-
-Process workflow
-~~~~~~~~~~~~~~~~
-
-The upgrade process in a nutshell:
-
-#. You create a test upgrade request.
-#. | The request is processed by Odoo:
-   | This happens via an automated process that runs the database through an upgrade script and
-     takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene
-     manually and adjust the script specifically to your database until the upgrade succeeds.
-#. Odoo delivers a test database.
-#. You test your database for possible discrepancies (see :ref:`db-upgrade/test-guidance`)
-#. If there are any discrepancies, you report them to the Upgrade support team via the
-   :ref:`Help portal <db-upgrade/test-assistance>`.
-#. We will fix the issues and send you a new test database.
-#. Once you completed the testing and are happy with the result, you decide on a date and time when
-   you stop users from accessing Odoo, freeze all data entries and create an upgrade request for the
-   production upgrade.
-#. Odoo delivers the production database through the automated process.
-#. You restore it in your Production environment a few short hours later and continue working on the
-   newly upgraded database.
-
-.. _db-upgrade/service-level:
-
-Service Level Agreement
------------------------
-
-What is covered by the Enterprise Licence?
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the
-following service at all times.
-
-The upgrade of:
-
-* standard applications
-* Studio customization (as long as the Studio app is still active)
-* customizations done by our consulting and developer services *if* they are covered by a
-  ‘Maintenance of Customisations’ subscription
-
-The Upgrade Service is limited to the technical conversion and adaptation of your database (standard
-modules and data) to make it compatible with the targeted version.
-
-What upgrading does NOT cover
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-* The cleaning of pre-existing data & configuration while upgrading
-* Any new developments and/or upgrade of your own :ref:`custom modules
-  <db-upgrade/faq/custom-modules>`
-* `Training <https://www.odoo.com/learn>`_ on the new version
-
-You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription
-Agreement <upgrade>` page.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/get-started:
-
-Get started
-===========
-
-The upgrade process varies depending on where your database is hosted.
-
-.. _db-upgrade/online:
-
-Online (SaaS)
--------------
-
-If you are hosted Online, please check our :ref:`instruction page for our Online (SaaS) customers
-<upgrade_button>`.
-
-.. _db-upgrade/odoo-sh:
-
-Odoo.sh
--------
-
-If you are Odoo.sh hosted, check our :doc:`specific instructions to be able to upgrade
-<odoo_sh/advanced/upgrade_your_database>`.
-
-.. _db-upgrade/on-premise:
-
-On-Premise
-----------
-
-There are two possibilities:
-
-#. Via the interface of our `website form <https://upgrade.odoo.com>`_
-#. | For technically-advanced users and partners, via the following command line (to be used on the
-     machine where your database is hosted):
-   | ``python <(curl -s beta.upgrade.odoo.com/upgrade) test -d <your db name> -t 14.0``
-
-What does it do?
-~~~~~~~~~~~~~~~~
-
-The above command will dump your database to a file, then send it to the upgrade platform for
-upgrade, displaying you the live logs, then restore the upgraded database back on your server as a
-duplicate test database.
-
-.. _db-upgrade/steps:
-
-Steps
-=====
-
-.. _db-upgrade/steps-test:
-
-The testing phase
------------------
-
-.. _db-upgrade/test-process:
-
-Test process
-~~~~~~~~~~~~
-
-Also referred to as the pre-production phase, the test phase allows you to review an upgraded
-version of your database without affecting your production database in any way.
-
-We suggest that you run the test upgrade process at least once, but you can do it as often as you
-want (one at a time).
-
-Once you receive your upgraded test database, you should check that all data, processes and
-functionality are still correct and working as expected.
-
-If you do find discrepancies, you'll be able to:
-
-* | :ref:`Report your issues <db-upgrade/test-assistance>`
-  | and/or
-* Ask for a new :ref:`test request <db-upgrade/test-db-request>` after the reported issues have
-  been fixed in the upgrade script.
-
-When you do not find any discrepancies, you'll be able to:
-
-* Move on to the upgrade of your :ref:`production database <db-upgrade/production-live>`.
-
-.. _db-upgrade/test-db-request:
-
-Request a test database
-~~~~~~~~~~~~~~~~~~~~~~~
-
-When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose.
-
-.. image:: media/db-upgrade-test-purpose.png
-   :align: center
-   :alt: Selection of the "Testing" purpose in the upgrade form on Odoo
-
-.. _db-upgrade/test-guidance:
-
-Test guidance
-~~~~~~~~~~~~~
-
-Every business and organization has its own operational needs and will have to test its specific
-Odoo instance respectively. However, we recommend you look at `the test scenario
-<https://drive.google.com/open?id=1Lm4JqbsHBirB1wMi14UChoz_YHLjx5ec>`_ we created, a high-level idea
-of what you should test and look out for.
-
-.. todo:: change link "test scenario" once the related doc is published
-
-.. _db-upgrade/test-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **test database**, please contact the Odoo Upgrade
-Support:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type.
-
-   .. image:: media/db-upgrade-test-assistance.png
-      :align: center
-      :alt: Selection of "An issue related to my upgrade" as Ticket Type in the support form on Odoo
-
-   .. warning::
-      If you choose another *Ticket Description* type, the request will be redirected to another
-      team than the upgrade one and will slow down the processing and response time.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-test-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-.. note::
-   * The purpose of the test phase is not to correct existing data or configurations in your
-     database.
-   * |assistance-contact|
-
-.. _db-upgrade/steps-production:
-
-The production launch
----------------------
-
-.. _db-upgrade/production-live:
-
-Production goes live
-~~~~~~~~~~~~~~~~~~~~
-
-The production upgrade request is when you decide to upgrade your current database with all your
-production data (invoices, VAT returns, inventories, current orders) to a new version of your choice.
-
-After your :ref:`tests <db-upgrade/steps-test>` are completed to your satisfaction, submit the
-request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_.
-Select *Production* purpose.
-
-.. image:: media/db-upgrade-production-purpose.png
-   :align: center
-   :alt: Selection of the "Production" purpose in the upgrade form on Odoo
-
-.. danger::
-   Going into production without first testing may lead to:
-
-   - business interruptions (e.g. no longer having the possibility to validate an action)
-   - poor customer experiences (e.g. an eCommerce website that does not work correctly)
-
-.. _db-upgrade/production-assistance:
-
-Assistance
-~~~~~~~~~~
-
-If you encounter issues or problems in the **production database**, please contact the **Odoo
-Support**:
-
-#. Connect to our `Odoo Support page <https://www.odoo.com/help>`_.
-#. Under the *Ticket Description* section, select the appropriate type related to your issue but
-   **do not select** the option *An issue related to my upgrade*.
-
-   .. note::
-      After upgrading to production, the support will be provided by the Support team instead of the
-      Upgrade team.
-
-#. Please provide as much detail as you can. Where applicable, illustrate the current and previous
-   flows with videos and/or screenshots. This will avoid clarifying questions and speed up the
-   resolution process significantly.
-
-   .. image:: media/db-upgrade-production-assistance-details.png
-      :align: center
-      :alt: "Detailed Description" field in the support form on Odoo
-
-   .. warning::
-      If you choose *An issue related to my upgrade* as ticket type, the request will be redirected
-      to another team than the support one and will slow down the processing and response time.
-
-.. _db-upgrade/faq:
-
-FAQ
-===
-
-.. _db-upgrade/faq/why:
-
-Why upgrade?
-------------
-
-* You benefit from the latest features of the :ref:`new major version
-  <db-upgrade/faq/release-notes>` released by Odoo.
-* If you are in an :ref:`unsupported version <db-upgrade/supported-versions>`, you get a new version
-  with support.
-
-.. _db-upgrade/faq/when:
-
-When to upgrade?
-----------------
-
-Whenever you want. You can make your upgrade request as soon as a new version is released on our
-`website form <https://upgrade.odoo.com>`_.
-
-.. _db-upgrade/faq/availability:
-
-Availability of the new version
--------------------------------
-
-Please kindly note that as soon as we announce the release of a new major version (usually at the
-end of year), the Upgrade Service team needs to adapt the upgrade scripts to it, which is why the
-new version is not immediately available for existing databases.
-
-.. _db-upgrade/faq/finalization:
-
-Finalization of the upgrade (:abbr:`ETA (Estimated Time of Arrival)`)
----------------------------------------------------------------------
-
-Unfortunately, it is impossible to give time estimates for every upgrade request. Odoo offers so
-many possibilities (e.g. branding, workflows, customization, etc) that it can get tricky to upgrade,
-and translate to the new structure. If you use multiple apps managing sensitive data (e.g.,
-Accounting, Inventory, etc.), some cases may still require a human intervention, making the process
-slower.
-
-This is especially true during the first months following the release of a new major version, which
-can significantly lengthen the upgrade delay.
-
-In general, the ‘smaller’ the database, the quickest the upgrade. A single-user database that uses
-only CRM will be processed faster than a multi-company, multi-user database that uses Accounting,
-Sales, Purchase, and Manufacturing.
-
-So, in a nutshell, what can impact your upgrade lead time?
-
-* Source & targeted versions
-* Installed apps
-* Volume of data
-* Amount of customization (models, fields, methods, workflows, reports, website, etc.)
-* Installation of new apps or configuration changes after the start of the test phase
-
-Usually, the delays experienced during the first request (waiting time between the time you
-submitted your first request for a test upgrade) can generally give you an idea of the time to wait
-for the production request.
-
-.. _db-upgrade/faq/custom-modules:
-
-Upgrade of the custom modules
------------------------------
-
-As stated in our :doc:`../legal/terms/enterprise`, section :ref:`charges_standard`, this optional
-service is subject to additional fees.
-
-If you have a custom code, you can choose to have it upgraded by our services, by one of our
-`partners <https://www.odoo.com/partners>`_ or you can do it yourself.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/editions-change:
-
-Editions change (from Community to Enterprise)
-----------------------------------------------
-
-An upgrade does not cover a change of `Editions <https://www.odoo.com/page/editions>`_
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/hosting-types-switch:
-
-Switching the hosting types (Self-hosted vs Online vs Odoo.sh)
---------------------------------------------------------------
-
-An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_.
-
-Open the following link to get :doc:`more information about how to change your hosting type
-<db_management/hosting_changes>`.
-
-.. note:: |assistance-contact|
-
-.. _db-upgrade/faq/release-notes:
-
-Release Notes by version
-------------------------
-
-Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new
-features and improvements made in each version.
-
-.. _db-upgrade/assistance:
-
-Assistance
-==========
-
-.. _db-upgrade/contact:
-
-Contact our Upgrade service support
------------------------------------
-
-Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo
-Upgrade Team <mailto:upgrade@odoo.com>`_. We will be very pleased to answer it as soon as possible.
-
-.. _db-upgrade/supported-versions:
-
-Supported versions
-------------------
-
-Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo.
-
-This is a factor to take into consideration before upgrading. If you are on an older version, we
-suggest you to prefer the most recent version to benefit from a longer support (before having to
-upgrade again).
-
-You can get more information about our :doc:`supported versions <../services/support/supported_versions>`.

content/administration/deployment.rst

@@ -1,10 +0,0 @@
-==========
-Deployment
-==========
-
-
-.. toctree::
-
-    deployment/deploy
-    deployment/cdn
-    deployment/email_gateway

content/administration/install.rst

@@ -1,756 +1,14 @@
+:nosearch:
 
-.. _setup/install:
+=======
+Install
+=======
 
-===============
-Installing Odoo
-===============
+.. If you add content on this page, remove the redirect rule 'install -> install/install'
 
-There are multiple ways to install Odoo, or not install it at all, depending
-on the intended use case.
+.. toctree::
 
-This documents attempts to describe most of the installation options.
-
-:ref:`setup/install/online`
-    The easiest way to use Odoo in production or to try it.
-
-:ref:`setup/install/packaged`
-    Suitable for testing Odoo, developing modules and can be used for
-    long-term production use with additional deployment and maintenance work.
-
-:ref:`setup/install/source`
-    Provides greater flexibility:  e.g. allow multiple running Odoo versions on
-    the same system. Good for developing modules, can be used as base for
-    production deployment.
-
-:ref:`setup/install/docker`
-    If you usually use docker_ for development or deployment, an official
-    docker_ base image is available.
-
-
-.. _setup/install/editions:
-
-Editions
-========
-
-There are two different Editions_ of Odoo: the Community and Enterprise versions.
-Using the Enterprise version is possible on our SaaS_ and accessing the code is
-restricted to Enterprise customers and partners. The Community version is freely
-available to anyone.
-
-If you already use the Community version and wish to upgrade to Enterprise, please
-refer to :ref:`setup/enterprise` (except for :ref:`setup/install/source`).
-
-
-.. _setup/install/online:
-
-Online
-======
-
-Demo
-----
-
-To simply get a quick idea of Odoo, demo_ instances are available. They are
-shared instances which only live for a few hours, and can be used to browse
-around and try things out with no commitment.
-
-Demo_ instances require no local installation, just a web browser.
-
-SaaS
-----
-
-Trivial to start with, fully managed and migrated by Odoo S.A., Odoo's SaaS_
-provides private instances and starts out free. It can be used to discover and
-test Odoo and do non-code customizations (i.e. incompatible with custom modules
-or the Odoo Apps Store) without having to install it locally.
-
-Can be used for both testing Odoo and long-term production use.
-
-Like demo_ instances, SaaS_ instances require no local installation, a web
-browser is sufficient.
-
-
-.. _setup/install/packaged:
-
-Packaged installers
-===================
-
-Odoo provides packaged installers for Windows, deb-based distributions
-(Debian, Ubuntu, …) and RPM-based distributions (Fedora, CentOS, RHEL, …) for
-both the Community and Enterprise versions.
-
-These packages automatically set up all dependencies (for the Community version),
-but may be difficult to keep up-to-date.
-
-Official Community packages with all relevant dependency requirements are
-available on our nightly_ server. Both Communtiy and Enterprise packages can
-be downloaded from our download_ page (you must to be logged in as a paying
-customer or partner to download the Enterprise packages).
-
-Windows
--------
-
-#. Download the installer from our nightly_ server (Community only) or the Windows installer from
-   the download_ page (any edition).
-#. Execute the downloaded file.
-
-   .. warning:: | On Windows 8 and later you may see a warning titled "Windows protected your PC".
-                | Click on **More Info** and then on **Run anyway**.
-
-#. Accept the UAC_ prompt.
-#. Go through the various installation steps.
-
-Odoo will automatically be started at the end of the installation.
-
-Linux
------
-
-Debian/Ubuntu
-'''''''''''''
-
-Odoo 14.0 'deb' package currently supports `Debian Buster`_, `Ubuntu 20.04`_ or above.
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-Repository
-^^^^^^^^^^
-
-Odoo S.A. provides a repository that can be used with  Debian and Ubuntu distributions. It can be
-used to install *Odoo Community Edition* by executing the following commands:
-
-.. code-block:: console
-
-    $ wget -O - https://nightly.odoo.com/odoo.key | sudo apt-key add -
-    $ sudo sh -c 'echo "deb http://nightly.odoo.com/14.0/nightly/deb/ ./" >> /etc/apt/sources.list.d/odoo.list'
-    $ sudo apt-get update && sudo apt-get install odoo
-
-You can then use the usual `apt-get upgrade` command to keep your installation up-to-date.
-
-At this moment, there is no nightly repository for the Enterprise Edition.
-
-Deb Package
-^^^^^^^^^^^
-
-Instead of using the repository as described above, the 'deb' packages for both the *Community* and
-*Enterprise* editions can be downloaded from the `official download page <download_>`_.
-
-Next, execute the following commands:
-
-.. code-block:: console
-
-    $ sudo apt-get install <path_to_installation_package>
-
-This will install Odoo as a service, create the necessary PostgreSQL_ user
-and automatically start the server.
-
-.. note:: The recommended `postgresql-server` package will be installed by the Debian Odoo package.
-          The `--no-install-recommends` argument of the `apt-get` tool should be used if you plan
-          to install the Postgresql server on another machine.
-
-Fedora
-''''''
-
-Odoo 14.0 'rpm' package supports Fedora 32.
-
-.. warning:: The Odoo 14.0 rpm package does not support Fedora 33 or above.
-
-Prepare
-^^^^^^^
-Odoo needs a `PostgreSQL`_ server to run properly. Make sure that the `sudo` command is available
-and well configured and, only then, execute the following command in order to install the PostgreSQL
-server:
-
-.. code-block:: console
-
-    $ sudo dnf install -y postgresql-server
-    $ sudo postgresql-setup --initdb --unit postgresql
-    $ sudo systemctl enable postgresql
-    $ sudo systemctl start postgresql
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-Repository
-^^^^^^^^^^
-
-Odoo S.A. provides a repository that can be used with the Fedora distributions.
-It can be used to install *Odoo Community Edition* by executing the following
-commands:
-
-.. code-block:: console
-
-    $ sudo dnf config-manager --add-repo=https://nightly.odoo.com/14.0/nightly/rpm/odoo.repo
-    $ sudo dnf install -y odoo
-    $ sudo systemctl enable odoo
-    $ sudo systemctl start odoo
-
-RPM package
-^^^^^^^^^^^
-
-Instead of using the repository as described above, the 'rpm' packages for both the *Community* and
-*Enterprise* editions can be downloaded from the `official download page <download_>`_.
-
-Once downloaded, the package can be installed using the 'dnf' package manager:
-
-.. code-block:: console
-
-    $ sudo dnf localinstall odoo_14.0.latest.noarch.rpm
-    $ sudo systemctl enable odoo
-    $ sudo systemctl start odoo
-
-
-.. _setup/install/source:
-
-Source Install
-==============
-
-The source "installation" is really about not installing Odoo, and running it directly from source
-instead.
-
-This can be more convenient for module developers as the Odoo source is more easily accessible
-than using packaged installation (for information or to build this documentation and have it
-available offline).
-
-It also makes starting and stopping Odoo more flexible and explicit than the services set up by the
-packaged installations, and allows overriding settings using
-:ref:`command-line parameters <reference/cmdline>` without needing to edit a configuration file.
-
-Finally it provides greater control over the system's set up, and allows to more easily keep
-(and run) multiple versions of Odoo side-by-side.
-
-Windows
--------
-
-Fetch the sources
-'''''''''''''''''
-
-There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
-
-Archive
-^^^^^^^
-
-Community Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <community-repository_>`_
-* `Nightly server <nightly_>`_
-
-Enterprise Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <enterprise-repository_>`_
-
-Git
-^^^
-
-The following requires git_ to be installed on your machine and that you have basic knowledge of
-git commands.
-
-Community Edition:
-
-.. code-block:: doscon
-
-    C:\> git clone https://github.com/odoo/odoo.git
-
-
-Enterprise Edition: (see :ref:`setup/install/editions` to get access)
-
-.. code-block:: doscon
-
-  C:\> git clone https://github.com/odoo/enterprise.git
-
-.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
-          a collection of extra add-ons. The main server code is in the Community version. Running
-          the Enterprise version actually means running the server from the Community version with
-          the addons-path option set to the folder with the Enterprise version. You need to clone
-          both the Community and Enterprise repository to have a working Odoo Enterprise
-          installation.
-
-Prepare
-'''''''
-
-Python
-^^^^^^
-
-Odoo requires Python 3.6 or later to run. Visit `Python's download page <https://www.python.org/downloads/windows/>`_
-to download and install the latest version of Python 3 on your machine.
-
-During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make
-sure that **pip** is checked.
-
-.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
-          versions are not compatible with Odoo.
-
-          .. code-block:: doscon
-
-              C:\> python --version
-
-          Verify also that pip_ is installed for this version.
-
-          .. code-block:: doscon
-
-              C:\> pip --version
-
-PostgreSQL
-^^^^^^^^^^
-
-Odoo uses PostgreSQL as database management system. `Download and install PostgreSQL <https://www.postgresql.org/download/windows/>`_
-(supported version: 10.0 and later).
-
-By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
-create a new PostgreSQL user:
-
-#. Add PostgreSQL's `bin` directory (by default: `C:\\Program Files\\PostgreSQL\\<version>\\bin`) to
-   your `PATH`.
-#. Create a postgres user with a password using the pg admin gui:
-
-   1. Open **pgAdmin**.
-   2. Double-click the server to create a connection.
-   3. Select :menuselection:`Object --> Create --> Login/Group Role`.
-   4. Enter the username in the **Role Name** field (e.g. `odoo`).
-   5. Open the **Definition** tab and enter the password (e.g. ``odoo``), then click **Save**.
-   6. Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to
-      `Yes`.
-
-Dependencies
-^^^^^^^^^^^^
-
-Before installing the dependencies, you must download and install the
-`Build Tools for Visual Studio <https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019>`_.
-When prompted, select **C++ build tools** in the **Workloads** tab and install them.
-
-Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-community directory.
-
-.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
-         or with your system. You can use virtualenv_ to create isolated Python environments.
-
-Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
-on the requirements file in a terminal **with Administrator privileges**:
-
-.. code-block:: doscon
-
-    C:\> cd \CommunityPath
-    C:\> pip install setuptools wheel
-    C:\> pip install -r requirements.txt
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
-needed:
-
-#. Download and install `nodejs <https://nodejs.org/en/download/>`_.
-#. Install `rtlcss`:
-
-   .. code-block:: doscon
-
-       C:\> npm install -g rtlcss
-
-#. Edit the System Environment's variable `PATH` to add the folder where `rtlcss.cmd` is located
-   (typically: `C:\\Users\\<user>\\AppData\\Roaming\\npm\\`).
-
-Running Odoo
-''''''''''''
-
-Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
-command-line interface of the server. It is located at the root of the Odoo Community directory.
-
-To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
-:ref:`configuration file <reference/cmdline/config>`.
-
-.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
-         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
-         addons to be loaded correctly.
-
-Common necessary configurations are:
-
-* PostgreSQL user and password.
-* Custom addon paths beyond the defaults, to load your own modules.
-
-A typical way to run the server would be:
-
-.. code-block:: doscon
-
-    C:\> cd CommunityPath/
-    C:\> python odoo-bin -r dbuser -w dbpassword --addons-path=addons -d mydb
-
-Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the
-PostgreSQL login, `dbpassword` is the PostgreSQL password
-and `mydb` is the default database to serve on `localhost:8069`. You can add other
-directory paths separated by a comma to ``addons`` at the end of the addons-path option.
-
-Linux
------
-
-Fetch the sources
-'''''''''''''''''
-
-There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
-
-Archive
-^^^^^^^
-
-Community Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <community-repository_>`_
-* `Nightly server <nightly_>`_
-
-Enterprise Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <enterprise-repository_>`_
-
-Git
-^^^
-
-The following requires git_ to be installed on your machine and that you have basic knowledge of
-git commands.
-
-Community Edition:
-
-.. code-block:: console
-
-    $ git clone https://github.com/odoo/odoo.git
-
-
-Enterprise Edition: (see :ref:`setup/install/editions` to get access)
-
-.. code-block:: console
-
-  $ git clone https://github.com/odoo/enterprise.git
-
-.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
-          a collection of extra add-ons. The main server code is in the Community version. Running
-          the Enterprise version actually means running the server from the Community version with
-          the addons-path option set to the folder with the Enterprise version. You need to clone
-          both the Community and Enterprise repository to have a working Odoo Enterprise
-          installation.
-
-Prepare
-'''''''
-
-Python
-^^^^^^
-
-Odoo requires Python 3.6 or later to run. Use your package manager to download and install Python 3
-on your machine if it is not already done.
-
-.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
-          versions are not compatible with Odoo.
-
-          .. code-block:: console
-
-              $ python3 --version
-
-          Verify also that pip_ is installed for this version.
-
-          .. code-block:: console
-
-              $ pip3 --version
-
-PostgreSQL
-^^^^^^^^^^
-
-Odoo uses PostgreSQL as database management system. Use your package manager to download and install
-PostgreSQL (supported version: 10.0 and later).
-
-On Debian/Unbuntu, it can be achieved by executing the following:
-
-.. code-block:: console
-
-    $ sudo apt install postgresql postgresql-client
-
-By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
-create a new PostgreSQL user:
-
-.. code-block:: console
-
-  $ sudo -u postgres createuser -s $USER
-  $ createdb $USER
-
-.. note:: Because your PostgreSQL user has the same name as your Unix login, you will be able to
-          connect to the database without password.
-
-Dependencies
-^^^^^^^^^^^^
-
-For libraries using native code, it is necessary to install development tools and native
-dependencies before the Python dependencies of Odoo. They are available in `-dev` or `-devel`
-packages for Python, PostgreSQL, libxml2, libxslt1, libevent, libsasl2 and libldap2.
-
-On Debian/Unbuntu, the following command should install all the required libraries:
-
-.. code-block:: console
-
-    $ sudo apt install python3-dev libxml2-dev libxslt1-dev libldap2-dev libsasl2-dev \
-        libtiff5-dev libjpeg8-dev libopenjp2-7-dev zlib1g-dev libfreetype6-dev \
-        liblcms2-dev libwebp-dev libharfbuzz-dev libfribidi-dev libxcb1-dev libpq-dev
-
-Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-community directory.
-
-.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
-         or with your system. You can use virtualenv_ to create isolated Python environments.
-
-Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
-on the requirements file:
-
-.. code-block:: console
-
-    $ cd /CommunityPath
-    $ pip3 install setuptools wheel
-    $ pip3 install -r requirements.txt
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
-needed:
-
-#. Download and install **nodejs** and **npm** with your package manager.
-#. Install `rtlcss`:
-
-   .. code-block:: console
-
-       $ sudo npm install -g rtlcss
-
-Running Odoo
-''''''''''''
-
-Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
-command-line interface of the server. It is located at the root of the Odoo Community directory.
-
-To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
-:ref:`configuration file <reference/cmdline/config>`.
-
-.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
-         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
-         addons to be loaded correctly.
-
-Common necessary configurations are:
-
-* PostgreSQL user and password. Odoo has no defaults beyond
-  `psycopg2's defaults <http://initd.org/psycopg/docs/module.html>`_: connects over a UNIX socket on
-  port `5432` with the current user and no password.
-* Custom addon paths beyond the defaults, to load your own modules.
-
-A typical way to run the server would be:
-
-.. code-block:: console
-
-    $ cd /CommunityPath
-    $ python3 odoo-bin --addons-path=addons -d mydb
-
-Where `CommunityPath` is the path of the Odoo Community installation
-and `mydb` is the default database to serve on `localhost:8069`. You can add other
-directory paths separated by a comma to ``addons`` at the end of the addons-path option.
-
-Mac OS
-------
-
-Fetch the sources
-'''''''''''''''''
-
-There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
-
-Archive
-^^^^^^^
-
-Community Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <community-repository_>`_
-* `Nightly server <nightly_>`_
-
-Enterprise Edition:
-
-* `Official download page <download_>`_
-* `GitHub repository <enterprise-repository_>`_
-
-Git
-^^^
-
-The following requires git_ to be installed on your machine and that you have basic knowledge of
-git commands.
-
-Community Edition:
-
-.. code-block:: console
-
-    $ git clone https://github.com/odoo/odoo.git
-
-
-Enterprise Edition: (see :ref:`setup/install/editions` to get access)
-
-.. code-block:: console
-
-  $ git clone https://github.com/odoo/enterprise.git
-
-.. note:: **The Enterprise git repository does not contain the full Odoo source code**. It is only
-          a collection of extra add-ons. The main server code is in the Community version. Running
-          the Enterprise version actually means running the server from the Community version with
-          the addons-path option set to the folder with the Enterprise version. You need to clone
-          both the Community and Enterprise repository to have a working Odoo Enterprise
-          installation.
-
-Prepare
-'''''''
-
-Python
-^^^^^^
-
-Odoo requires Python 3.6 or later to run. Use your preferred package manager (homebrew_, macports_)
-to download and install Python 3 on your machine if it is not already done.
-
-.. note:: If Python 3 is already installed, make sure that the version is 3.6 or above, as previous
-          versions are not compatible with Odoo.
-
-          .. code-block:: console
-
-              $ python3 --version
-
-          Verify also that pip_ is installed for this version.
-
-          .. code-block:: console
-
-              $ pip3 --version
-
-PostgreSQL
-^^^^^^^^^^
-
-Odoo uses PostgreSQL as database management system. Use `postgres.app <https://postgresapp.com>`_
-to download and install PostgreSQL (supported version: 10.0 and later).
-
-By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to
-create a new PostgreSQL user:
-
-.. code-block:: console
-
-  $ sudo -u postgres createuser -s $USER
-  $ createdb $USER
-
-.. note:: Because your PostgreSQL user has the same name as your Unix login, you will be able to
-          connect to the database without password.
-
-Dependencies
-^^^^^^^^^^^^
-
-Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
-community directory.
-
-.. tip:: It can be preferable to not mix python modules packages between different instances of Odoo
-         or with your system. You can use virtualenv_ to create isolated Python environments.
-
-Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip**
-on the requirements file:
-
-.. code-block:: console
-
-   $ cd /CommunityPath
-   $ pip3 install setuptools wheel
-   $ pip3 install -r requirements.txt
-
-.. warning:: Non-Python dependencies need to be installed with a package manager:
-
-             #. Download and install the **Command Line Tools**:
-
-                .. code-block:: console
-
-                   $ xcode-select --install
-
-             #. Download and install the package manager of your choice (homebrew_, macports_).
-             #. Install non-python dependencies.
-
-.. warning:: `wkhtmltopdf` is not installed through **pip** and must be installed manually in
-             version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and
-             footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more
-             details on the various versions.
-
-For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
-needed:
-
-#. Download and install **nodejs** with your preferred package manager (homebrew_, macports_).
-#. Install `rtlcss`:
-
-   .. code-block:: console
-
-       $ sudo npm install -g rtlcss
-
-Running Odoo
-''''''''''''
-
-Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
-command-line interface of the server. It is located at the root of the Odoo Community directory.
-
-To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a
-:ref:`configuration file <reference/cmdline/config>`.
-
-.. tip:: For the Enterprise edition, you must add the path to the `enterprise` addons to the
-         `addons-path` argument. Note that it must come before the other paths in `addons-path` for
-         addons to be loaded correctly.
-
-Common necessary configurations are:
-
-* PostgreSQL user and password. Odoo has no defaults beyond
-  `psycopg2's defaults <http://initd.org/psycopg/docs/module.html>`_: connects over a UNIX socket on
-  port `5432` with the current user and no password.
-* Custom addon paths beyond the defaults, to load your own modules.
-
-A typical way to run the server would be:
-
-.. code-block:: console
-
-    $ cd /CommunityPath
-    $ python3 odoo-bin --addons-path=addons -d mydb
-
-Where `CommunityPath` is the path of the Odoo Community installation
-and `mydb` is the default database to serve on `localhost:8069`. You can add other
-directory paths separated by a comma to ``addons`` at the end of the addons-path option.
-
-
-.. _setup/install/docker:
-
-Docker
-======
-
-The full documentation on how to use Odoo with Docker can be found on the
-official Odoo `docker image <https://registry.hub.docker.com/_/odoo/>`_ page.
-
-.. _Debian Buster: https://www.debian.org/releases/buster/
-.. _demo: https://demo.odoo.com
-.. _docker: https://www.docker.com
-.. _download: https://www.odoo.com/page/download
-.. _Ubuntu 20.04: http://releases.ubuntu.com/20.04/
-.. _EPEL: https://fedoraproject.org/wiki/EPEL
-.. _PostgreSQL: http://www.postgresql.org
-.. _the official installer:
-.. _install pip:
-    https://pip.pypa.io/en/latest/installing.html#install-pip
-.. _Quilt: http://en.wikipedia.org/wiki/Quilt_(software)
-.. _saas: https://www.odoo.com/page/start
-.. _the wkhtmltopdf download page: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.5
-.. _UAC: http://en.wikipedia.org/wiki/User_Account_Control
-.. _wkhtmltopdf: http://wkhtmltopdf.org
-.. _pip: https://pip.pypa.io
-.. _macports: https://www.macports.org
-.. _homebrew: http://brew.sh
-.. _wheels: https://wheel.readthedocs.org/en/latest/
-.. _virtualenv: https://pypi.python.org/pypi/virtualenv
-.. _virtualenvwrapper: https://virtualenvwrapper.readthedocs.io/en/latest/
-.. _pywin32: http://sourceforge.net/projects/pywin32/files/pywin32/
-.. _community-repository: https://github.com/odoo/odoo
-.. _enterprise-repository: https://github.com/odoo/enterprise
-.. _git: https://git-scm.com/
-.. _Editions: https://www.odoo.com/pricing#pricing_table_features
-.. _nightly: https://nightly.odoo.com/
-.. _extra: https://nightly.odoo.com/extra/
+    install/install
+    install/deploy
+    install/cdn
+    install/email_gateway

content/administration/install/cdn.rst

@@ -1,7 +1,6 @@
-
-========================================
-Deploying with Content Delivery Networks
-========================================
+===========================================
+Setting up a Content Delivery Network (CDN)
+===========================================
 
 .. _reference/cdn/keycdn:
 

content/administration/install/deploy.rst

@@ -1,15 +1,13 @@
-
-==============
-Deploying Odoo
-==============
+====================
+System configuration
+====================
 
 This document describes basic steps to set up Odoo in production or on an
 internet-facing server. It follows :ref:`installation <setup/install>`, and is
 not generally necessary for a development systems that is not exposed on the
 internet.
 
-.. warning:: If you are setting up a public server, be sure to check our :ref:`security` recommandations!
-
+.. warning:: If you are setting up a public server, be sure to check our :ref:`security` recommendations!
 
 .. _db_filter:
 
@@ -65,15 +63,15 @@ in ``/etc/odoo.conf`` set:
   dbfilter = ^%d$
 
 .. note::
+
   Setting a proper :option:`--db-filter <odoo-bin --db-filter>` is an important part
   of securing your deployment.
   Once it is correctly working and only matching a single database per hostname, it
   is strongly recommended to block access to the database manager screens,
-  and to use the ``--no-database-list`` startup paramater to prevent listing
+  and to use the ``--no-database-list`` startup parameter to prevent listing
   your databases, and to block access to the database management screens.
   See also security_.
 
-
 PostgreSQL
 ==========
 
@@ -171,7 +169,7 @@ SSL Between Odoo and PostgreSQL
 
 Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL.
 in Odoo the db_sslmode control the ssl security of the connection
-with value choosed out of 'disable', 'allow', 'prefer', 'require', 'verify-ca'
+with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca'
 or 'verify-full'
 
 `PostgreSQL Doc <https://www.postgresql.org/docs/current/static/libpq-ssl.html>`_
@@ -197,7 +195,6 @@ be better monitored and resource-restricted.
 
 .. warning:: multiprocessing mode currently isn't available on Windows
 
-
 Worker number calculation
 -------------------------
 
@@ -230,16 +227,14 @@ like nginx or apache. When doing so, you'll need to forward some more http Heade
 to Odoo, and activate the proxy_mode in Odoo configuration to have Odoo read those
 headers.
 
-
-
 Configuration sample
 --------------------
 
 * Server with 4 CPU, 8 Thread
 * 60 concurrent users
 
-* 60 users / 6 = 10 <- theorical number of worker needed
-* (4 * 2) + 1 = 9 <- theorical maximal number of worker
+* 60 users / 6 = 10 <- theoretical number of worker needed
+* (4 * 2) + 1 = 9 <- theoretical maximal number of worker
 * We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 .
 * RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo
 
@@ -290,59 +285,58 @@ in ``/etc/nginx/sites-enabled/odoo.conf`` set:
 
   #odoo server
   upstream odoo {
-   server 127.0.0.1:8069;
+    server 127.0.0.1:8069;
   }
   upstream odoochat {
-   server 127.0.0.1:8072;
+    server 127.0.0.1:8072;
   }
 
   # http -> https
   server {
-     listen 80;
-     server_name odoo.mycompany.com;
-     rewrite ^(.*) https://$host$1 permanent;
+    listen 80;
+    server_name odoo.mycompany.com;
+    rewrite ^(.*) https://$host$1 permanent;
   }
 
   server {
-   listen 443;
-   server_name odoo.mycompany.com;
-   proxy_read_timeout 720s;
-   proxy_connect_timeout 720s;
-   proxy_send_timeout 720s;
+    listen 443 ssl;
+    server_name odoo.mycompany.com;
+    proxy_read_timeout 720s;
+    proxy_connect_timeout 720s;
+    proxy_send_timeout 720s;
 
-   # Add Headers for odoo proxy mode
-   proxy_set_header X-Forwarded-Host $host;
-   proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
-   proxy_set_header X-Forwarded-Proto $scheme;
-   proxy_set_header X-Real-IP $remote_addr;
+    # Add Headers for odoo proxy mode
+    proxy_set_header X-Forwarded-Host $host;
+    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+    proxy_set_header X-Forwarded-Proto $scheme;
+    proxy_set_header X-Real-IP $remote_addr;
 
-   # SSL parameters
-   ssl on;
-   ssl_certificate /etc/ssl/nginx/server.crt;
-   ssl_certificate_key /etc/ssl/nginx/server.key;
-   ssl_session_timeout 30m;
-   ssl_protocols TLSv1.2;
-   ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
-   ssl_prefer_server_ciphers off;
+    # SSL parameters
+    ssl_certificate /etc/ssl/nginx/server.crt;
+    ssl_certificate_key /etc/ssl/nginx/server.key;
+    ssl_session_timeout 30m;
+    ssl_protocols TLSv1.2;
+    ssl_ciphers ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384;
+    ssl_prefer_server_ciphers off;
 
-   # log
-   access_log /var/log/nginx/odoo.access.log;
-   error_log /var/log/nginx/odoo.error.log;
+    # log
+    access_log /var/log/nginx/odoo.access.log;
+    error_log /var/log/nginx/odoo.error.log;
 
-   # Redirect longpoll requests to odoo longpolling port
-   location /longpolling {
-   proxy_pass http://odoochat;
-   }
+    # Redirect longpoll requests to odoo longpolling port
+    location /longpolling {
+      proxy_pass http://odoochat;
+    }
 
-   # Redirect requests to odoo backend server
-   location / {
-     proxy_redirect off;
-     proxy_pass http://odoo;
-   }
+    # Redirect requests to odoo backend server
+    location / {
+      proxy_redirect off;
+      proxy_pass http://odoo;
+    }
 
-   # common gzip
-   gzip_types text/css text/scss text/plain text/xml application/xml application/json application/javascript;
-   gzip on;
+    # common gzip
+    gzip_types text/css text/scss text/plain text/xml application/xml application/json application/javascript;
+    gzip on;
   }
 
 Odoo as a WSGI Application
@@ -386,7 +380,7 @@ notifications.
 
 The solutions to support livechat/motifications in a WSGI application are:
 
-* Deploy a threaded version of Odoo (instread of a process-based preforking
+* Deploy a threaded version of Odoo (instead of a process-based preforking
   one) and redirect only requests to URLs starting with ``/longpolling/`` to
   that Odoo, this is the simplest and the longpolling URL can double up as
   the cron instance.
@@ -394,20 +388,112 @@ The solutions to support livechat/motifications in a WSGI application are:
   with ``/longpolling/`` to
   :option:`the longpolling port <odoo-bin --longpolling-port>`.
 
-Serving Static Files
-====================
+.. _deploy/streaming:
 
-For development convenience, Odoo directly serves all static files in its
-modules. This may not be ideal when it comes to performances, and static
-files should generally be served by a static HTTP server.
+Serving static files and attachments
+====================================
 
-Odoo static files live in each module's ``static/`` folder, so static files
-can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`,
-and looking up the right module (and file) in the various addons paths.
+For development convenience, Odoo directly serves all static files and attachments in its modules.
+This may not be ideal when it comes to performances, and static files should generally be served by
+a static HTTP server.
+
+Serving static files
+--------------------
+
+Odoo static files are located in each module's :file:`static/` folder, so static files can be served 
+by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module
+(and file) in the various addons paths.
+
+.. example::
+   Say Odoo has been installed via the **debian packages** for Community and Enterprise, the addons
+   paths is :file:`/usr/lib/python3/dist-packages/odoo/addons`. Using the above NGINX (https)
+   configuration, the following location block should be added to serve static files via NGINX.
+   
+   .. code-block:: nginx
+   
+       location @odoo {
+           # copy-paste the content of the / location block
+       }
+   
+       # Serve static files right away
+       location ~ ^/[^/]+/static/.+$ {
+           root /usr/lib/python3/dist-packages/odoo/addons;
+           try_files $uri @odoo;
+           expires 24h;
+       }
+
+.. example::
+   Say Odoo has been installed via the **source**, and the two git repositories for Community and
+   Enterprise has been cloned in :file:`/opt/odoo` and :file:`/opt/odoo-enterprise` respectively. 
+   The addons paths is ``/opt/odoo/odoo,/opt/odoo/addons,/opt/odoo-enterprise``. Using the above
+   NGINX (https) configuragion, the following location block should be added to serve static files
+   via NGINX.
+
+   .. code-block:: nginx
+   
+       location @odoo {
+           # copy-paste the content of the / location block
+       }
+   
+       # Serve static files right away
+       location ~ ^/[^/]+/static/.+$ {
+           try_files /static-base$uri /static-addons$uri /static-enterprise$uri @odoo$uri;
+           expires 24h;
+       }
+   
+       location /static-base {
+           internal;
+           alias /opt/odoo/odoo/addons;
+       }
+   
+       location /static-addons {
+           internal;
+           alias /opt/odoo/addons;
+       }
+   
+       location /static-enterprise {
+           internal;
+           alias /opt/odoo-enterprise;
+       }
+
+.. warning::
+   The actual NGINX configuration you need is highly dependent on your own installation. The two
+   above snippets only highlight two possible configurations and may not be used as-is.
+
+Serving attachments
+-------------------
+
+Attachments are files stored in the filestore which access is regulated by Odoo. They cannot be
+directly accessed via a static web server as accessing them requires multiple lookups in the
+database to determine where the files are stored and whether the current user can access them or
+not.
+
+Nevertheless, once the file has been located and the access rights verified by Odoo, it is a good
+idea to serve the file using the static web server instead of Odoo. For Odoo to delegate serving
+files to the static web server, the `X-Sendfile <https://tn123.org/mod_xsendfile/>`_ (apache) or
+`X-Accel <https://www.nginx.com/resources/wiki/start/topics/examples/x-accel/>`_ (nginx) extensions
+must be enabled and configured on the static web server. Once it is set up, start Odoo with the
+:option:`--x-sendfile <odoo-bin --x-sendfile>` CLI flag (this unique flag is used for both
+X-Sendfile and X-Accel).
+
+
+.. note::
+   - The X-Sendfile extension for apache (and compatible web servers) does not require any
+     supplementary configuration.
+   - The X-Accel extension for NGINX **does** require the following additionnal configuration:
+
+     .. code-block:: nginx
+ 
+         location /web/filestore {
+             internal;
+             alias /path/to/odoo/data-dir/filestore;
+         }
+
+     In case you don't know what is the path to your filestore, start Odoo with the
+     :option:`--x-sendfile <odoo-bin --x-sendfile>` option and navigate to the ``/web/filestore`` URL
+     directly via Odoo (don't navigate to the URL via NGINX). This logs a warnings, the message
+     contains the configuration you need.
 
-.. todo:: test whether it would be interesting to serve filestored attachments
-          via this, and how (e.g. possibility of mapping ir.attachment id to
-          filestore hash in the database?)
 
 .. _security:
 
@@ -559,9 +645,6 @@ Here is what it could look like for blocking the IP for 15 minutes when
     findtime = 60  ; within 1 min  /!\ Should be adjusted with the TZ offset
     logpath = /var/log/odoo.log  ;  set the actual odoo log path here
 
-
-
-
 .. _db_manager_security:
 
 Database Manager Security
@@ -624,12 +707,10 @@ Here are the supported browsers:
 .. warning:: Please make sure your browser is up-to-date and still supported by
     its publisher before filing a bug report.
 
-
 .. note::
 
     Since Odoo 13.0, ES6 is supported.  Therefore, IE support is dropped.
 
-
 .. [#different-machines]
     to have multiple Odoo installations use the same PostgreSQL database,
     or to provide more computing resources to both software.

content/administration/install/email_gateway.rst

@@ -1,7 +1,6 @@
-
-==================
-Odoo email gateway
-==================
+=============
+Email gateway
+=============
 
 The Odoo mail gateway allows you to inject directly all the received emails in Odoo.
 
@@ -45,4 +44,4 @@ For Exim
 
 .. tip::
    If you don't have access/manage your email server, use :ref:`inbound messages
-   <discuss/email_servers/inbound_messages>`.
+   <email_communication/inbound_messages>`.

content/administration/install/install.rst

@@ -0,0 +1,708 @@
+
+.. _setup/install:
+
+===============
+Installing Odoo
+===============
+
+There are multiple ways to install Odoo, or not install it at all, depending
+on the intended use case.
+
+This documents attempts to describe most of the installation options.
+
+:ref:`setup/install/online`
+    The easiest way to use Odoo in production or to try it.
+
+:ref:`setup/install/packaged`
+    Suitable for testing Odoo, developing modules and can be used for
+    long-term production use with additional deployment and maintenance work.
+
+:ref:`setup/install/source`
+    Provides greater flexibility:  e.g. allow multiple running Odoo versions on
+    the same system. Good for developing modules, can be used as base for
+    production deployment.
+
+:ref:`setup/install/docker`
+    If you usually use docker_ for development or deployment, an official
+    docker_ base image is available.
+
+
+.. _setup/install/editions:
+
+Editions
+========
+
+There are two different Editions_ of Odoo: the Community and Enterprise versions.
+Using the Enterprise version is possible on our SaaS_ and accessing the code is
+restricted to Enterprise customers and partners. The Community version is freely
+available to anyone.
+
+If you already use the Community version and wish to upgrade to Enterprise, please
+refer to :ref:`setup/enterprise` (except for :ref:`setup/install/source`).
+
+
+.. _setup/install/online:
+
+Online
+======
+
+Demo
+----
+
+To simply get a quick idea of Odoo, demo_ instances are available. They are
+shared instances which only live for a few hours, and can be used to browse
+around and try things out with no commitment.
+
+Demo_ instances require no local installation, just a web browser.
+
+SaaS
+----
+
+Trivial to start with, fully managed and migrated by Odoo S.A., Odoo's SaaS_
+provides private instances and starts out free. It can be used to discover and
+test Odoo and do non-code customizations (i.e. incompatible with custom modules
+or the Odoo Apps Store) without having to install it locally.
+
+Can be used for both testing Odoo and long-term production use.
+
+Like demo_ instances, SaaS_ instances require no local installation, a web
+browser is sufficient.
+
+
+.. _setup/install/packaged:
+
+Packaged installers
+===================
+
+Odoo provides packaged installers for Windows, deb-based distributions
+(Debian, Ubuntu, …) and RPM-based distributions (Fedora, CentOS, RHEL, …) for
+both the Community and Enterprise versions.
+
+These packages automatically set up all dependencies (for the Community version),
+but may be difficult to keep up-to-date.
+
+Official Community packages with all relevant dependency requirements are
+available on our nightly_ server. Both Community and Enterprise packages can
+be downloaded from our download_ page (you must to be logged in as a paying
+customer or partner to download the Enterprise packages).
+
+Windows
+-------
+
+#. Download the installer from our nightly_ server (Community only) or the Windows installer from
+   the download_ page (any edition).
+#. Execute the downloaded file.
+
+   .. warning::
+      | On Windows 8 and later you may see a warning titled "Windows protected your PC".
+      | Click on **More Info** and then on **Run anyway**.
+
+#. Accept the UAC_ prompt.
+#. Go through the various installation steps.
+
+Odoo will automatically be started at the end of the installation.
+
+Linux
+-----
+
+Prepare
+~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Debian/Ubuntu
+
+      Odoo needs a `PostgreSQL`_ server to run properly. The default configuration for
+      the Odoo 'deb' package is to use the PostgreSQL server on the same host as your
+      Odoo instance. Execute the following command in order to install the PostgreSQL server:
+
+      .. code-block:: console
+
+         $ sudo apt install postgresql -y
+
+   .. group-tab:: Fedora
+
+      Odoo needs a `PostgreSQL`_ server to run properly. Make sure that the `sudo` command is
+      available and well configured and, only then, execute the following command in order to
+      install the PostgreSQL server:
+
+      .. code-block:: console
+
+         $ sudo dnf install -y postgresql-server
+         $ sudo postgresql-setup --initdb --unit postgresql
+         $ sudo systemctl enable postgresql
+         $ sudo systemctl start postgresql
+
+.. warning::
+   `wkhtmltopdf` is not installed through **pip** and must be installed manually in version `0.12.5
+   <the wkhtmltopdf download page_>`_ for it to support headers and footers. See our `wiki
+   <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the various versions.
+
+Repository
+~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Debian/Ubuntu
+
+      Odoo S.A. provides a repository that can be used with Debian and Ubuntu distributions. It can
+      be used to install *Odoo Community Edition* by executing the following commands **as root**:
+
+      .. code-block:: console
+
+          # wget -O - https://nightly.odoo.com/odoo.key | apt-key add -
+          # echo "deb http://nightly.odoo.com/15.0/nightly/deb/ ./" >> /etc/apt/sources.list.d/odoo.list
+          # apt-get update && apt-get install odoo
+
+      You can then use the usual `apt-get upgrade` command to keep your installation up-to-date.
+
+   .. group-tab:: Fedora
+
+      Odoo S.A. provides a repository that can be used with the Fedora distributions. It can be used
+      to install *Odoo Community Edition* by executing the following commands:
+
+      .. code-block:: console
+
+         $ sudo dnf config-manager --add-repo=https://nightly.odoo.com/15.0/nightly/rpm/odoo.repo
+         $ sudo dnf install -y odoo
+         $ sudo systemctl enable odoo
+         $ sudo systemctl start odoo
+
+.. note::
+   At this moment, there is no nightly repository for the Enterprise Edition.
+
+Distribution package
+~~~~~~~~~~~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Debian/Ubuntu
+
+      Instead of using the repository as described above, the 'deb' packages for both the
+      *Community* and *Enterprise* editions can be downloaded from the `official download page
+      <download_>`_.
+
+      .. note::
+         Odoo 15.0 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu 20.04 (Focal)`_
+         or above.
+
+      Next, execute the following commands **as root**:
+
+      .. code-block:: console
+
+         # dpkg -i <path_to_installation_package> # this probably fails with missing dependencies
+         # apt-get install -f # should install the missing dependencies
+         # dpkg -i <path_to_installation_package>
+
+      This will install Odoo as a service, create the necessary PostgreSQL_ user
+      and automatically start the server.
+
+      .. warning::
+         - The `python3-xlwt` Debian package does not exists in Debian Buster nor Ubuntu 18.04. This
+           python module is needed to export into xls format.
+
+           If you need the feature, you can install it manually with:
+
+           .. code-block:: console
+
+              $ sudo pip3 install xlwt
+
+         - The `num2words` python package does not exists in Debian Buster nor Ubuntu 18.04. Textual
+           amounts will not be rendered by Odoo and this could cause problems with the `l10n_mx_edi`
+           module.
+
+           If you need this feature, you can install manually with:
+
+           .. code-block:: console
+
+              $ sudo pip3 install num2words
+
+   .. group-tab:: Fedora
+
+      Instead of using the repository as described above, the 'rpm' packages for both the
+      *Community* and *Enterprise* editions can be downloaded from the `official download page
+      <download_>`_.
+
+      .. note::
+         Odoo 15.0 'rpm' package supports Fedora 34.
+
+      Once downloaded, the package can be installed using the 'dnf' package manager:
+
+      .. code-block:: console
+
+         $ sudo dnf localinstall odoo_15.0.latest.noarch.rpm
+         $ sudo systemctl enable odoo
+         $ sudo systemctl start odoo
+
+.. _setup/install/source:
+
+Source install
+==============
+
+The source "installation" is really about not installing Odoo, and running it directly from source
+instead.
+
+This can be more convenient for module developers as the Odoo source is more easily accessible
+than using packaged installation (for information or to build this documentation and have it
+available offline).
+
+It also makes starting and stopping Odoo more flexible and explicit than the services set up by the
+packaged installations, and allows overriding settings using
+:ref:`command-line parameters <reference/cmdline>` without needing to edit a configuration file.
+
+Finally it provides greater control over the system's set up, and allows to more easily keep
+(and run) multiple versions of Odoo side-by-side.
+
+Fetch the sources
+-----------------
+
+There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**.
+
+Archive
+~~~~~~~
+
+Community Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <community-repository_>`_
+* `Nightly server <nightly_>`_
+
+Enterprise Edition:
+
+* `Official download page <download_>`_
+* `GitHub repository <enterprise-repository_>`_
+
+Git
+~~~
+
+The following requires `git <https://git-scm.com/>`_ to be installed on your machine and that you
+have basic knowledge of git commands.
+
+Community Edition:
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      .. code-block:: doscon
+
+          C:\> git clone https://github.com/odoo/odoo.git
+
+   .. group-tab:: Linux
+
+      .. code-block:: console
+
+          $ git clone https://github.com/odoo/odoo.git
+
+   .. group-tab:: Mac OS
+
+      .. code-block:: console
+
+          $ git clone https://github.com/odoo/odoo.git
+
+Enterprise Edition: (see :ref:`setup/install/editions` to get access)
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      .. code-block:: doscon
+
+        C:\> git clone https://github.com/odoo/enterprise.git
+
+   .. group-tab:: Linux
+
+      .. code-block:: console
+
+        $ git clone https://github.com/odoo/enterprise.git
+
+   .. group-tab:: Mac OS
+
+      .. code-block:: console
+
+        $ git clone https://github.com/odoo/enterprise.git
+
+.. note::
+   **The Enterprise git repository does not contain the full Odoo source code**. It is only a
+   collection of extra add-ons. The main server code is in the Community version. Running the
+   Enterprise version actually means running the server from the Community version with the
+   addons-path option set to the folder with the Enterprise version. You need to clone both the
+   Community and Enterprise repository to have a working Odoo Enterprise installation.
+
+Prepare
+-------
+
+Python
+~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      Odoo requires Python 3.7 or later to run. Visit `Python's download page <https://www.python.org/downloads/windows/>`_
+      to download and install the latest version of Python 3 on your machine.
+
+      During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make
+      sure that **pip** is checked.
+
+      .. note::
+         If Python 3 is already installed, make sure that the version is 3.7 or above, as previous
+         versions are not compatible with Odoo.
+
+         .. code-block:: doscon
+
+            C:\> python --version
+
+         Verify also that pip_ is installed for this version.
+
+         .. code-block:: doscon
+
+            C:\> pip --version
+
+   .. group-tab:: Linux
+
+      Odoo requires Python 3.7 or later to run. Use your package manager to download and install Python 3
+      on your machine if it is not already done.
+
+      .. note::
+         If Python 3 is already installed, make sure that the version is 3.7 or above, as previous
+         versions are not compatible with Odoo.
+
+         .. code-block:: console
+
+            $ python3 --version
+
+         Verify also that pip_ is installed for this version.
+
+         .. code-block:: console
+
+            $ pip3 --version
+
+   .. group-tab:: Mac OS
+
+      Odoo requires Python 3.7 or later to run. Use your preferred package manager (homebrew_, macports_)
+      to download and install Python 3 on your machine if it is not already done.
+
+      .. note::
+         If Python 3 is already installed, make sure that the version is 3.7 or above, as previous
+         versions are not compatible with Odoo.
+
+         .. code-block:: console
+
+            $ python3 --version
+
+         Verify also that pip_ is installed for this version.
+
+         .. code-block:: console
+
+            $ pip3 --version
+
+PostgreSQL
+~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      Odoo uses PostgreSQL as database management system. `Download and install PostgreSQL
+      <https://www.postgresql.org/download/windows/>`_ (supported version: 10.0 and later).
+
+      By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need
+      to create a new PostgreSQL user:
+
+      #. Add PostgreSQL's `bin` directory (by default:
+         :file:`C:\\Program Files\\PostgreSQL\\<version>\\bin`) to your `PATH`.
+      #. Create a postgres user with a password using the pg admin gui:
+
+         1. Open **pgAdmin**.
+         2. Double-click the server to create a connection.
+         3. Select :menuselection:`Object --> Create --> Login/Group Role`.
+         4. Enter the username in the **Role Name** field (e.g. `odoo`).
+         5. Open the **Definition** tab and enter the password (e.g. `odoo`), then click **Save**.
+         6. Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?**
+            to `Yes`.
+
+   .. group-tab:: Linux
+
+      Odoo uses PostgreSQL as database management system. Use your package manager to download and
+      install PostgreSQL (supported version: 10.0 and later).
+
+      It can be achieved by executing the following:
+
+      .. code-block:: console
+
+          $ sudo apt install postgresql postgresql-client
+
+      By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need
+      to create a new PostgreSQL user:
+
+      .. code-block:: console
+
+        $ sudo -u postgres createuser -s $USER
+        $ createdb $USER
+
+      .. note::
+         Because your PostgreSQL user has the same name as your Unix login, you will be able to
+         connect to the database without password.
+
+   .. group-tab:: Mac OS
+
+      Odoo uses PostgreSQL as database management system. Use `postgres.app
+      <https://postgresapp.com>`_ to download and install PostgreSQL (supported version: 10.0 and
+      later).
+
+      By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need
+      to create a new PostgreSQL user:
+
+      .. code-block:: console
+
+        $ sudo -u postgres createuser -s $USER
+        $ createdb $USER
+
+      .. note::
+         Because your PostgreSQL user has the same name as your Unix login, you will be able to
+         connect to the database without password.
+
+.. _install/dependencies:
+
+Dependencies
+~~~~~~~~~~~~
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      Before installing the dependencies, you must download and install the `Build Tools for Visual
+      Studio <https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019>`_.
+      When prompted, select **C++ build tools** in the **Workloads** tab and install them.
+
+      Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
+      community directory.
+
+      .. tip::
+         It can be preferable to not mix python modules packages between different instances of Odoo
+         or with your system. You can use virtualenv_ to create isolated Python environments.
+
+      Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip** on
+      the requirements file in a terminal **with Administrator privileges**:
+
+      .. code-block:: doscon
+
+          C:\> cd \CommunityPath
+          C:\> pip install setuptools wheel
+          C:\> pip install -r requirements.txt
+
+      For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss`
+      is needed:
+
+      #. Download and install `nodejs <https://nodejs.org/en/download/>`_.
+      #. Install `rtlcss`:
+
+         .. code-block:: doscon
+
+             C:\> npm install -g rtlcss
+
+      #. Edit the System Environment's variable `PATH` to add the folder where `rtlcss.cmd` is
+         located (typically: :file:`C:\\Users\\<user>\\AppData\\Roaming\\npm\\`).
+
+   .. group-tab:: Linux
+
+      Using your **distribution packages** is the preferred way of installing dependencies.
+      Alternatively, you can install the python dependencies with **pip**.
+
+      .. tabs::
+
+         .. tab:: Debian/Ubuntu
+
+            For Debian-based systems, the packages are listed in the `debian/control
+            <https://github.com/odoo/odoo/blob/master/debian/control>`_ file of the Odoo sources.
+
+            On Debian/Ubuntu, the following commands should install the required packages:
+
+            .. code-block:: console
+
+               $ cd /CommunityPath
+               $ sed -n -e '/^Depends:/,/^Pre/ s/ python3-\(.*\),/python3-\1/p' debian/control | sudo xargs apt-get install -y
+
+         .. tab:: Install with pip
+
+            As some of the python packages need a compilation step, they require system libraries to
+            be installed.
+
+            On Debian/Ubuntu-based systems, the following command should install these required
+            libraries:
+
+            .. code-block:: console
+
+               $ sudo apt install python3-pip libldap2-dev libpq-dev libsasl2-dev
+
+            Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of
+            the Odoo community directory.
+
+            .. note::
+               | The python packages in :file:`requirements.txt` are based on their stable/LTS
+                 Debian/Ubuntu corresponding version at the moment of the Odoo release.
+               | E.g., for Odoo 15.0, the `python3-babel` package version is 2.8.0 in Debian
+                 Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is then chosen in the
+                 :file:`requirements.txt`.
+
+            .. tip::
+               It can be preferable to not mix python modules packages between different instances
+               of Odoo or with your system. You can use virtualenv_ to create isolated Python
+               environments.
+
+            Navigate to the path of your Odoo Community installation (:file:`CommunityPath`) and run
+            **pip** on the requirements file to install the requirements for the current user.
+
+            .. code-block:: console
+
+               $ cd /CommunityPath
+               $ pip install -r requirements.txt
+
+      For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
+      needed:
+
+      #. Download and install **nodejs** and **npm** with your package manager.
+      #. Install `rtlcss`:
+
+         .. code-block:: console
+
+            $ sudo npm install -g rtlcss
+
+   .. group-tab:: Mac OS
+
+      Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo
+      community directory.
+
+      .. tip::
+         It can be preferable to not mix python modules packages between different instances of Odoo
+         or with your system. You can use virtualenv_ to create isolated Python environments.
+
+      Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip** on
+      the requirements file:
+
+      .. code-block:: console
+
+         $ cd /CommunityPath
+         $ pip3 install setuptools wheel
+         $ pip3 install -r requirements.txt
+
+      .. warning::
+         Non-Python dependencies need to be installed with a package manager:
+
+         #. Download and install the **Command Line Tools**:
+
+            .. code-block:: console
+
+               $ xcode-select --install
+
+         #. Download and install the package manager of your choice (homebrew_, macports_).
+         #. Install non-python dependencies.
+
+      For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is
+      needed:
+
+      #. Download and install **nodejs** with your preferred package manager (homebrew_, macports_).
+      #. Install `rtlcss`:
+
+         .. code-block:: console
+
+             $ sudo npm install -g rtlcss
+
+.. important::
+   `wkhtmltopdf` is not installed through **pip** and must be installed manually in version `0.12.5
+   <the wkhtmltopdf download page_>`_ for it to support headers and footers. See our `wiki
+   <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the various versions.
+
+Running Odoo
+------------
+
+Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the
+command-line interface of the server. It is located at the root of the Odoo Community directory.
+
+To configure the server, you can either specify :ref:`command-line arguments
+<reference/cmdline/server>` or a :ref:`configuration file <reference/cmdline/config>`.
+
+.. tip::
+   For the Enterprise edition, you must add the path to the `enterprise` addons to the `addons-path`
+   argument. Note that it must come before the other paths in `addons-path` for addons to be loaded
+   correctly.
+
+Common necessary configurations are:
+
+- PostgreSQL user and password.
+- Custom addon paths beyond the defaults, to load your own modules.
+
+A typical way to run the server would be:
+
+.. tabs::
+
+   .. group-tab:: Windows
+
+      .. code-block:: doscon
+
+          C:\> cd CommunityPath/
+          C:\> python odoo-bin -r dbuser -w dbpassword --addons-path=addons -d mydb
+
+      Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the
+      PostgreSQL login, `dbpassword` is the PostgreSQL password and `mydb` is the default database
+      to serve on `localhost:8069`.
+
+   .. group-tab:: Linux
+
+      .. code-block:: console
+
+          $ cd /CommunityPath
+          $ python3 odoo-bin --addons-path=addons -d mydb
+
+      Where `CommunityPath` is the path of the Odoo Community installation and `mydb` is the default
+      database to serve on `localhost:8069`.
+
+   .. group-tab:: Mac OS
+
+      .. code-block:: console
+
+          $ cd /CommunityPath
+          $ python3 odoo-bin --addons-path=addons -d mydb
+
+      Where `CommunityPath` is the path of the Odoo Community installation and `mydb` is the default
+      database to serve on `localhost:8069`.
+
+.. seealso::
+   - :doc:`The exhaustive list of arguments for odoo-bin </developer/misc/other/cmdline>`.
+
+.. _setup/install/docker:
+
+Docker
+======
+
+The full documentation on how to use Odoo with Docker can be found on the
+official Odoo `docker image <https://hub.docker.com/_/odoo/>`_ page.
+
+.. _Debian 11 (Bullseye): https://www.debian.org/releases/bullseye/
+.. _demo: https://demo.odoo.com
+.. _docker: https://www.docker.com
+.. _download: https://www.odoo.com/page/download
+.. _Ubuntu 20.04 (Focal): http://releases.ubuntu.com/20.04/
+.. _EPEL: https://fedoraproject.org/wiki/EPEL
+.. _PostgreSQL: http://www.postgresql.org
+.. _the official installer:
+.. _install pip:
+    https://pip.pypa.io/en/latest/installing.html#install-pip
+.. _Quilt: http://en.wikipedia.org/wiki/Quilt_(software)
+.. _saas: https://www.odoo.com/page/start
+.. _the wkhtmltopdf download page: https://github.com/wkhtmltopdf/wkhtmltopdf/releases/tag/0.12.5
+.. _UAC: http://en.wikipedia.org/wiki/User_Account_Control
+.. _wkhtmltopdf: http://wkhtmltopdf.org
+.. _pip: https://pip.pypa.io
+.. _macports: https://www.macports.org
+.. _homebrew: http://brew.sh
+.. _wheels: https://wheel.readthedocs.org/en/latest/
+.. _virtualenv: https://pypi.python.org/pypi/virtualenv
+.. _virtualenvwrapper: https://virtualenvwrapper.readthedocs.io/en/latest/
+.. _pywin32: http://sourceforge.net/projects/pywin32/files/pywin32/
+.. _community-repository: https://github.com/odoo/odoo
+.. _enterprise-repository: https://github.com/odoo/enterprise
+.. _Editions: https://www.odoo.com/pricing#pricing_table_features
+.. _nightly: https://nightly.odoo.com/
+.. _extra: https://nightly.odoo.com/extra/

content/administration/maintain.rst

@@ -0,0 +1,15 @@
+:nosearch:
+
+========
+Maintain
+========
+
+.. toctree::
+
+    maintain/domain_names
+    maintain/update
+    maintain/enterprise
+    maintain/hosting_changes
+    maintain/online
+    maintain/on_premise
+    maintain/supported_versions

content/administration/maintain/domain_names.rst

@@ -0,0 +1,334 @@
+============
+Domain names
+============
+
+A **domain name** works as an address for your website. It makes the Internet much more accessible
+as it allows users to type a meaningful web address, such as ``www.odoo.com``, rather than its
+server's IP address with a series of numbers.
+
+You can use a custom domain name to access your Odoo database and websites:
+
+- By :ref:`registering a free domain name with Odoo <domain-name/odoo-register>` (for Odoo Online
+  databases)
+- By :ref:`configuring a custom domain that you already own <domain-name/existing>`.
+
+.. note::
+   Odoo Online and Odoo.sh databases, including their websites, use by default a subdomain of
+   ``odoo.com`` for both the URL and the emails (e.g., ``https://example.odoo.com``).
+
+.. important::
+   Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online 
+   databases for one year. Visitors can then access your website with an address such as
+   ``www.example.com`` rather than the default ``example.odoo.com``.
+
+.. seealso::
+   - `Odoo Tutorials: Register a Free Domain Name
+     <https://www.odoo.com/slides/slide/register-a-free-domain-name-1663>`_
+   - `Odoo Quick Tips: Get a free domain name! <https://www.youtube.com/watch?v=eAfgeNOHLP4>`_
+
+.. _domain-name/about:
+
+About domain names
+==================
+
+Having a **good domain name** is as important to your branding as the name of your business or
+organization as it is the first thing your visitors will notice. We recommend you keep them *simple,
+short, easy to remember and spell*.
+
+A **subdomain** is a domain that is a part of another domain. It often refers to the additional part
+that comes before the main domain name. Traditionally, most websites use the ``www.`` subdomain,
+but any string of letters can be used as well. You can use subdomains to direct your visitors to
+other websites than your main website or to specific pages (e.g., ``experience.odoo.com`` points to
+a specific page.)
+
+All domain names are referenced in the **Domain Name System**, or **DNS**, which works as a giant
+directory for the Internet. There are many DNS servers, so any modification to the DNS can take up
+to 72 hours to propagate worldwide on all servers.
+
+.. _domain-name/odoo-register:
+
+Register a free domain name with Odoo
+=====================================
+
+You can register a domain name for your Odoo Online database directly from Odoo Website or your
+database manager.
+
+.. important::
+   - Your domain name is **free for one year** if you register it with Odoo!
+   - The domain name is registered with `Gandi <https://www.gandi.net/>`_, the domain name
+     registrar.
+   - You are the owner of the domain name and can use it for other purposes.
+   - Odoo manages payment and technical support for you.
+
+To do so, go to :menuselection:`Website --> Go to website --> Promote --> Domain Name`.
+Alternatively, open your `database manager <https://www.odoo.com/my/databases>`_, click on the
+:guilabel:`settings` button next to your database, then on :guilabel:`Domain names`.
+
+.. image:: domain_names/register-promote.png
+   :align: center
+   :alt: Clicking on Domain Names from an Odoo website
+
+Search for the domain name of your choice to check its availability, then select the one you want to
+register for your website.
+
+.. image:: domain_names/register-search.png
+   :align: center
+   :alt: The search of the domain name example.com shows which associated domains are available.
+
+Next, fill in the form with your information to become the domain name owner.
+
+Your domain name is directly linked to your database, but you still have to :ref:`map your domain
+name with your website <domain-name/website-map>`.
+
+.. note::
+   - Free domain names are also available for free Odoo Online databases (if you installed one app
+     only, for example). In this case, Odoo reviews your request and your website to avoid abuse.
+     This process may take up to three days.
+   - This is not available for Odoo.sh databases yet.
+
+.. _domain-name/odoo-manage:
+
+Manage your domain name registered with Odoo
+--------------------------------------------
+
+To manage the DNS records of your domain name registered with Odoo or to visualize the contacts
+associated with it, open your `database manager <https://www.odoo.com/my/databases>`_, click on the
+:guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on
+:guilabel:`Contacts` or :guilabel:`DNS`.
+
+.. image:: domain_names/manage.png
+   :align: center
+   :alt: Management of the domain names linked to an Odoo database
+
+.. note::
+   Please `submit a support ticket <https://www.odoo.com/help>`_ if you need further assistance to
+   manage your domain name.
+
+.. _domain-name/existing:
+
+Configure your existing domain name
+===================================
+
+If you already own a domain name, you can use it to point to your website.
+
+To avoid any issue with the :ref:`SSL certificate validation <domain-name/ssl>`, we highly recommend
+that you proceed with the following actions in this order:
+
+#. :ref:`Add a CNAME record <domain-name/cname>` on your domain name's DNS zone.
+#. :ref:`Map your domain name with your Odoo database <domain-name/db-map>`.
+#. :ref:`Map your domain name with your Odoo website <domain-name/website-map>`.
+
+.. _domain-name/cname:
+
+Add a CNAME record
+------------------
+
+A **CNAME record** is a type of DNS record that points to the IP address of another website rather
+than to directly to an IP address.
+
+You need a CNAME record that points to your Odoo database. The requirements are detailed in your
+database manager.
+
+.. tabs::
+
+   .. group-tab:: Odoo Online
+
+      The target address is the current address of your database, as defined at its creation (e.g.,
+      ``example.odoo.com``)
+
+   .. group-tab:: Odoo.sh
+
+      Your project's main address is defined in :menuselection:`Settings --> Project Name`.
+
+      If you want to target a specific branch (production, staging or development), go to
+      :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, and click on
+      :guilabel:`How to set up my domain?`. A message indicates which address your CNAME record
+      should target.
+
+#. Open your domain name's manager dashboard.
+#. Open the **DNS zone** management page for the domain name you want to configure.
+#. Create a **CNAME record** pointing to the address of your database.
+
+While Odoo suggests creating a CNAME record for your ``www.`` subdomain (``www.example.com``, you
+can of course use any domain name of your choice, with any subdomain (e.g.,
+``anything.example.com``).
+
+.. example::
+   You own the domain name ``example.com``, and you have an Odoo Online database at the address
+   ``example.odoo.com``. You want to access your Odoo database primarily with the domain
+   ``www.example.com`` but also with the :ref:`naked domain <domain-name/naked-domain>`
+   ``example.com``.
+
+   To do so, you create a CNAME record for the ``www`` subdomain, with ``example.odoo.com`` as the
+   target. The DNS zone manager generates the following rule and adds it to your DNS zone: ``www IN
+   CNAME example.odoo.com.``
+
+   You also create a redirection from ``example.com`` to ``wwww.example.com``.
+
+   Your new DNS records are propagated to all DNS servers.
+
+.. note::
+   Here are some specific guidelines to create a CNAME record:
+
+   - `GoDaddy <https://www.godaddy.com/help/add-a-cname-record-19236>`_
+   - `Namecheap <https://www.namecheap.com/support/knowledgebase/article.aspx/9646/2237/how-to-create-a-cname-record-for-your-domain>`_
+   - `OVH <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/#add-a-new-dns-record>`_
+   - `CloudFlare <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_
+   - `Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_
+
+.. _domain-name/naked-domain:
+
+Naked domain
+~~~~~~~~~~~~
+
+A **naked domain** is a domain name that doesn't have any subdomain at the beginning of the address
+(e.g., ``odoo.com`` instead of ``www.odoo.com``).
+
+You may want your naked domain to redirect to your website as some visitors may not type the full
+domain name to access your website.
+
+#. Open your domain name's manager dashboard.
+#. Create a **redirection** from the naked domain (``example.com``) to your main domain name
+   (``www.example.com``).
+
+.. note::
+   Depending on your domain name registrar, this redirection may be already pre-configured.
+
+.. _domain-name/db-map:
+
+Map your domain name with your Odoo database
+--------------------------------------------
+
+.. tabs::
+
+   .. group-tab:: Odoo Online
+
+      Open your `database manager <https://www.odoo.com/my/databases>`_, click on the
+      :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on
+      :guilabel:`Use my own domain` at the bottom of the right column.
+
+      Type the domain name you want to add to this database, then click on :guilabel:`Verify` to
+      check if the CNAME record is correctly configured. Once done, click on :guilabel:`I confirm,
+      it's done`.
+
+      .. image:: domain_names/online-map.png
+         :align: center
+         :alt: Verification of the CNAME records of a domain name before mapping it with a database
+
+   .. group-tab:: Odoo.sh
+
+      Go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, type
+      the domain name you want to add to this database, then click on :guilabel:`Add domain`.
+
+      .. image:: domain_names/odoo-sh-map.png
+         :align: center
+         :alt: Mapping a domain name with an Odoo.sh branch
+
+      .. seealso::
+         - :ref:`Odoo.sh branches: settings tab <odoosh-gettingstarted-branches-tabs-settings>`
+
+.. warning::
+   Make sure to :ref:`add a CNAME record <domain-name/cname>` to your domain name's DNS **before**
+   mapping your domain name with your Odoo database.
+
+   Failing to do so may impede the validation of the :ref:`SSL certificate <domain-name/ssl>` and
+   would result in a *certificate name mismatch* error. This is often displayed by web browsers as a
+   warning such as *"Your connection is not private"*.
+
+   If this is the case and you have added the domain name to your database's settings less than five
+   days ago, wait 24 hours as the validation may still happen. Otherwise, please `submit a support
+   ticket <https://www.odoo.com/help>`_ including screenshots of your CNAME records.
+
+.. _domain-name/ssl:
+
+SSL encryption (HTTPS protocol)
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+**SSL encryption** is an encryption-based Internet security protocol. It allows your visitors to
+navigate your website through a secure connection, which appears as an ``https://`` protocol at the
+beginning of your web address, rather than a non-secure ``http://`` protocol.
+
+Odoo generates a separate SSL certificate for each domain :ref:`mapped in the database manager
+<domain-name/db-map>`, using integration with `Let's Encrypt Certificate Authority and ACME protocol
+<https://letsencrypt.org/how-it-works/>`_.
+
+.. note::
+   - The certificate generation may take up to 24h.
+   - Several attempts to validate your certificate are made during the five days following the
+     moment you add your domain name in your database's settings.
+   - If you already use another service, you can keep using it or simply change for Odoo.
+
+.. _domain-name/web-base-url:
+
+Web base URL of a database
+~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+.. note::
+   If you have Odoo Website, you can disregard this part and directly :ref:`map your domain name
+   with your website <domain-name/website-map>`.
+
+The **web base URL** of a database, or **root URL** affects your main website address and all the
+links sent to your customers (e.g., quotations, portal links, etc.).
+
+To configure it, access your Odoo database with your custom address, then log in as an administrator
+of your database (any user in the *Settings* group) from the login screen.
+
+.. warning::
+   Connecting to your database with the original Odoo subdomain address (e.g., ``example.odoo.com``
+   also updates the web base URL of your database. See below to prevent these automatic updates.
+
+Alternatively, you can do it manually. To do so, activate the :ref:`developer mode
+<developer-mode>`, then go to :menuselection:`Settings --> Technical --> System Parameters`.
+
+Find the key called ``web.base.url`` (or create it if it does not exist) and enter the full address
+of your website as value, such as ``https://www.example.com``.
+
+.. note::
+   The URL must include the protocol ``https://`` (or ``http://``) and must not end with a slash
+   (``/``).
+
+To prevent the automatic update of the web base URL when an administrator logs in the database, you
+can create the following System Parameter:
+
+- key: ``web.base.url.freeze``
+- value: ``True``
+
+.. _domain-name/website-map:
+
+Map your domain name with your website
+======================================
+
+Mapping your domain name to your website isn't the same as mapping it with your database:
+
+- It defines your domain name as the main one for your website, helping search engines to index your
+  website properly.
+- It defines your domain name as the base URL for your database, including the portal links sent by
+  email to your customers.
+- If you have multiple websites, it maps your domain name with the appropriate website.
+
+Go to :menuselection:`Website --> Configuration --> Settings --> Website Info`. If you have multiple
+websites, select the one you want to configure.
+
+In the :guilabel:`Domain` field, fill in the web address of your website (e.g.,
+``https://www.example.com``) and click on :guilabel:`Save`.
+
+.. image:: domain_names/website-settings.png
+   :align: center
+   :alt: Configuring https://www.example.com as the Domain of the website
+
+.. warning::
+   Mapping your domain name with your Odoo website prevents Google from indexing both your custom
+   domain name ``www.example.com`` and your original odoo database address ``example.odoo.com``.
+
+   If both addresses are already indexed, it may take some time before Google removes the indexation
+   of the second address. You may also try using the `Google Search Console
+   <https://search.google.com/search-console/welcome>`_ to fix this.
+
+.. note::
+   If you have multiple websites and companies on your database, make sure that you select the
+   right :guilabel:`Company` in the website settings, next to the :guilabel:`Domain` settings. Doing
+   so indicates Odoo which URL to use as the :ref:`base URL <domain-name/web-base-url>` according to
+   the company in use.
+
+.. seealso::
+  - :doc:`/applications/general/email_communication/email_servers`

content/administration/maintain/enterprise.rst

@@ -1,9 +1,9 @@
 
 .. _setup/enterprise:
 
-============================
-From Community to Enterprise
-============================
+===============================
+Upgrade Community to Enterprise
+===============================
 
 Depending on your current installation, there are multiple ways to upgrade
 your community version.

content/administration/maintain/hosting_changes.rst

@@ -1,9 +1,9 @@
 
 .. _db_management/hosting_changes:
 
-===============
-Hosting Changes
-===============
+=======================
+Change hosting solution
+=======================
 
 You may want to move your Odoo database from one hosting solution to another.
 Depending on the platforms, you have to do it by yourself or contact our support team first.
@@ -11,8 +11,6 @@ Depending on the platforms, you have to do it by yourself or contact our support
 From on-premises to Odoo Online
 ===============================
 
-.. warning:: Odoo Online is not compatible with **non-standard apps**.
-
 1. Create a :ref:`duplicate <duplicate_premise>` of your database: in this duplicate, uninstall all the **non-standard apps**.
 2. Grab a "dump with filestore" of your database by using the Database Manager.
 3. **If you have time constraints, contact us earlier to schedule the transfer.**
@@ -20,6 +18,11 @@ From on-premises to Odoo Online
 5. We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you.
 6. It's done!
 
+.. important::
+   - Odoo Online is not compatible with **non-standard apps**.
+   - The database you are moving to Odoo Online must be in a :doc:`supported version
+     <supported_versions>`.
+
 From on-premises to Odoo.sh
 ===========================
 
@@ -49,7 +52,7 @@ From Odoo.sh to Odoo Online
 
 1.  Uninstall all the **non-standard apps**: test it in a staging build first, then do it in your production build.
 2.  **If you have time constraints, contact us earlier to schedule the transfer.**
-3. `Create a support ticket <https://www.odoo.com/help>`_ and attach the dump (if the file is too large, use any file transfer service and attach the link to your ticket). Also include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com).
+3. `Create a support ticket <https://www.odoo.com/help>`_ and include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com).
 4.  We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you.
 5.  It's done!
 
@@ -59,4 +62,3 @@ From Odoo.sh to on-premises
 1.  Grab a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`.
 2.  Restore it from the database manager on your local server.
 
-

content/administration/maintain/on_premise.rst

@@ -1,9 +1,6 @@
-
-.. _db_premise:
-
-===============================
-On-premises Database management
-===============================
+==============================
+On-premise database management
+==============================
 
 Register a database
 ===================
@@ -12,7 +9,7 @@ To register your database, you just need to enter your Subscription Code in the
 banner in the App Switcher. Make sure you do not add extra spaces before or after
 your subscription code. If the registration is successful, it will turn green and
 will provide you with the Expiration Date of your freshly-registered database. You
-can check this Epiration Date in the About menu (Odoo 9) or in the Settings Dashboard
+can check this Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard
 (Odoo 10).
 
 Registration Error Message
@@ -21,7 +18,7 @@ Registration Error Message
 If you are unable to register your database, you will likely encounter this
 message:
 
-.. image:: media/error_message_sub_code.png
+.. image:: on_premise/error_message_sub_code.png
     :align: center
     :alt: Something went wrong while registering your database,
           you can try again or contact Odoo Help
@@ -44,14 +41,14 @@ Solutions
   * You can unlink the old database yourself on your `Odoo Contract
     <https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"
 
-    .. image:: media/unlink_single_db.png
+    .. image:: on_premise/unlink_single_db.png
         :align: center
 
 
     A confirmation message will appear; make sure this is the correct database as
     it will be deactivated shortly:
 
-    .. image:: media/unlink_confirm_enterprise_edition.png
+    .. image:: on_premise/unlink_confirm_enterprise_edition.png
         :align: center
 
 
@@ -65,7 +62,7 @@ Solutions
     <https://accounts.odoo.com/my/subscription>`__, a short message will appear
     specifying which database is problematic:
 
-    .. image:: media/unlink_db_name_collision.png
+    .. image:: on_premise/unlink_db_name_collision.png
         :align: center
 
 
@@ -96,7 +93,7 @@ Error message due to too many users
 If you have more users in your local database than provisionned in your
 Odoo Enterprise subscription, you may encounter this message:
 
-.. image:: media/add_more_users.png
+.. image:: on_premise/add_more_users.png
     :align: center
     :alt: This database will expire in X days, you
           have more users than your subscription allows
@@ -125,7 +122,7 @@ Database expired error message
 If your database reaches its expiration date before your renew your subscription,
 you will encounter this message:
 
-.. image:: media/database_expired.png
+.. image:: on_premise/database_expired.png
     :align: center
     :alt: This database has expired.
 
@@ -157,7 +154,7 @@ You can duplicate your database by accessing the database manager on your
 server (<odoo-server>/web/database/manager). In this page, you can easily
 duplicate your database (among other things).
 
-.. image:: media/db_manager.gif
+.. image:: on_premise/db_manager.gif
     :align: center
 
 
@@ -175,5 +172,5 @@ System Parameters`, we advise you to use a `uuid generator <https://www.uuidtool
 use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any
 other record by clicking on it and using the edit button.
 
-.. image:: media/db_uuid.png
+.. image:: on_premise/db_uuid.png
     :align: center

content/administration/maintain/online.rst

@@ -0,0 +1,155 @@
+=================================
+Online (SaaS) database management
+=================================
+
+To manage a database, sign in to https://www.odoo.com and access the `database management page
+<https://www.odoo.com/my/databases>`_ by clicking on the user icon, then on *My Databases*.
+
+.. image:: online/my-databases.png
+   :align: center
+   :alt: Clicking on the user icon opens a drop-down menu. "My databases" button is highlighted.
+
+.. note::
+   Make sure you are connected as the administrator of the database you want to manage.
+
+.. image:: online/dropdown-menu.png
+   :align: right
+   :alt: Clicking on the gear icon opens the drop-down menu.
+
+Open the drop-down menu next to the database you want to manage by clicking on the gear icon.
+
+Several actions are available:
+
+- :ref:`online/upgrade`
+- :ref:`online/duplicate`
+- :ref:`online/rename`
+- :ref:`online/download`
+- :ref:`online/domains`
+- :ref:`online/tags`
+- :ref:`online/delete`
+- :ref:`online/contact-support`
+- :ref:`online/users`
+
+.. _online/upgrade:
+
+Upgrade
+=======
+
+If you are *not* on the latest **Online version**, you should receive an invitation to :doc:`upgrade
+<../upgrade>` your database. A **Rolling Release button** on your database's main screen proposes an
+upgrade to the latest version (e.g., 13.0 to 15.1).
+
+.. important::
+   - | **If your Odoo database's version is lower than the latest major release:**
+     | You must upgrade your database within two months. After these two months, an automatic
+       upgrade is initiated.
+   - | **If your Odoo database's version is equal to or higher than the latest major release:**
+     | You can disregard the invitation to upgrade as you probably wouldn't benefit from new
+       features every two months.
+
+.. note::
+   Versions that are not supported anymore become deprecated and need to be updated to avoid
+   security issues. We recommend you initiate the upgrade of the database yourself, as this method
+   allows you to request a test upgrade of your database to check for any discrepancies.
+
+.. seealso::
+   - :doc:`../upgrade`
+   - :doc:`supported_versions`
+
+.. _online/duplicate:
+
+Duplicate
+=========
+
+Make an exact copy of the database to be able to perform testing without compromising the daily
+operations.
+
+.. important::
+   - By checking *For testing purposes*, all external communication (emails, payments, delivery
+     orders, etc.) are disabled by default on the duplicated database.
+   - Duplicate databases expire automatically after 15 days.
+
+.. _online/rename:
+
+Rename
+======
+
+Rename the database and its URL.
+
+.. _online/download:
+
+Download
+========
+
+Download instantly a ZIP file with a backup of the database.
+
+.. note::
+   Databases are backed up daily according to the `Odoo Cloud SLA
+   <https://www.odoo.com/cloud-sla>`_.
+
+.. _online/domains:
+
+Domains
+=======
+
+Configure custom domains to access the database via another URL.
+
+.. seealso::
+   - :doc:`domain_names`
+
+.. _online/tags:
+
+Tags
+====
+
+Add tags to sort your databases out. You can search the tags in the search bar.
+
+.. _online/delete:
+
+Delete
+======
+
+Delete a database instantly.
+
+.. danger::
+   Deleting a database means that all data is permanently lost. The deletion is instant and for all
+   users. It is recommended to create a backup of the database before deleting it.
+
+Read carefully the warning message that pops up and proceed only if you fully understand the
+implications of deleting a database:
+
+.. image:: online/delete.png
+   :align: center
+   :alt: A warning message is prompted before deleting a database.
+
+.. note::
+   - Only an administrator can delete a database.
+   - The database name is immediately available for a new database.
+   - It is not possible to delete a database if it is expired or linked to a subscription. If
+     needed, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+   - To delete your account, please get in touch with `Odoo Support <https://www.odoo.com/help>`_.
+
+.. _online/contact-support:
+
+Contact Support
+===============
+
+Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already
+pre-filled.
+
+.. _online/users:
+
+Invite / Remove Users
+=====================
+
+To invite users, fill out the email address of the new user and click on *Invite*. To add multiple
+users, click on *Add more users*.
+
+.. image:: online/invite-users.png
+   :align: center
+   :alt: Clicking on "Add more users" adds additional email fields.
+
+To remove users, select the users to remove and click on *Remove*.
+
+.. seealso::
+   - :doc:`/applications/general/users/manage_users`

content/administration/maintain/supported_versions.rst

@@ -0,0 +1,87 @@
+
+.. _supported_versions:
+
+==================
+Supported versions
+==================
+
+Odoo provides support and bug fixing **for the 3 last major versions** of Odoo.
+
+.. note::
+   Odoo releases intermediary versions called **Online versions** on the :doc:`Odoo Online <online>`
+   hosting every two months. Odoo Online users can then benefit from the latest features of Odoo.
+
+   - Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly.
+   - Online versions are *not* released for Odoo.sh and On-Premise installations.
+   - Online versions are listed below as *SaaS*.
+
+What's the support status of my Odoo?
+=====================================
+
+This matrix shows the support status of every version.
+
+**Major releases are in bold type.**
+
++-----------------+-------------+----------+-------------+----------------+------------------------+
+|                 | Odoo Online | Odoo.sh  | On-Premise  | Release date   | End of support         |
++=================+=============+==========+=============+================+========================+
+| Odoo saas~15.2  | |green|     | N/A      | N/A         | March 2022     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo saas~15.1  | |red|       | N/A      | N/A         | February 2022  |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 15.0**   | |green|     | |green|  | |green|     | October 2021   | October 2024 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 14.0**   | |green|     | |green|  | |green|     | October 2020   | October 2023 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 13.0**   | |green|     | |green|  | |green|     | October 2019   | October 2022 (planned) |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo saas~12.3  | |red|       | N/A      | N/A         | August 2019    |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 12.0**   | |red|       | |red|    | |red|       | October 2018   | October 2021           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo saas~11.3  | |red|       | N/A      | N/A         | April 2018     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 11.0**   | |red|       | |red|    | |red|       | October 2017   | October 2020           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~15 | |red|       | N/A      | N/A         | March 2017     |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 10.saas~14 | |red|       | N/A      | N/A         | January 2017   |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 10.0**   | |red|       | |red|    | |red|       | October 2016   | October 2019           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 9.saas~11  | |red|       | N/A      | N/A         | May 2016       |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 9.0**    | |red|       | N/A      | |red|       | October 2015   | October 2018           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| Odoo 8.saas~6   | |red|       | N/A      | N/A         | February 2015  |                        |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+| **Odoo 8.0**    | |red|       | N/A      | |red|       | September 2014 | October 2017           |
++-----------------+-------------+----------+-------------+----------------+------------------------+
+
+.. note::
+
+    |green| Supported version
+
+    |red| End-of-support
+
+    N/A Never released for this platform
+
+    🏁 Future version, not released yet
+
+.. This is an awful way to display colored circles but "Large Green Circle Emoji" was only released
+   in 2019 (see https://unicode-table.com/en/1F7E2/). Let's wait a few more years...
+
+.. |green| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6IzAwYTcwMCIvPjwvc3ZnPg==
+   :width: 15
+
+.. |red| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6I2QwMDAwMCIvPjwvc3ZnPg==
+   :width: 15
+
+I run an older version of Odoo/OpenERP/TinyERP
+==============================================
+
+OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform.
+
+TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform.
+
+Even though we don't support older versions, you can always `upgrade from any version <https://upgrade.odoo.com/>`_.

content/administration/maintain/update.rst

@@ -1,9 +1,9 @@
 
 .. _setup/update:
 
-=============================
-Updating an Odoo installation
-=============================
+==============
+Bugfix updates
+==============
 
 Introduction
 ============
@@ -147,4 +147,4 @@ Docker
 ------
 
 Please refer to our `Docker image documentation <https://hub.docker.com/_/odoo/>`_ for
-specific update instructions.
+specific update instructions.

content/administration/odoo_sh.rst

@@ -1,5 +1,7 @@
+:nosearch:
+
 =======
-Odoo sh
+Odoo.sh
 =======
 
 

content/administration/odoo_sh/advanced.rst

@@ -1,3 +1,4 @@
+:nosearch:
 
 =================
 Advanced
@@ -8,5 +9,4 @@ Advanced
 
    advanced/containers
    advanced/submodules
-   advanced/upgrade_your_database
    advanced/frequent_technical_questions

content/administration/odoo_sh/advanced/containers.rst

@@ -167,7 +167,7 @@ In the above commands, the argument:
 * ``--stop-after-init`` will immediately shutdown the server instance after it completed the operations you asked.
 
 More options are available and detailed in the
-:doc:`CLI documentation </developer/reference/cmdline>`.
+:doc:`CLI documentation </developer/misc/other/cmdline>`.
 
 You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh to run your server.
 Look for "*odoo: addons paths*":
@@ -232,6 +232,6 @@ Save the file and then run the Odoo Shell:
 Finally, *via* the Odoo Shell, you can trigger the piece of code/function/method
 you want to debug.
 
-.. image:: ./media/pdb_sh.png
+.. image:: containers/pdb_sh.png
     :align: center
     :alt: Console screenshot showing ``pdb`` running in an Odoo.sh shell.

content/administration/odoo_sh/advanced/submodules.rst

@@ -44,7 +44,7 @@ On Odoo.sh, in the branches view of your project, choose the branch in which you
 
 In the upper right corner, click on the *Submodule* button, and then on *Run*.
 
-.. image:: ./media/advanced-submodules-button.png
+.. image:: submodules/advanced-submodules-button.png
    :align: center
 
 A dialog with a form is shown. Fill the inputs as follows:
@@ -53,12 +53,12 @@ A dialog with a form is shown. Fill the inputs as follows:
 * Branch: The branch you want to use.
 * Path: The folder in which you want to add this submodule in your branch.
 
-.. image:: ./media/advanced-submodules-dialog.png
+.. image:: submodules/advanced-submodules-dialog.png
    :align: center
 
 On Github, you can get the repository URL with the *Clone or download* button of the repository. Make sure to *use SSH*.
 
-.. image:: ./media/advanced-submodules-github-sshurl.png
+.. image:: submodules/advanced-submodules-github-sshurl.png
   :align: center
 
 .. _odoosh-advanced-submodules-withgit:

content/administration/odoo_sh/advanced/upgrade_your_database.rst

@@ -1,48 +0,0 @@
-
-=====================
-Upgrade your database
-=====================
-
-.. _odoosh-advanced-upgrade_your_database:
-
-Download and Upload your database
-=================================
-
-Download a dump of your database (from the :ref:`Builds view <odoosh-gettingstarted-builds-download-dump>`), choose the
-exact copy and without filestore options. Upload the .sql.gz dump on https://upgrade.odoo.com/upload and
-select the Testing Purpose. If you have custom code, you can choose to have it upgraded by us, or do it yourself. Once
-it's processed, you'll get a dump of the database in return.
-
-.. warning::
-   Do *not* upload *backups* of your production database (found in the Backups tab of the production branch) as these
-   are incompatible with the Upgrade platform - they contain your complete sources, etc. that are not needed for the
-   upgrade. Make sure to download a **Dump** instead - either through the Backups tab using the *Download Dump* button
-   or through the Builds page by using the *Download Dump* entry of the contextual menu of your latest production build.
-
-Test your upgraded database
-===========================
-
-Create a staging branch that will run the upgraded database. Either make sure your production branch's code is
-compatible between the two Odoo versions and fork your production branch, or make a new staging branch containing
-the upgraded code.
-
-Once the staging build is done (it doesn't matter if it failed due to the version incompatibility), import your
-upgraded dump in the backups tab of the branch. The platform will automatically detect the version of the dump and
-change the version of Odoo's source code to the corresponding version for the build.
-
-Test the upgraded database and make sure everything runs as it's supposed to.
-
-Replace your existing production database
-=========================================
-
-Once you've tested everything and you're satisfied, start the process over to get an up-to-date upgraded dump:
-
-* Make a new dump of your production database (as described in step 1)
-* Upload it on upgrade.odoo.com and select the Production purpose
-* Receive the newly upgraded dump and import it in your production branch. The build might get marked as failed because
-  the platform will run it with the upgraded databases' Odoo version together with the old custom code.
-* Merge or commit the upgraded custom code in the production branch
-
-If anything goes wrong, remember you can restore a backup. The platform will always make one before you make any
-Odoo.sh operation on the production database. If the restored backup comes from a previous version, the platform will
-detect it and change the project's Odoo version back if it needs to.

content/administration/odoo_sh/getting_started.rst

@@ -1,3 +1,4 @@
+:nosearch:
 
 =================
 Get started

content/administration/odoo_sh/getting_started/branches.rst

@@ -8,7 +8,7 @@ Overview
 
 The branches view gives you an overview of the different branches your repository has.
 
-.. image:: ./media/interface-branches.png
+.. image:: branches/interface-branches.png
    :align: center
 
 .. _odoosh-gettingstarted-branches-stages:
@@ -20,7 +20,7 @@ Odoo.sh offers three different stages for your branches: production, staging and
 
 You can change the stage of a branch by drag and dropping it into the stage section title.
 
-.. image:: ./media/interface-branches-stagechange.png
+.. image:: branches/interface-branches-stagechange.png
    :align: center
 
 .. _stage_production:
@@ -42,7 +42,7 @@ instance will be held temporarily unavailable for maintenance reason.
 
 This method is equivalent to perform an upgrade of the module through the Apps menu,
 or through the :code:`-u` switch of
-:doc:`the command line </developer/reference/cmdline>`.
+:doc:`the command line </developer/misc/other/cmdline>`.
 
 In the case the changes in the commit prevent the server to restart,
 or if the modules update fails,
@@ -109,7 +109,7 @@ Merging your branches
 ---------------------
 You can merge your branches easily by drag and dropping them into each other.
 
-.. image:: ./media/interface-branches-merge.png
+.. image:: branches/interface-branches-merge.png
    :align: center
 
 When you want to test the changes of your development branches with the production data,
@@ -156,7 +156,7 @@ An overview of your branch history:
 * The messages of the commits and their authors,
 * The various events linked to the platform, such as stage changes, database imports, backup restores.
 
-.. image:: ./media/interface-branches-history.png
+.. image:: branches/interface-branches-history.png
    :align: center
 
 For each event, a status is displayed in the top right-hand corner.
@@ -172,7 +172,7 @@ This tab contains the mail catcher. It displays an overview of the emails sent b
 The mail catcher is available for your development and
 staging branches as the emails of your production database are really sent instead of being intercepted.
 
-.. image:: ./media/interface-branches-mails.png
+.. image:: branches/interface-branches-mails.png
    :align: center
    :scale: 50%
 
@@ -181,7 +181,7 @@ Shell
 A shell access to your container. You can perform basic linux commands (:code:`ls`, :code:`top`)
 and open a shell on your database by typing :code:`psql`.
 
-.. image:: ./media/interface-branches-shell.png
+.. image:: branches/interface-branches-shell.png
    :align: center
 
 You can open multiple tabs and drag-and-drop them to arrange the layout as you wish,
@@ -197,7 +197,7 @@ Editor
 An online integrated development environment (IDE) to edit the source code.
 You can also open terminals, Python consoles and even Odoo Shell consoles.
 
-.. image:: ./media/interface-branches-editor.png
+.. image:: branches/interface-branches-editor.png
    :align: center
 
 You can open multiple tabs and drag-and-drop them to arrange the layout as you wish,
@@ -207,17 +207,19 @@ Monitoring
 ----------
 This link contains various monitoring metrics of the current build.
 
-.. image:: ./media/interface-branches-monitoring.png
+.. image:: branches/interface-branches-monitoring.png
    :align: center
 
 You can zoom, change the time range or select a specific metric on each graph.
 On the graphs, annotations help you relate to changes on the build (database import, git push, etc...).
 
+.. _odoosh/logs:
+
 Logs
 ----
 A viewer to have a look to your server logs.
 
-.. image:: ./media/interface-branches-logs.png
+.. image:: branches/interface-branches-logs.png
    :align: center
 
 Different logs are available:
@@ -241,7 +243,7 @@ Backups
 A list of the backups available for download and restore, the ability to perform a manual backup and to import a
 database.
 
-.. image:: ./media/interface-branches-backups.png
+.. image:: branches/interface-branches-backups.png
    :align: center
 
 Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 weekly and 3 monthly backups.
@@ -283,7 +285,7 @@ Settings
 --------
 Here you can find a couple of settings that only apply to the currently selected branch.
 
-.. image:: ./media/interface-branches-settings.jpg
+.. image:: branches/interface-branches-settings.jpg
    :align: center
 
 **Behaviour upon new commit**
@@ -300,7 +302,7 @@ back from staging to development will automatically be set to 'Do nothing'.
 
 Choose the modules to install automatically for your development builds.
 
-.. image:: ./media/interface-settings-modulesinstallation.png
+.. image:: branches/interface-settings-modulesinstallation.png
    :align: center
 
 * *Install only my modules* will install the modules of the branch only. This is the default option.
@@ -382,7 +384,9 @@ we are considering the feature if there is enough demand.
 In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM
 (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name
 settings to increase the deliverability of your outgoing emails.
-The configuration steps are explained in the :ref:`Discuss app documentation <discuss-email_servers-spf-compliant>`.
+The configuration steps are explained in the documentation about :ref:`SPF 
+<email_communication/spf_compliant>` and :ref:`DKIM <email_communication/dkim_compliant>`.
+
 
 .. Warning::
   Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host can lead to the
@@ -393,7 +397,7 @@ Shell commands
 ==============
 In the top right-hand corner of the view, different shell commands are available.
 
-.. image:: ./media/interface-branches-shellcommands.png
+.. image:: branches/interface-branches-shellcommands.png
    :align: center
 
 Each command can be copied in the clipboard to be used in a terminal,
@@ -462,12 +466,12 @@ To do so, follow these steps:
    (only apply the step 1)
 #. Paste the copied content to your profile SSH keys and press "Add"
 
-   .. image:: ./media/SSH-key-pasting.png
+   .. image:: branches/SSH-key-pasting.png
       :align: center
 
 #. The key should appear below
 
-   .. image:: ./media/SSH-key-appearing.png
+   .. image:: branches/SSH-key-appearing.png
       :align: center
 
 Connection
@@ -481,7 +485,7 @@ To connect to your builds using ssh use the following command in a terminal:
 
 You will find a shortcut for this command into the SSH tab in the upper right corner.
 
-.. image:: ./media/SSH-panel.png
+.. image:: branches/SSH-panel.png
    :align: center
 
 Provided you have the :ref:`correct access rights <odoosh-gettingstarted-settings-collaborators>` on the project,

content/administration/odoo_sh/getting_started/builds.rst

@@ -13,7 +13,7 @@ In Odoo.sh, a build is considered as a database loaded by an Odoo server
 running on a specific revision of your project repository in a containerized environment.
 Its purpose is to test the well-behavior of the server, the database and the features with this revision.
 
-.. image:: ./media/interface-builds.png
+.. image:: builds/interface-builds.png
    :align: center
 
 In this view, a row represents a branch, and a cell of a row represents a build of this branch.
@@ -95,7 +95,7 @@ Features
 The production branch will always appear first,
 and then the other branches are ordered by last build created. You can filter out the branches.
 
-.. image:: ./media/interface-builds-branches.png
+.. image:: builds/interface-builds-branches.png
    :align: center
 
 For each branch, you can access the last build's database using the *Connect* link and jump to the branch code using
@@ -103,7 +103,7 @@ the *Github* link. For other branches than the production, you can create a new
 of the branch using the link *rebuild*. This last link is not available when there is already a build in progress for
 the branch.
 
-.. image:: ./media/interface-builds-build.png
+.. image:: builds/interface-builds-build.png
    :align: center
 
 For each build, you can access the revision changes using the button with the Github icon.
@@ -113,7 +113,7 @@ in the dropdown menu of the *Connect* button.
 
 .. _odoosh-gettingstarted-builds-download-dump:
 
-.. image:: ./media/interface-builds-build-dropdown.png
+.. image:: builds/interface-builds-build-dropdown.png
    :align: center
 
 .. _odoosh-gettingstarted-builds-dropdown-menu: