test

.gitattributes

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

.github/CODEOWNERS

@@ -0,0 +1,11 @@
+# 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
+*.mo
 
 # Sphinx build files
 _build/
+extensions/odoo_theme/static/style.css
 
 # Dependencies
 odoo

.tx/config

@@ -1,63 +1,63 @@
 [main]
 host = https://www.transifex.com
+type = PO
 
-[o:odoo:p:odoo-16-doc:r:administration]
-file_filter = locale/<lang>/LC_MESSAGES/administration.po
-source_file = locale/sources/administration.pot
-source_lang = en
-
-[o:odoo:p:odoo-16-doc:r:applications]
+[odoo-14-doc.applications]
 file_filter = locale/<lang>/LC_MESSAGES/applications.po
 source_file = locale/sources/applications.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:finance]
+[odoo-14-doc.finance]
 file_filter = locale/<lang>/LC_MESSAGES/finance.po
 source_file = locale/sources/finance.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:general]
+[odoo-14-doc.general]
 file_filter = locale/<lang>/LC_MESSAGES/general.po
 source_file = locale/sources/general.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:index]
+[odoo-14-doc.index]
 file_filter = locale/<lang>/LC_MESSAGES/index.po
 source_file = locale/sources/index.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:inventory_and_mrp]
+[odoo-14-doc.inventory_and_mrp]
 file_filter = locale/<lang>/LC_MESSAGES/inventory_and_mrp.po
 source_file = locale/sources/inventory_and_mrp.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:marketing]
+[odoo-14-doc.marketing]
 file_filter = locale/<lang>/LC_MESSAGES/marketing.po
 source_file = locale/sources/marketing.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:productivity]
+[odoo-14-doc.productivity]
 file_filter = locale/<lang>/LC_MESSAGES/productivity.po
 source_file = locale/sources/productivity.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:sales]
+[odoo-14-doc.sales]
 file_filter = locale/<lang>/LC_MESSAGES/sales.po
 source_file = locale/sources/sales.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:services]
+[odoo-14-doc.services]
 file_filter = locale/<lang>/LC_MESSAGES/services.po
 source_file = locale/sources/services.pot
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:user_settings]
+[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
 source_lang = en
 
-[o:odoo:p:odoo-16-doc:r:websites]
+[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

@@ -9,21 +9,16 @@ ifndef BUILD_DIR
   BUILD_DIR    = _build
 endif
 
-ifndef CURRENT_LANG
-  CURRENT_LANG = en
-endif
-
 SPHINX_BUILD   = sphinx-build
 CONFIG_DIR     = .
 SPHINXOPTS     = -D project_root=$(ROOT) -D canonical_version=$(CANONICAL_VERSION) \
                  -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
 
+
 HTML_BUILD_DIR = $(BUILD_DIR)/html
 ifdef VERSIONS
   HTML_BUILD_DIR := $(HTML_BUILD_DIR)/master
@@ -42,21 +37,20 @@ help:
 	@echo "  html         to build the documentation to HTML"
 	@echo "  fast         to build the documentation to HTML with shallow menu (faster)"
 	@echo "  clean        to delete the build files"
-	@echo "  test         to run the guidelines tests"
 
 clean:
 	@echo "Cleaning build files..."
 	rm -rf $(BUILD_DIR)/*
 	@echo "Cleaning finished."
 
-html: $(HTML_BUILD_DIR)/_static/style.css
+html: $(BUILD_DIR)/html/_static/style.css
 	@echo "Starting build..."
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b html $(SPHINXOPTS) $(SOURCE_DIR) $(HTML_BUILD_DIR)
 	@echo "Build finished."
 
 # To call *after* `make html`
 # Binary dependencies (Debian): texlive-fonts-recommended texlive-latex-extra
-# texlive-fonts-extra
+# texlive-generic-recommended texlive-fonts-extra
 latexpdf:
 	@echo "Starting build..."
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b latex $(SPHINXOPTS) $(SOURCE_DIR) $(BUILD_DIR)/latex
@@ -69,10 +63,10 @@ gettext:
 	$(SPHINX_BUILD) -c $(CONFIG_DIR) -b gettext $(SOURCE_DIR) locale/sources
 	@echo "Generation finished."
 
-$(HTML_BUILD_DIR)/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
+$(BUILD_DIR)/html/_static/style.css: extensions/odoo_theme/static/style.scss extensions/odoo_theme/static/scss/*.scss
 	@echo "Compiling stylesheets..."
-	mkdir -p $(HTML_BUILD_DIR)/_static
-	python3 -m pysassc extensions/odoo_theme/static/style.scss $(HTML_BUILD_DIR)/_static/style.css
+	mkdir -p $(BUILD_DIR)/html/_static
+	pysassc extensions/odoo_theme/static/style.scss $(BUILD_DIR)/html/_static/style.css
 	@echo "Compilation finished."
 
 #=== Development and debugging rules ===#
@@ -80,9 +74,6 @@ $(HTML_BUILD_DIR)/_static/style.css: extensions/odoo_theme/static/style.scss ext
 fast: SPHINXOPTS += -A collapse_menu=True
 fast: html
 
-static: $(HTML_BUILD_DIR)/_static/style.css
-	cp -r extensions/odoo_theme/static/* $(HTML_BUILD_DIR)/_static/
-	cp -r static/* $(HTML_BUILD_DIR)/_static/
-
-test:
-	@python tests/main.py $(SOURCE_DIR)/administration $(SOURCE_DIR)/applications $(SOURCE_DIR)/contributing $(SOURCE_DIR)/developer $(SOURCE_DIR)/services redirects
+static: $(BUILD_DIR)/static/style.css
+	cp -r extensions/odoo_theme/static/* $(BUILD_DIR)/html/_static/
+	cp -r static/* $(BUILD_DIR)/html/_static/

README.md

@@ -4,33 +4,47 @@
 
 ### Requirements
 
-- Git
-- Python 3.6, 3.7, or 3.8
-- Python dependencies listed in the file `requirements.txt`.
-- Make
-- A local copy of the [odoo/odoo repository](https://github.com/odoo/odoo) (optional)
+- [Git](https://www.odoo.com/documentation/master/contributing/documentation.html#install-git)
+- [Python 3.6, 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
 
-1. In a terminal, navigate to the root directory of the documentation and build it `make`.
+1. In a terminal, navigate to the root directory and compile the documentation to HTML with the
+   following command:
+
+   ```sh
+   make
+   ```
+
    Additional commands are available with `make help`.
-2. Open the file `documentation/_build/html/index.html` in your web browser.
-3. See [this guide](https://www.odoo.com/documentation/latest/contributing/documentation.html)
+
+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/master/contributing/documentation.html#preview-your-changes)
    for more detailed instructions.
 
-Optional: place your local copy of the `odoo/odoo` repository in the parent directory or in the root
-directory of the documentation to build the latter with the documented Python docstrings.
+Optional: to fully build the developer documentation with inline docstrings for documented Python
+functions, place your local copy of the `odoo/odoo` repository in the root directory. Alternatively,
+create a symbolic link with `odoo` as link name. If the Odoo sources are not found, a warning will
+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/latest/contributing/documentation.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/issues).
+[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
 [the official eLearning](https://odoo.com/slides) and
-[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).
+[Scale-up, The Business Game](https://www.odoo.com/page/scale-up-business-game).

commit_template.txt

@@ -16,4 +16,4 @@
 # [REM] = Removal
 # [REF] = Refactoring (restructuring)
 # [MOV] = Move/rename
-#
+#

conf.py

@@ -1,14 +1,11 @@
-import os
 import re
-import shutil
+import os
 import sys
 from pathlib import Path
 
-import docutils
-import sphinx
 from pygments.lexers import JsonLexer, XmlLexer
-from sphinx.ext import graphviz
 from sphinx.util import logging
+import sphinx
 
 _logger = logging.getLogger(__name__)
 
@@ -19,25 +16,11 @@ _logger = logging.getLogger(__name__)
 project = 'Odoo'
 copyright = 'Odoo S.A.'
 
-# `version` is the version info for the project being documented, acts as replacement for |version|,
+# `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 = 'master'
 
-# `current_branch` is the technical name of the current branch.
-# E.g., saas-15.4 -> saas-15.4; 12.0 -> 12.0, master -> master (*).
-current_branch = version
-# `current_version` is the Odoo version linked to the current branch.
-# E.g., saas-15.4 -> 15.4; 12.0 -> 12; master -> master (*).
-current_version = current_branch.replace('saas-', '').replace('.0', '')
-# `current_major_branch` is the technical name of the major branch before the current branch.
-# E.g., saas-15.4 -> 15.0; 12.0 -> 12.0; master -> master (*).
-current_major_branch = re.sub(r'\.\d', '.0', current_branch.replace('saas-', ''))
-# `current_major_version` is the Odoo version linked to the current major branch.
-# E.g., saas-15.4 -> 15; 12.0 -> 12; master -> master (*).
-current_major_version = current_major_branch.replace('.0', '')
-# (*): We don't care for master.
-
 # The minimal Sphinx version required to build the documentation.
 needs_sphinx = '3.0.0'
 
@@ -65,86 +48,52 @@ exclude_patterns = [
 # See https://docutils.sourceforge.io/docs/ref/rst/roles.html#standard-roles for other roles.
 default_role = 'literal'
 
-
-# Whether scaled down images should be be wrapped in a `<a/>` tag linking to the image file or not.
-html_scaled_image_link = False
-
 # If true, '()' will be appended to :func: etc. cross-reference text
 add_function_parentheses = True
 
 #=== Extensions configuration ===#
 
-source_read_replace_vals = {
-    'BRANCH': current_branch,
-    'CURRENT_BRANCH': current_branch,
-    'CURRENT_VERSION': current_version,
-    'CURRENT_MAJOR_BRANCH': current_major_branch,
-    'CURRENT_MAJOR_VERSION': current_major_version,
-    'GITHUB_PATH': f'https://github.com/odoo/odoo/blob/{version}',
-    'GITHUB_ENT_PATH': f'https://github.com/odoo/enterprise/blob/{version}',
-    'OWL_PATH': f'https://github.com/odoo/owl/blob/master',
-}
-
 # 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_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 = Path('odoo')
 odoo_dir_in_path = False
-
-if not odoo_sources_dirs:
+if not odoo_dir.is_dir():
+    parent_odoo_dir = Path('../odoo')
+    if parent_odoo_dir.is_dir():
+        _logger.info('Using parent dir to find odoo sources')
+        odoo_dir = parent_odoo_dir
+if not odoo_dir.is_dir():
     _logger.warning(
-        "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])},
+        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."
     )
 else:
-    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])
-    sys.path.insert(0, str(odoo_dir))
-    import odoo.addons
-    odoo.addons.__path__.append(str(odoo_dir) + '/addons')
+    sys.path.insert(0, str(odoo_dir.absolute()))
     from odoo import release as odoo_release  # Don't collide with Sphinx's 'release' config option
-    odoo_version = '.'.join(str(s) for s in odoo_release.version_info[:2]).replace('~', '-')  # Change saas~XX.Y to saas-XX.Y
-    odoo_version = 'master' if 'alpha' in odoo_release.version else odoo_version
+    odoo_version = odoo_release.version if 'alpha' not in odoo_release.version else 'master'
     if release != odoo_version:
         _logger.warning(
-            "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},
+            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}`."
         )
     else:
-        _logger.info(
-            "Found Odoo sources in %(directory)s matching documentation version '%(version)s'.",
-            {'directory': odoo_dir, 'version': release},
-        )
+        _logger.info(f"Found Odoo sources directory matching documentation 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',
 
@@ -157,45 +106,29 @@ extensions = [
     # Youtube and Vimeo videos integration (youtube, vimeo directives)
     'embedded_video',
 
-    'custom_admonitions',
+    'exercise_admonition',
 
     # Redirection generator
     'redirects',
 
-    # Content tabs
-    'sphinx_tabs.tabs',
-
-    # Cards
-    'cards',
-
-    # Spoilers
-    'spoilers',
+    # Code switcher (switcher and case directives)
+    'switcher',
 
     # 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/2.3.x/', None),
+    'werkzeug': ('https://werkzeug.palletsprojects.com/en/1.0.x/', None),
 }
 
 github_user = 'odoo'
@@ -209,40 +142,19 @@ sphinx.transforms.i18n.docname_to_domain = (
     sphinx.util.i18n.docname_to_domain
 ) = lambda docname, compact: docname.split('/')[1 if docname.startswith('applications/') else 0]
 
-# 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-16.3': "Odoo Online",
-    'saas-16.2': "Odoo Online",
-    'saas-16.1': "Odoo Online",
-    '16.0': "Odoo 16",
-    'saas-15.2': "Odoo Online",
-    '15.0': "Odoo 15",
-    '14.0': "Odoo 14",
-    '13.0': "Odoo 13",
+supported_languages = {
+    'de': 'Deutsch',
+    'en': 'English',
+    'es': 'Español',
+    'fr': 'Français',
+    'nl': 'Nederlands',
+    'pt_BR': 'Português (BR)',
+    'uk': 'українська',
+    'zh_CN': '简体中文',
 }
 
-# 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': 'DE',
-    'en': 'EN',
-    'es': 'ES',
-    'fr': 'FR',
-    'it': 'IT',
-    'nl': 'NL',
-    'pt_BR': 'PT',
-    'uk': 'UA',
-    'zh_CN': 'ZH (CN)',
-    'zh_TW': 'ZH (TW)'
-}
-
-# The directory in which files holding redirect rules used by the 'redirects' extension are listed.
-redirects_dir = 'redirects/'
-
-sphinx_tabs_disable_tab_closing = True
-sphinx_tabs_disable_css_loading = True
+# The specifications of redirect rules used by the redirects extension.
+redirects_file = 'redirects.txt'
 
 #=== Options for HTML output ===#
 
@@ -263,8 +175,8 @@ html_favicon = os.path.join(html_theme_path[0], html_theme, 'static', 'img', 'fa
 # They are copied after the builtin static files, so a file named "default.css" will overwrite the
 # builtin "default.css".
 html_static_path = ['static']
-html_permalinks = True
-
+html_add_permalinks = '¶'  # Sphinx < 3.5
+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 = []
@@ -286,7 +198,7 @@ latex_elements = {
     'tableofcontents': '',  # no TOC
 
     # Output manually in latex docs
-    'releasename': release,
+    'releasename': '14.0',
 }
 
 latex_additional_files = ['static/latex/odoo.sty']
@@ -306,7 +218,7 @@ latex_documents = [
     ('legal/terms/i18n/partnership_tex_fr',
      'odoo_partnership_agreement_fr.tex', 'Odoo Partnership Agreement (FR)', '', 'howto'),
     ('legal/terms/i18n/terms_of_sale_fr', 'terms_of_sale_fr.tex',
-     'Conditions Générales de Vente Odoo', '', 'howto'),
+     u'Conditions Générales de Vente Odoo', '', 'howto'),
 
     ('legal/terms/i18n/enterprise_tex_nl', 'odoo_enterprise_agreement_nl.tex',
      'Odoo Enterprise Subscription Agreement (NL)', '', 'howto'),
@@ -318,38 +230,14 @@ latex_documents = [
      'Odoo Enterprise Subscription Agreement (ES)', '', 'howto'),
     ('legal/terms/i18n/partnership_tex_es',
      'odoo_partnership_agreement_es.tex', 'Odoo Partnership Agreement (ES)', '', 'howto'),
-
-    ('legal/terms/i18n/enterprise_tex_pt_BR', 'odoo_enterprise_agreement_pt_BR.tex',
-     'Odoo Enterprise Subscription Agreement (PT)', '', 'howto'),
 ]
 
-# List of languages that have legal translations (excluding EN). The keys must be in
-# `languages_names`. These translations will have a link to their versions of the legal
-# contracts, instead of the default EN one. The main legal documents are not part of the
-# translations since they have legal meaning.
-legal_translations = ['de', 'es', 'fr', 'nl', 'pt_BR']
-
 # The name of an image file (relative to this directory) to place at the top of the title page.
 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
@@ -358,34 +246,12 @@ 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.
@@ -417,18 +283,15 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
 
         The entry 'version' is added by Sphinx in the rendering context.
         """
-        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))
-                )
+        # 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')
+            )
+        ]
 
     def _localize():
         """ Add the pairs of (lang, code, url) for the current document in the rendering context.
@@ -438,28 +301,20 @@ def _generate_alternate_urls(app, pagename, templatename, context, doctree):
         The entry 'language' is added by Sphinx in the rendering context.
         """
         _current_lang = app.config.language or 'en'
-        # Replace the context value by its upper-cased value ("FR" instead of "fr")
-        context['language'] = languages_names.get(_current_lang)
-        context['language_code'] = _current_lang
+        # Replace the context value by its translated description ("Français" instead of "french")
+        context['language'] = supported_languages.get(_current_lang)
 
         # If the list of languages is not set, assume that the project has no alternate language
-        _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),
-                    )
-                )
-
-        # Dynamic generation of localized legal doc links
-        context['legal_translations'] = legal_translations
-
+        _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
+        ]
 
     def _build_url(_version=None, _lang=None):
         if app.config.is_remote_build:

content/administration.rst

@@ -18,5 +18,4 @@ These guides provide instructions on how to install, maintain and upgrade Odoo d
 
     administration/install
     administration/maintain
-    administration/upgrade
     administration/odoo_sh

content/administration/install.rst

@@ -4,8 +4,6 @@
 Install
 =======
 
-.. If you add content on this page, remove the redirect rule 'install -> install/install'
-
 .. toctree::
 
     install/install

content/administration/install/cdn.rst

@@ -1,109 +1,80 @@
-=======================================
-Set up a content delivery network (CDN)
-=======================================
+===========================================
+Setting up a Content Delivery Network (CDN)
+===========================================
 
 .. _reference/cdn/keycdn:
 
-Deploying with KeyCDN
-=====================
+Deploying with KeyCDN_
+======================
 
-A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically
-distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content
-Delivery Network)` provides quick, high-quality content delivery for content-heavy websites.
+.. sectionauthor:: Fabien Meghazi
 
-This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website.
+This document will guide you through the setup of a KeyCDN_ account with your
+Odoo powered website.
 
-Create a pull zone in the KeyCDN dashboard
-------------------------------------------
+Step 1: Create a pull zone in the KeyCDN dashboard
+--------------------------------------------------
 
-On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On
-the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN
-(Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone
-Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to
-:guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the
-:guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource
-Locator)`.
+.. image:: cdn/keycdn_create_a_pull_zone.png
+   :class: img-fluid
 
-.. example::
-   Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the
-   actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as
-   well, in place of the Odoo subdomain that was provided to the database.
+When creating the zone, enable the CORS option in the
+:guilabel:`advanced features` submenu. (more on that later)
 
-.. image:: cdn/keycdn-zone.png
-   :align: center
-   :alt: KeyCDN's Zone configuration page.
+.. image:: cdn/keycdn_enable_CORS.png
+   :class: img-fluid
 
-Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all
-settings` button to expand the zone options. This should be the last option on the page. After
-expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is
-:guilabel:`enabled`.
+Once done, you'll have to wait a bit while KeyCDN_ is crawling your website.
 
-Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN
-will indicate that the new zone will be deployed. This can take about 10 minutes.
+.. image:: cdn/keycdn_progressbar.png
+   :class: img-fluid
 
-.. image:: cdn/zone-url.png
-   :align: center
-   :alt: KeyCDN deploying the new Zone.
+.. note:: a new URL has been generated for your Zone, in this case it is
+          ``http://pulltest-b49.kxcdn.com``
 
-.. note::
-   A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is
-   ``pulltest-xxxxx.kxcdn.com``. This value will differ for each database.
+Step 2: Configure the odoo instance with your zone
+--------------------------------------------------
 
-Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps.
+In the Odoo back end, go to the :guilabel:`Website Settings`: menu, then
+activate the CDN support and copy/paste your zone URL in the
+:guilabel:`CDN Base URL` field. This field is only visible and configurable if
+you have developer mode activated.
 
-Configure the Odoo instance with the new zone
----------------------------------------------
+.. image:: cdn/odoo_cdn_base_url.png
+   :class: img-fluid
 
-In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the
-:guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value
-from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and
-configurable when :doc:`Developer Mode <../../applications/general/developer_mode>` is activated.
+Now your website is using the CDN for the resources matching the
+:guilabel:`CDN filters` regular expressions.
 
-.. note::
-   Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one
-   forward slash (`/`) after the :guilabel:`CDN Base URL`.
+You can have a look to the HTML of your website in order to check if the CDN
+integration is properly working.
 
-:guilabel:`Save` the settings when complete.
+.. image:: cdn/odoo_check_your_html.png
+   :class: img-fluid
 
-.. image:: cdn/cdn-base-url.png
-   :align: center
-   :alt: Activate the CDN setting in Odoo.
 
-Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular
-expressions.
+Why should I activate CORS?
+---------------------------
 
-In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced
-as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base
-URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website.
-Look for it's record by searching within the :guilabel:`Network` tab inside of devtools.
+A security restriction in some browsers (Firefox and Chrome at time of writing)
+prevents a remotely linked CSS file to fetch relative resources on this same
+external server.
 
-.. image:: cdn/test-pull.png
-   :align: center
-   :alt: The CDN Base URL can be seen using the inspect function on the Odoo website.
+If you don't activate the CORS option in the CDN zone, the more obvious
+resulting problem on a default Odoo website will be the lack of font-awesome
+icons because the font file declared in the font-awesome CSS won't be loaded on
+the remote server.
 
-Prevent security issues by activating cross-origin resource sharing (CORS)
---------------------------------------------------------------------------
+Here's what you would see on your homepage in such a case:
 
-A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a
-remotely linked CSS file to fetch relative resources on this same external server.
+.. image:: cdn/odoo_font_file_not_loaded.png
+   :class: img-fluid
 
-If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN
-Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font
-Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the
-remote server.
+A security error message will also appear in the browser's console:
 
-When these cross-origin resource issues occur, a security error message similar to the output
-below will appear in the web browser's developer console:
+.. image:: cdn/odoo_security_message.png
+   :class: img-fluid
 
-``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by
-Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the
-requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``
-
-.. image:: cdn/odoo-security-message.png
-   :align: center
-   :alt: Error message populated in the browser console.
-
-Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery
-Network)` settings fixes this issue.
+Enabling the CORS option in the CDN fixes this issue.
 
 .. _KeyCDN: https://www.keycdn.com

content/administration/install/deploy.rst

@@ -7,7 +7,8 @@ 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` recommendations!
+.. warning:: If you are setting up a public server, be sure to check our :ref:`security` recommandations!
+
 
 .. _db_filter:
 
@@ -63,7 +64,6 @@ 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
@@ -72,6 +72,7 @@ in ``/etc/odoo.conf`` set:
   your databases, and to block access to the database management screens.
   See also security_.
 
+
 PostgreSQL
 ==========
 
@@ -97,7 +98,7 @@ Configuration sample
 * Allow tcp connection on localhost
 * Allow tcp connection from 192.168.1.x network
 
-in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:
+in ``/etc/postgresql/9.5/main/pg_hba.conf`` set:
 
 .. code-block:: text
 
@@ -105,7 +106,7 @@ in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:
   host    all             all             127.0.0.1/32            md5
   host    all             all             192.168.1.0/24          md5
 
-in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:
+in ``/etc/postgresql/9.5/main/postgresql.conf`` set:
 
 .. code-block:: text
 
@@ -172,7 +173,7 @@ in Odoo the db_sslmode control the ssl security of the connection
 with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca'
 or 'verify-full'
 
-`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_
+`PostgreSQL Doc <https://www.postgresql.org/docs/current/static/libpq-ssl.html>`_
 
 .. _builtin_server:
 
@@ -195,6 +196,7 @@ be better monitored and resource-restricted.
 
 .. warning:: multiprocessing mode currently isn't available on Windows
 
+
 Worker number calculation
 -------------------------
 
@@ -215,11 +217,11 @@ LiveChat
 --------
 
 In multiprocessing, a dedicated LiveChat worker is automatically started and
-listening on :option:`the gevent port <odoo-bin --gevent-port>` but
+listening on :option:`the longpolling port <odoo-bin --longpolling-port>` but
 the client will not connect to it.
 
 Instead you must have a proxy redirecting requests whose URL starts with
-``/websocket/`` to the gevent port. Other request should be proxied to
+``/longpolling/`` to the longpolling port. Other request should be proxied to
 the :option:`normal HTTP port <odoo-bin --http-port>`
 
 To achieve such a thing, you'll need to deploy a reverse proxy in front of Odoo,
@@ -227,6 +229,8 @@ 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
 --------------------
 
@@ -285,67 +289,59 @@ 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;
-  }
-  map $http_upgrade $connection_upgrade {
-    default upgrade;
-    ''      close;
+   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 ssl;
-    server_name odoo.mycompany.com;
-    proxy_read_timeout 720s;
-    proxy_connect_timeout 720s;
-    proxy_send_timeout 720s;
+   listen 443;
+   server_name odoo.mycompany.com;
+   proxy_read_timeout 720s;
+   proxy_connect_timeout 720s;
+   proxy_send_timeout 720s;
 
-    # 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;
+   # 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;
 
-    # log
-    access_log /var/log/nginx/odoo.access.log;
-    error_log /var/log/nginx/odoo.error.log;
+   # 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;
 
-    # Redirect websocket requests to odoo gevent port
-    location /websocket {
-      proxy_pass http://odoochat;
-      proxy_set_header Upgrade $http_upgrade;
-      proxy_set_header Connection $connection_upgrade;
-      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;
-    }
+   # log
+   access_log /var/log/nginx/odoo.access.log;
+   error_log /var/log/nginx/odoo.error.log;
 
-    # Redirect requests to odoo backend server
-    location / {
-      # 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;
-      proxy_redirect off;
-      proxy_pass http://odoo;
-    }
+   # Redirect longpoll requests to odoo longpolling port
+   location /longpolling {
+   proxy_pass http://odoochat;
+   }
 
-    # common gzip
-    gzip_types text/css text/scss text/plain text/xml application/xml application/json application/javascript;
-    gzip on;
+   # 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;
   }
 
 Odoo as a WSGI Application
@@ -390,109 +386,27 @@ notifications.
 The solutions to support livechat/motifications in a WSGI application are:
 
 * Deploy a threaded version of Odoo (instead of a process-based preforking
-  one) and redirect only requests to URLs starting with ``/websocket/`` to
-  that Odoo, this is the simplest and the websocket URL can double up as the cron
-  instance.
+  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.
 * Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting
-  with ``/websocket/`` to
-  :option:`the gevent port <odoo-bin --gevent-port>`.
+  with ``/longpolling/`` to
+  :option:`the longpolling port <odoo-bin --longpolling-port>`.
 
-.. _deploy/streaming:
+Serving Static Files
+====================
 
-Serving static files and attachments
-====================================
+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.
 
-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 and the
-   :option:`--addons-path <odoo-bin --addons-path>` is ``'/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**. The two git repositories for Community and
-   Enterprise have been cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise`
-   respectively and the :option:`--addons-path <odoo-bin --addons-path>` is
-   ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``.
-
-   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 /opt/odoo;
-           try_files /community/odoo/addons$uri /community/addons$uri /enterprise$uri @odoo;
-           expires 24h;
-       }
-
-.. 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.
+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.
 
+.. 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:
 
@@ -607,7 +521,6 @@ security-related topics:
 
 Blocking Brute Force Attacks
 ----------------------------
-
 For internet-facing deployments, brute force attacks on user passwords are very common, and this
 threat should not be neglected for Odoo servers. Odoo emits a log entry whenever a login attempt
 is performed, and reports the result: success or failure, along with the target login and source IP.
@@ -645,6 +558,9 @@ 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
@@ -707,10 +623,12 @@ 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.
@@ -735,8 +653,8 @@ Here are the supported browsers:
 .. _socat: http://www.dest-unreach.org/socat/
 .. _PostgreSQL connection settings:
 .. _listen to network interfaces:
-    https://www.postgresql.org/docs/12/static/runtime-config-connection.html
+    https://www.postgresql.org/docs/9.6/static/runtime-config-connection.html
 .. _use an SSH tunnel:
-    https://www.postgresql.org/docs/12/static/ssh-tunnels.html
+    https://www.postgresql.org/docs/9.6/static/ssh-tunnels.html
 .. _WSGI: https://wsgi.readthedocs.org/
 .. _POSBox: https://www.odoo.com/page/point-of-sale-hardware#part_2

content/administration/install/email_gateway.rst

@@ -4,22 +4,19 @@ Email gateway
 
 The Odoo mail gateway allows you to inject directly all the received emails in Odoo.
 
-Its principle is straightforward: your SMTP server executes the "mailgate" script for every new
-incoming email.
+Its principle is straightforward: your SMTP server executes the "mailgate" script for every new incoming email.
 
 The script takes care of connecting to your Odoo database through XML-RPC, and send the emails via
 the `MailThread.message_process()` feature.
 
 Prerequisites
 -------------
-
 - Administrator access to the Odoo database.
 - Your own mail server such as Postfix or Exim.
 - Technical knowledge on how to configure an email server.
 
 For Postfix
 -----------
-
 In you alias config (:file:`/etc/aliases`):
 
 .. code-block:: text
@@ -36,7 +33,6 @@ In you alias config (:file:`/etc/aliases`):
 
 For Exim
 --------
-
 .. code-block:: text
 
    *: |/odoo-directory/addons/mail/static/scripts/odoo-mailgate.py -d <database-name> -u <userid> -p <password>
@@ -48,4 +44,4 @@ For Exim
 
 .. tip::
    If you don't have access/manage your email server, use :ref:`inbound messages
-   <email_communication/inbound_messages>`.
+   <discuss/email_servers/inbound_messages>`.

content/administration/maintain.rst

@@ -6,13 +6,9 @@ Maintain
 
 .. toctree::
 
-    maintain/domain_names
-    maintain/azure_oauth
-    maintain/google_oauth
-    maintain/mailjet_api
     maintain/update
+    maintain/db_upgrade
     maintain/enterprise
     maintain/hosting_changes
-    maintain/odoo_online
-    maintain/on_premise
+    maintain/db_premise
     maintain/supported_versions

content/administration/maintain/azure_oauth.rst

@@ -1,220 +0,0 @@
-=======================================================
-Connect Microsoft Outlook 365 to Odoo using Azure OAuth
-=======================================================
-
-Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order to send and receive
-secure emails from a custom domain, all that is required is to configure a few settings on the
-Azure platform and on the back end of the Odoo database. This configuration works with either a
-personal email address or an address created by a custom domain.
-
-.. seealso::
-   `Microsoft Learn: Register an application with the Microsoft identity platform
-   <https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app>`_
-
-.. seealso::
-   - :doc:`/applications/general/auth/azure`
-   - :doc:`/applications/productivity/calendar/outlook`
-
-Setup in Microsoft Azure Portal
-===============================
-
-Create a new application
-------------------------
-
-To get started, go to `Microsoft's Azure Portal <https://portal.azure.com/>`_. Log in with the
-:guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the
-personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings
-will need to connect and perform the following configuration. Next, navigate to the section
-labeled :guilabel:`Manage Azure Active Directory`.
-
-Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App
-registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to
-`Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select
-:guilabel:`Accounts in any organizational directory (Any Azure AD directory - Multitenant) and
-personal Microsoft accounts (e.g. Skype, Xbox)`.
-
-Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input
-`https://<odoo base url>/microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL
-is the canonical domain at which your Odoo instance can be reached in the URL field.
-
-.. example::
-   *mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the database's subdomain,
-   assuming it's hosted on Odoo.com
-
-After the URL has been added to the field, :guilabel:`Register` the application so it is created.
-
-API permissions
----------------
-
-The :guilabel:`API permissions` should be set next. Odoo will need specific API permissions to be
-able to read (IMAP) and send (SMTP) emails in the Microsoft 365 setup. First, click the
-:guilabel:`API permissions` link, located in the left menu bar. Next, click on the :guilabel:`(+)
-Add a Permission` button and select :guilabel:`Microsoft Graph` under :guilabel:`Commonly Used
-Microsoft APIs`. After, select the :guilabel:`Delegated Permissions` option.
-
-In the search bar, search for the following :guilabel:`Deregulated permissions` and click
-:guilabel:`Add permissions` for each one:
-
-- :guilabel:`SMTP.Send`
-- :guilabel:`IMAP.AccessAsUser.All`
-
-.. note::
-   The :guilabel:`User.Read` permission will be added by default.
-
-.. image:: azure_oauth/permissions.png
-   :align: center
-   :alt: API permissions needed for Odoo integration are listed under the Microsoft Graph.
-
-Assign users and groups
-=======================
-
-After adding the API permissions, navigate back to the :guilabel:`Overview` of the
-:guilabel:`Application` in the top of the left sidebar menu.
-
-Now, add users to this application. Under the :guilabel:`Essentials` overview table, click on the
-link labeled :guilabel:`Managed Application in Local Directory`, or the last option on the bottom
-right-hand side of the table.
-
-.. image:: azure_oauth/managed-application.png
-   :align: center
-   :alt: Add users/groups by clicking the Managed application in local directory link for the
-         created application.
-
-In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click on :guilabel:`(+) Add
-User/Group`. Depending on the account, either a :guilabel:`Group` and a :guilabel:`User` can be
-added, or only :guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` to be
-added.
-
-Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None Selected` and add the users
-or group of users that will be sending emails from the :guilabel:`Microsoft account` in Odoo.
-:guilabel:`Add` the users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to the
-application.
-
-Create credentials
-------------------
-
-Now that the Microsoft Azure app is set up, credentials need to be created for the Odoo setup.
-These include the :guilabel:`Client ID` and :guilabel:`Client Secret`. To start, the
-:guilabel:`Client ID` can be copied from the :guilabel:`Overview` page of the app. The
-:guilabel:`Client ID` or :guilabel:`Application ID` is located under the :guilabel:`Display Name`
-in the :guilabel:`Essentials` overview of the app.
-
-.. image:: azure_oauth/application-id.png
-   :align: center
-   :alt: Application/Client ID located in the Overview of the app.
-
-Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this value, click on
-:guilabel:`Certificates & Secrets` in the left sidebar menu. Then, a :guilabel:`Client Secret`
-needs to be produced. In order to do this, click on the :guilabel:`(+) New Client Secret` button.
-
-A window on the right will populate with a button labeled :guilabel:`Add a client secret`. Under
-:guilabel:`Description`, type in `Odoo Fetchmail` or something recognizable, and then set the
-:guilabel:`expiration date`.
-
-.. important::
-   A new :guilabel:`Client Secret` will need to be produced and configured if the first one
-   expires. In this event, there could be an interruption of service, so the expiration date should
-   be noted and set to the furthest possible date.
-
-Next, click on :guilabel:`Add` when these two values are entered. A :guilabel:`Client Secret Value`
-and :guilabel:`Secret ID` will be created. It is important to copy the :guilabel:`Value` or
-:guilabel:`Client Secret Value` into a notepad as it will become encrypted after leaving this page.
-The :guilabel:`Secret ID` is not needed.
-
-.. image:: azure_oauth/secretvalue.png
-   :align: center
-   :alt: Client Secret Value or Value in the app's credentials.
-
-After these steps, the following items should be ready to be set up in Odoo:
-
-- A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)
-- A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)
-
-This completes the setup on the :guilabel:`Microsoft Azure Portal` side.
-
-Setup in Odoo
-=============
-
-Enter Microsoft Outlook credentials
------------------------------------
-
-First, open the Odoo database and navigate to the :guilabel:`Apps` module. Then, remove the
-:guilabel:`Apps` filter from the search bar and type in `Outlook`. After that, install the module
-called :guilabel:`Microsoft Outlook`.
-
-Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss`
-section, ensure that the checkbox for :guilabel:`Custom Email Servers` is checked. This populates
-a new option for :guilabel:`Outlook Credentials`.
-
-:guilabel:`Save` the progress.
-
-Then, copy and paste the :guilabel:`Client ID` (Application ID) and :guilabel:`Client Secret
-(Client Secret Value)` into the respective fields and :guilabel:`Save` the settings.
-
-.. image:: azure_oauth/outlookcreds.png
-   :align: center
-   :alt: Outlook Credentials in Odoo General Settings.
-
-Configure outgoing email server
--------------------------------
-
-On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email Servers` setting,
-click the :guilabel:`Outgoing Email Servers` link to configure the Microsoft account.
-
-Then, create a new email server and check the box for :guilabel:`Outlook`. Next, fill in the
-:guilabel:`Name` (it can be anything) and the Microsoft Outlook email :guilabel:`Username`.
-
-If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address
-<email_communication/default>`.
-
-Then, click on :guilabel:`Connect your Outlook account`.
-
-A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the
-appropriate email address that is being configured in Odoo.
-
-.. image:: azure_oauth/verify-outlook.png
-   :align: center
-   :alt: Permission page to grant access between newly created app and Odoo.
-
-Then, allow Odoo to access the Microsoft account by clicking on :guilabel:`Yes`. After this, the
-page will navigate back to the newly configured :guilabel:`Outgoing Mail Server` in Odoo. The
-configuration automatically loads the :guilabel:`token` in Odoo, and a tag stating
-:guilabel:`Outlook Token Valid` appears in green.
-
-.. image:: azure_oauth/outlook-token.png
-   :align: center
-   :alt: Valid Outlook Token indicator.
-
-Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database
-can now send safe, secure emails through Microsoft Outlook using OAuth authentication.
-
-Multiple user configuration
-~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Each user should have a separate server set up. The :guilabel:`from-filter` should be set so that
-only the user's email is sent from that server. In other words, only a user with an email address
-that matches the set :guilabel:`from-filter` is able to use this server.
-
-After setting the :guilabel:`from-filter`, set up a fallback email account to allow for the sending
-of :guilabel:`notifications`. The fallback email must be configured as a :guilabel:`general
-transactional server`. The :guilabel:`mail.default.from` system parameter must be set to the
-:guilabel:`username` of the general transactional server account. For more information see
-:ref:`Use a default email address <email_communication/default>`.
-
-.. note::
-   The :guilabel:`System Parameters` can be accessed by activating
-   :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical
-   --> Parameters --> System Parameters` menu.
-
-Configure incoming email server
--------------------------------
-
-The incoming account should be configured in a similar way to the outgoing email account. Navigate
-to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a
-new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and
-enter the :guilabel:`Microsoft Outlook username`.  Click on :guilabel:`Connect your Outlook
-account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the
-account. The account should be ready to receive email to the Odoo database.
-
-.. seealso::
-   :doc:`../../applications/general/email_communication/email_servers`

content/administration/maintain/db_premise.rst

@@ -0,0 +1,179 @@
+
+.. _db_premise:
+
+===============================
+On-premises Database management
+===============================
+
+Register a database
+===================
+
+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
+(Odoo 10).
+
+Registration Error Message
+--------------------------
+
+If you are unable to register your database, you will likely encounter this
+message:
+
+.. image:: media/error_message_sub_code.png
+    :align: center
+    :alt: Something went wrong while registering your database,
+          you can try again or contact Odoo Help
+
+Solutions
+'''''''''
+
+* Do you have a valid Enterprise subscription?
+
+  * Check if your subscription details get the tag "In Progress" on
+    your `Odoo Account
+    <https://accounts.odoo.com/my/subscription>`__ or with your Account Manager
+
+* Have you already linked a database with your subscription reference?
+
+  * You can link only one database per subscription.
+    (Need a test or a development database? `Find a partner
+    <https://www.odoo.com/partners>`__)
+
+  * 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
+        :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
+        :align: center
+
+
+* Do you have the updated version of Odoo 9?
+
+  * From July 2016 onward, Odoo 9 now automatically change the uuid of a
+    duplicated database; a manual operation is no longer required.
+
+  * If it's not the case, you may have multiple databases sharing the same
+    UUID. Please check on your `Odoo Contract
+    <https://accounts.odoo.com/my/subscription>`__, a short message will appear
+    specifying which database is problematic:
+
+    .. image:: media/unlink_db_name_collision.png
+        :align: center
+
+
+    In this case, you need to change the UUID on your test databases to solve this
+    issue. You will find more information about this in :ref:`this section <duplicate_premise>`.
+
+    For your information, we identify database with UUID. Therefore, each database
+    should have a distinct UUID to ensure that registration and invoicing proceed
+    effortlessly for your and for us.
+
+* Check your network and firewall settings
+
+  * The Update notification must be able to reach Odoo's subscription
+    validation servers. In other words, make sure that the Odoo server is able
+    to open outgoing connections towards:
+
+      * services.odoo.com on port 443 (or 80)
+      * services.openerp.com on port 443 (or 80) for older deployments
+
+  * Once you activated your database, you must keep these ports open, as the
+    Update notification runs once a week.
+
+
+
+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
+    :align: center
+    :alt: This database will expire in X days, you
+          have more users than your subscription allows
+
+
+When the message appears you have 30 days before the expiration.
+The countdown is updated everyday.
+
+Solutions
+'''''''''
+
+- **Add more users** on your subscription: follow the link and Validate
+  the upsell quotation and pay for the extra users.
+- **Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_
+  and **Reject** the upsell quotation.
+
+Once your database has the correct number of users, the expiration message
+will disappear automatically after a few days, when the next verification occurs.
+We understand that it can be a bit frightening to see the countdown,
+so you can :ref:`force an Update Notification <force_ping>`  to make the message disappear
+right away.
+
+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
+    :align: center
+    :alt: This database has expired.
+
+
+This **blocking** message appears after a non-blocking message that lasts 30 days.
+If you fail to take action before the end of the countdown, the database is expired.
+
+Solutions
+'''''''''
+
+* Renew your subscription: follow the link and renew your subscription - note that
+    if you wish to pay by Wire Transfer, your subscription will effectively be renewed
+    only when the payment arrives, which can take a few days. Credit card payments are
+    processed immediately.
+* Contact our `Support <https://www.odoo.com/help>`__
+
+None of those solutions worked for you? Please contact our
+`Support <https://www.odoo.com/help>`__
+
+
+.. _force_ping:
+
+.. _duplicate_premise:
+
+Duplicate a database
+====================
+
+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
+    :align: center
+
+
+When you duplicate a local database, it is **strongly** advised to change
+the duplicated database's uuid (Unniversally Unique Identifier), since this
+uuid is how your database identifies itself with our servers. Having two
+databases with the same uuid could result in invoicing problems or registration
+problems down the line.
+
+.. note:: From July 2016 onward, Odoo 9 now automatically change the uuid of a
+    duplicated database; a manual operation is no longer required.
+
+The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical -->
+System Parameters`, we advise you to use a `uuid generator <https://www.uuidtools.com>`_ or to
+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
+    :align: center

content/administration/maintain/db_upgrade.rst

@@ -0,0 +1,413 @@
+
+.. |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:
+
+================
+Versions upgrade
+================
+
+.. _db-upgrade/overview:
+
+Overview
+========
+
+.. _db-upgrade/process:
+
+The upgrade process
+-------------------
+
+This documentation is for our *On-Premise* (self-hosted) and *Odoo.sh* customers.
+
+.. _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 your `database manager <https://www.odoo.com/my/databases>`_.
+
+.. _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
+<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 <supported_versions>`.

content/administration/maintain/domain_names.rst

@@ -1,366 +0,0 @@
-============
-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/indexing:
-
-Indexing of domain names by search engines
-------------------------------------------
-
-Search engines, such as Google and Bing, rely on web crawlers (:dfn:`robots that explore and analyze
-the web`) to index all websites and their related domain names. These crawlers discover new URLs
-thanks to links on known web pages. As a result, search engines should index domain names
-automatically after a while, as long as their URLs are mentioned elsewhere on the Internet.
-
-Improving the appearance and positioning of web pages on search engines is a practice named "Search
-Engine Optimization" (SEO).
-
-.. tip::
-   Adding relevant content, optimizing metadata, and building high-quality backlinks can all help
-   improve a website's search engine visibility.
-
-Some search engines provide tools for web admins, such as
-`Google Search Console <https://search.google.com/search-console>`_ and
-`Bing Webmaster Tools <https://www.bing.com/webmasters>`_, to help you analyze and improve your
-page ranking. To use these services, you must prove that you are the owner of your domain name. One
-way to verify the ownership of your domain name is by adding a DNS record. You can do this for
-:ref:`domain names registered with Odoo <domain-name/odoo-manage>` and for domain names managed by
-other providers.
-
-.. seealso::
-   - :doc:`/applications/websites/website/pages/seo`
-   - `Google Search Console Help - Verify your site ownership <https://support.google.com/webmasters/answer/9008080>`_
-   - `Bing Webmaster Tools - Add and Verify site <https://www.bing.com/webmasters/help/add-and-verify-site-12184f8b>`_
-
-.. _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.
-   - This offer doesn't include any mailbox. However, you can :ref:`configure your MX records
-     <domain-name/odoo-manage>` to use your own email server or solution such as Google Workspace.
-
-To do so, go to :menuselection:`Website --> 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-menu.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 domain of another website rather than
-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>`_ 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

@@ -41,7 +41,7 @@ On Linux, using an installer
   .. code-block:: console
 
     $ sudo dpkg -i <path_to_enterprise_deb>
-
+  
 * Update your database to the enterprise packages using
 
   .. code-block:: console

content/administration/maintain/google_oauth.rst

@@ -1,219 +0,0 @@
-========================================
-Connect Gmail to Odoo using Google OAuth
-========================================
-
-Odoo is compatible with Google's OAuth for Gmail. In order to send secure emails from a custom
-domain, all that is required is to configure a few settings on Google's *Workspace* platform, as
-well as on the back end of the Odoo database. This configuration works by using either a personal
-email address or an address created by a custom domain.
-
-.. tip::
-   For more information, visit `Google's documentation
-   <https://support.google.com/cloud/answer/6158849>`_ on setting up OAuth.
-
-.. seealso::
-   - :doc:`/applications/general/auth/google`
-   - :doc:`/applications/productivity/calendar/google`
-
-Setup in Google
-===============
-
-Create a new project
---------------------
-
-To get started, go to the `Google API Console <https://console.developers.google.com>`_. Log in
-with your *Google Workspace* account if you have one, otherwise log in with your personal Gmail
-account (this should match the email address you want to configure in Odoo).
-
-After that, click on :guilabel:`Create Project`, located on the far right of the :guilabel:`OAuth
-consent screen`. If a project has already been created in this account, then the :guilabel:`New
-Project` option will be located on the top right under the :guilabel:`Select a project` drop-down
-menu.
-
-On the :menuselection:`New Project` screen, rename the :guilabel:`Project name` to `Odoo` and
-browse for the :guilabel:`Location`. Set the :guilabel:`Location` as the *Google Workspace
-organization*. If you are using a personal Gmail account, then leave the :guilabel:`Location` as
-:guilabel:`No Organization`.
-
-.. image:: google_oauth/new-project.png
-   :align: center
-   :alt: Project Name and Location for Google OAuth.
-
-Click on :guilabel:`Create` to finish this step.
-
-OAuth consent screen
---------------------
-
-If the page doesn't redirect to the :menuselection:`User Type` options, click on :guilabel:`OAuth
-consent screen` in the left menu.
-
-Under :guilabel:`User Type` options, select the appropriate :guilabel:`User Type`, and then click on
-:guilabel:`Create` again, which will finally navigate to the :menuselection:`Edit app registration`
-page.
-
-.. warning::
-   *Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may
-   require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account
-   allows for **Internal** User Type to be used.
-
-   Note, as well, that while the API connection is in the *External* testing mode, then no approval is
-   necessary from Google. User limits in this testing mode is set to 100 users.
-
-Edit app registration
----------------------
-
-Next we will configure the app registration of the project.
-
-On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App information` section, enter
-`Odoo` in the :guilabel:`App name` field. Select the organization's email address under the
-:guilabel:`User support` email field.
-
-Next, under :menuselection:`App Domain --> Authorized domains`, click on :guilabel:`Add Domain` and
-enter `odoo.com`.
-
-After that, under the :guilabel:`Developer contact information` section, enter the organization's
-email address. Google uses this email address to notify the organization about any changes to your
-project.
-
-Next, click on the :guilabel:`Save and Continue` button. Then, skip the :menuselection:`Scopes` page
-by scrolling to the bottom and clicking on :guilabel:`Save and Continue`.
-
-If continuing in testing mode (External), add the email addresses being configured under the
-:guilabel:`Test users` step, by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and
-Continue` button. A summary of the app registration appears.
-
-Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to finish setting up the
-project.
-
-Create Credentials
-------------------
-
-Now that the project is set up, credentials should be created, which includes the *Client ID* and
-*Client Secret*. First, click on :guilabel:`Credentials` in the left sidebar menu.
-
-Then, click on :guilabel:`Create Credentials` in the top menu and select :guilabel:`OAuth client ID`
-from the dropdown menu.
-
-- Under :guilabel:`Application Type`, select :guilabel:`Web Application` from the dropdown menu.
-- In the :guilabel:`Name` field, enter `Odoo`.
-- Under the :guilabel:`Authorized redirect URIs` label, click the button :guilabel:`ADD URI`, and
-  then input `https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1` field.
-  Be sure to replace the *yourdbname* part of the URL with the actual Odoo database name.
-- Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID` and :guilabel:`Client
-  Secret`. Finally, copy each generated value for later use when configuring in Odoo, and then
-  navigate to the Odoo database.
-
-.. image:: google_oauth/client-credentials.png
-   :align: center
-   :alt: Client ID and Client Secret for Google OAuth.
-
-Setup in Odoo
-=============
-
-Enter Google Credentials
-------------------------
-
-First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps`
-filter from the search bar and type in `Google`. Install the module called :guilabel:`Google
-Gmail`.
-
-Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss`
-section, ensure that the checkbox for :guilabel:`Custom Email Servers` or :guilabel:`External Email
-Servers` is checked. This populates a new option for :guilabel:`Gmail Credentials` or :guilabel:`Use
-a Gmail Sever`. Then, copy and paste the respective values into the :guilabel:`Client ID` and
-:guilabel:`Client Secret` fields and :guilabel:`Save` the settings.
-
-Configure outgoing email server
--------------------------------
-
-To configure the external Gmail account, return to the top of the :guilabel:`Custom Email Servers`
-setting and then click the :guilabel:`Outgoing Email Servers` link.
-
-.. image:: google_oauth/outgoing-servers.png
-   :align: center
-   :alt: Configure Outgoing Email Servers in Odoo.
-
-Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email server, and fill in the
-:guilabel:`Name`, :guilabel:`Description`, and the email :guilabel:`Username` (if required).
-
-Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` (under the
-:guilabel:`Authenticate with` or :guilabel:`Connection` section). Finally, click on
-:guilabel:`Connect your Gmail Account`.
-
-A new window labeled :guilabel:`Google` opens to complete the authorization process. Select the
-appropriate email address that is being configured in Odoo.
-
-If the email address is a personal account, then an extra step pops up, so click
-:guilabel:`Continue` to allow the verification and connect the Gmail account to Odoo.
-
-Then, allow Odoo to access the Google account by clicking on :guilabel:`Continue` or
-:guilabel:`Allow`. After that, the page navigates back to the newly configured outgoing email
-server in Odoo. The configuration automatically loads the token in Odoo, and a tag stating
-:guilabel:`Gmail Token Valid` appears in green.
-
-.. image:: google_oauth/green-token.png
-   :align: center
-   :alt: Configure Outgoing Email Servers in Odoo.
-
-Finally, :guilabel:`Test the Connection`. A confirmation message should appear. The Odoo database
-can now send safe, secure emails through Google using OAuth authentication.
-
-Google OAuth FAQ
-================
-
-Production VS Testing Publishing Status
----------------------------------------
-
-Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of
-:guilabel:`Testing`) will display the following warning message:
-
-.. image:: google_oauth/published-status.png
-   :align: center
-   :alt: OAuth is Limited to 100 Sensitive Scope Logins.
-
-To correct this warning, navigate to the `Google API Platform
-<https://console.cloud.google.com/apis/credentials/consent>`_. If the :guilabel:`Publishing status`
-is :guilabel:`In Production`, click :guilabel:`Back to Testing` to correct the issue.
-
-No Test Users Added
--------------------
-
-If no test users are added to the OAuth consent screen, then a 403 access denied error will
-populate.
-
-.. image:: google_oauth/403-error.png
-   :align: center
-   :alt: 403 Access Denied Error.
-
-To correct this error, return to the :guilabel:`OAuth consent screen` under :guilabel:`APIs &
-Services` and add test user(s) to the app. Add the email that you are configuring in Odoo.
-
-Gmail Module not updated
-------------------------
-
-If the *Google Gmail* module in Odoo has not been updated to the latest version, then a
-:guilabel:`Forbidden` error message populates.
-
-.. image:: google_oauth/forbidden-error.png
-   :align: center
-   :alt: Forbidden you don't have the permission to access the requested resource.
-
-To correct this error, go to the :menuselection:`Apps` module and clear out the search terms. Then,
-search for `Gmail` or `Google` and upgrade the :guilabel:`Google Gmail` module. Finally, click
-on the three dots on the upper right of the module and select :guilabel:`Upgrade`.
-
-Application Type
-----------------
-
-When creating the credentials (OAuth *Client ID* and *Client Secret*), if :guilabel:`Desktop App` is
-selected for the :guilabel:`Application Type`, an :guilabel:`Authorization Error` appears.
-
-.. image:: google_oauth/error-400.png
-   :align: center
-   :alt: Error 400 Redirect URI Mismatch.
-
-To correct this error, delete the credentials already created and create new credentials, selecting
-:guilabel:`Web Application` for the :guilabel:`Application Type`. Then, under :guilabel:`Authorized
-redirect URIs`, click :guilabel:`ADD URI` and type:
-`https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure to replace *yourdbname*
-in the URL with the Odoo database name.

content/administration/maintain/hosting_changes.rst

@@ -11,6 +11,8 @@ 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.**
@@ -18,11 +20,6 @@ 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
 ===========================
 
@@ -48,40 +45,17 @@ From Odoo Online to Odoo.sh
 From Odoo.sh to Odoo Online
 ===========================
 
-#. Uninstall all the **non-standard apps**.
-#. `Create a support ticket <https://www.odoo.com/help>`_ and include the following:
+.. warning:: Odoo Online is not compatible with **non-standard apps**.
 
-   - Your subscription number
-   - The URL you want to use for your database (e.g., `example.odoo.com`)
-   - Which branch you want to migrate
-   - In which region you want to be hosted:
-
-     - Americas
-     - Europe
-     - Asia
-
-   - Which user(s) will be the administrator(s)
-   - When (and in which timezone) you want the database to be up and running
-
-#. 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.
-#. All done!
-
-.. important::
-   - Odoo Online is not compatible with **non-standard apps**.
-   - Make sure to uninstall all the **non-standard apps** in a staging build before doing it in your
-     production build.
-
-.. note::
-   - Make sure you select the **region** that is closest to your users to reduce latency.
-   - The future **administrator(s)** must have an odoo.com account.
-   - The specific **date and time** at which you want the database to be up and running are mainly
-     helpful to organize the switch from the odoo.sh server to the Odoo Online servers.
-   - Databases are **not reachable** during their migration.
-   - **If you have time constraints, contact us earlier to schedule the transfer**.
+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).
+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!
 
 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/mailjet_api.rst

@@ -1,218 +0,0 @@
-===========
-Mailjet API
-===========
-
-Odoo is compatible with Mailjet's :abbr:`API (Application Programming Interface)` for mass mailing.
-Set up a dedicated mass mailing server through Mailjet by configuring settings in the Mailjet
-account and the Odoo database. In some circumstances, settings need to be configured on the custom
-domain's :abbr:`DNS (Domain Name System)` settings as well.
-
-Set up in Mailjet
-=================
-
-Create API credentials
-----------------------
-
-To get started, sign in to the `Mailjet Account Information <https://app.mailjet.com/account>`_
-page. Next, navigate to the :guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and
-SEND API Settings`.
-
-.. image:: mailjet_api/api-settings.png
-   :align: center
-   :alt: SMTP and Send API Settings link in the Senders & Domains section of Mailjet.
-
-Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings onto a notepad.
-They can be found under the :guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple
-Mail Transfer Protocol)` configuration settings include the server address, the security option
-needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)`), and the
-port number. The settings are needed to configure Mailjet in Odoo, which is covered in the
-:ref:`last section <maintain/mailjet-api/odoo-setup>`.
-
-.. seealso::
-   `Mailjet: How can I configure my SMTP parameters?
-   <https://documentation.mailjet.com/hc/articles/360043229473>`_
-
-.. important::
-   Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See reference here
-   <email_servers/restriction>`.
-
-.. image:: mailjet_api/smtp-config.png
-   :align: center
-   :alt: SMTP configuration from Mailjet.
-
-Next, click on the button labeled :guilabel:`Retrieve your API credentials` to retrieve the Mailjet
-API credentials.
-
-Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key to a notepad, as this
-serves as the :guilabel:`Username` in the Odoo configuration. Next, click on the
-:guilabel:`Generate Secret Key` button to generate the :guilabel:`Secret Key`. Copy this key to a
-notepad, as this serves as the :guilabel:`Password` in the Odoo configuration.
-
-Add verified sender address(es)
--------------------------------
-
-The next step is to add a sender address or a domain to the Mailjet account settings so that the
-email address or domain is approved to send emails using Mailjet's servers. First, navigate to the
-`Mailjet Account Information <https://app.mailjet.com/account>`_ page. Next, click on the
-:guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section.
-
-.. image:: mailjet_api/add-domain-email.png
-   :align: center
-   :alt: Add a sender domain or address in the Mailjet interface.
-
-Determine if a sender's email address or the entire domain needs to be added to the Mailjet
-settings. It may be easier to configure the domain as a whole if :abbr:`DNS (Domain Name System)`
-access is available. Jump to the :ref:`Add a domain <maintain/mailjet-api/add-domain>` section for
-steps on adding the domain.
-
-.. note::
-   Either all email addresses of the Odoo database users who are sending emails using Mailjet's
-   servers need to be configured or the domain(s) of the users' email addresses can be configured.
-
-By default, the email address originally set up in the Mailjet account is added as a trusted
-sender. To add another email address, click on the button labeled :guilabel:`Add a sender address`.
-Then, add the email address that is configured to send from the custom domain.
-
-At minimum the following email addresses should be set up in the provider and verified in Mailjet:
-
-- notifications\@yourdomain.com
-- bounce\@yourdomain.com
-- catchall\@yourdomain.com
-
-.. note::
-   Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use
-   the :guilabel:`mail.catchall.domain` system parameter.
-
-After that, fill out the :guilabel:`Email Information` form, making sure to select the appropriate
-email type: transactional email or mass emails. After completing the form, an activation email is
-sent to the email address and the trusted sender can be activated.
-
-It is recommended to set up the :abbr:`SPF (Sender Policy Framework)`/:abbr:`DKIM (DomainKeys
-Identified Mail)`/:abbr:`DMARC (Domain-based Message Authentication, Reporting, and
-Conformance)` settings on the domain of the sender.
-
-.. seealso::
-   `Mailjet's SPF/DKIM/DMARC documentation <https://documentation.mailjet.com/hc/articles/
-   360042412734-Authenticating-Domains-with-SPF-DKIM>`_
-
-.. important::
-   If the database is not using a custom domain, then in order to verify the sender's address, a
-   temporary alias (of the three email addresses mentioned above) should be set up in Odoo CRM to
-   create a lead. Then, the database is able to receive the verification email and verify the
-   accounts.
-
-.. _maintain/mailjet-api/add-domain:
-
-Add a domain
-------------
-
-By adding an entire domain to the Mailjet account, all the sender addresses related to that domain
-are automatically validated for sending emails using Mailjet servers. First, navigate to the
-`Mailjet Account Information <https://app.mailjet.com/account>`_ page. Next, click on
-:guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section.
-Then, click on :guilabel:`Add domain` to add the custom domain.
-
-.. note::
-   The domain needs to be added to the Mailjet account and then validated through the :abbr:`DNS
-   (Domain Name System)`.
-
-After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and click
-:guilabel:`Continue`.
-
-After adding the domain, a validation page will populate. Unless the Odoo database is on-premise
-(in which case, choose :guilabel:`Option 1`), choose :guilabel:`Option 2: Create a DNS Record`.
-Copy the TXT record information to a notepad and then navigate to the domain's :abbr:`DNS (Domain
-Name System)` provider to complete validation.
-
-.. image:: mailjet_api/host-value-dns.png
-   :align: center
-   :alt: The TXT record information to input on the domain's DNS.
-
-Setup in the domain's DNS
-~~~~~~~~~~~~~~~~~~~~~~~~~
-
-After getting the TXT record information from the Mailjet account, add a TXT record to the domain's
-:abbr:`DNS (Domain Name System)`. This process varies depending on the :abbr:`DNS (Domain Name
-System)` provider. Consult the provider for specific configuration processes. The TXT record
-information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste these into
-the corresponding fields in the TXT record.
-
-Return to Mailjet account information
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-After adding the TXT record to the domain's :abbr:`DNS (Domain Name System)`, navigate back to the
-Mailjet account. Then, navigate to :menuselection:`Account Information --> Add a Sender Domain or
-Address`, click the gear icon next to :guilabel:`Domain`, and select :guilabel:`Validate`.
-
-This action can also be done by going to the `Sender domains & addresses <https://app.mailjet.com/
-account/sender>`_ page on the Mailjet account information and clicking on :guilabel:`Manage`.
-
-Next, click :guilabel:`Check Now` to validate the TXT record that was added on the domain. A
-success screen will appear if the domain is configured correctly.
-
-.. image:: mailjet_api/check-dns.png
-   :align: center
-   :alt: Check DNS record in Mailjet.
-
-After successfully setting up the domain, there is an option to :guilabel:`Authenticate this domain
-(SPF/DKIM)`. This button populates :abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys
-Identified Mail) records to input into the :abbr:`DNS (Domain Name System)` provider.
-
-.. seealso::
-   `Mailjet's SPF/DKIM/DMARC documentation <https://documentation.mailjet.com/hc/articles/
-   360042412734-Authenticating-Domains-with-SPF-DKIM>`_
-
-.. image:: mailjet_api/authenticate.png
-   :align: center
-   :alt: Authenticate the domain with SPF/DKIM records in Mailjet.
-
-.. _maintain/mailjet-api/odoo-setup:
-
-Set up in Odoo
-==============
-
-To complete the setup, navigate to the Odoo database and go to the :guilabel:`Settings`. With
-:ref:`developer-mode` turned on, go to the :menuselection:`Technical Menu --> Email --> Outgoing
-Mail Servers`. Then, create a new outgoing server configuration by clicking on the
-:guilabel:`Create` button.
-
-Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or 465), and `Security
-(SSL/TLS)` that was copied earlier from the Mailjet account. They can also be found `here
-<https://app.mailjet.com/account/setup>`_. It is recommended to use :abbr:`SSL (Secure Sockets
-Layer)`/:abbr:`TLS (Transport Layer Security)` even though Mailjet may not require it.
-
-For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the :guilabel:`Password`, input
-the :guilabel:`SECRET KEY` that was copied from the Mailjet account to the notepad earlier. These
-settings can be found on :menuselection:`Mailjet -->  Account Settings --> SMTP and SEND API
-Settings`.
-
-Then, if the Mailjet server is used for mass emailing, set the :guilabel:`Priority` value higher
-than that of any transactional email server(s). Finally, save the settings and :guilabel:`Test the
-Connection`.
-
-.. image:: mailjet_api/server-settings.png
-   :align: center
-   :alt: Odoo outgoing email server settings.
-
-.. important::
-   In order for the notifications feature to work using Mailjet, there are three settings that need
-   to be set in Odoo.
-
-   #. The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended
-      to set it as a domain and not a full email address. It should match the domain in the two
-      proceeding steps. More information can be referenced :ref:`here
-      <email_communication/from_filter>`.
-   #. The :guilabel:`mail.default.from` system parameter must have the value
-      `notifications\@yourdomain.com`.
-   #. The :guilabel:`mail.default.from_filter` system parameter must have the value
-      `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there
-      isn't one, then use the :guilabel:`mail.catchall.domain` system parameter.
-
-   For more information see :ref:`Using a default email address <email_communication/default>`.
-
-   The :guilabel:`System Parameters` can be accessed by activating
-   :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical
-   --> Parameters --> System Parameters` menu.
-
-Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass
-mailing or transactional emails!

content/administration/maintain/odoo_online.rst

@@ -1,157 +0,0 @@
-===============================
-Odoo Online 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
-:guilabel:`My Databases`.
-
-.. image:: odoo_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 to connect as the administrator of the database that changes will be made on.
-
-.. image:: odoo_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 that changes will be made on by clicking on the gear
-icon.
-
-Several actions are available:
-
-- :ref:`odoo_online/upgrade`
-- :ref:`odoo_online/duplicate`
-- :ref:`odoo_online/rename`
-- :ref:`odoo_online/download`
-- :ref:`odoo_online/domains`
-- :ref:`odoo_online/tags`
-- :ref:`odoo_online/delete`
-- :ref:`odoo_online/contact-support`
-- :ref:`odoo_online/users`
-
-.. _odoo_online/upgrade:
-
-Upgrade
-=======
-
-If the database is *not* on the latest **Online version**, the administrator should receive an
-invitation to :doc:`upgrade <../upgrade>` the database. A :guilabel:`Rolling Release`` button on the
-database's main screen proposes an upgrade to the latest version (e.g., 14.0 to 16.1).
-
-.. important::
-   - | **If the Odoo database's version is lower than the latest major release:**
-     | The database must be upgraded within two months. After these two months, an automatic
-       upgrade is initiated.
-   - | **If the Odoo database's version is equal to or higher than the latest major release:**
-     | Disregard the invitation to upgrade as the database 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. Odoo recommends that the company initiate the upgrade, as this method allows for
-   the company to request a test upgrade of the database to check for any discrepancies.
-
-.. seealso::
-   - :doc:`../upgrade`
-   - :doc:`supported_versions`
-
-.. _odoo_online/duplicate:
-
-Duplicate
-=========
-
-This allows to make an exact copy of the database to be able to perform testing without compromising
-the daily operations.
-
-.. important::
-   - By checking :guilabel:`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.
-
-.. _odoo_online/rename:
-
-Rename
-======
-
-Rename the database and its URL.
-
-.. _odoo_online/download:
-
-Download
-========
-
-Instantly download 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>`_.
-
-.. _odoo_online/domains:
-
-Domains
-=======
-
-Configure custom domains to access the database via another URL.
-
-.. seealso::
-   - :doc:`domain_names`
-
-.. _odoo_online/tags:
-
-Tags
-====
-
-Add tags to sort your databases out. You can search the tags in the search bar.
-
-.. _odoo_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.
-
-Carefully read the warning message that pops up and proceed only if the implications of deleting a
-database are fully understood:
-
-.. image:: odoo_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>`_.
-
-.. _odoo_online/contact-support:
-
-Contact Support
-===============
-
-Access the Odoo `support page <https://www.odoo.com/help>`_ with your database's details already
-pre-filled.
-
-.. _odoo_online/users:
-
-Invite / Remove Users
-=====================
-
-To invite users, fill out the email address of the new user and click on :guilabel:`Invite`. To add
-multiple users, click on :guilabel:`Add more users`.
-
-.. image:: odoo_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 :guilabel:`Remove`.
-
-.. seealso::
-   - :doc:`/applications/general/users/manage_users`
-   - :doc:`/applications/general/users/delete_account`

content/administration/maintain/on_premise.rst

@@ -1,168 +0,0 @@
-==============================
-On-premise database management
-==============================
-
-Register a database
-===================
-
-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 Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard
-(Odoo 10).
-
-Registration Error Message
---------------------------
-
-If you are unable to register your database, you will likely encounter this
-message:
-
-.. 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
-
-Solutions
-~~~~~~~~~
-
-* Do you have a valid Enterprise subscription?
-
-  * Check if your subscription details get the tag "In Progress" on
-    your `Odoo Account
-    <https://accounts.odoo.com/my/subscription>`__ or with your Account Manager
-
-* Have you already linked a database with your subscription reference?
-
-  * You can link only one database per subscription.
-    (Need a test or a development database? `Find a partner
-    <https://www.odoo.com/partners>`__)
-
-  * You can unlink the old database yourself on your `Odoo Contract
-    <https://accounts.odoo.com/my/subscription>`__ with the button "Unlink database"
-
-    .. 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:: on_premise/unlink_confirm_enterprise_edition.png
-       :align: center
-
-* Do you have the updated version of Odoo 9?
-
-  * From July 2016 onward, Odoo 9 now automatically change the uuid of a
-    duplicated database; a manual operation is no longer required.
-
-  * If it's not the case, you may have multiple databases sharing the same
-    UUID. Please check on your `Odoo Contract
-    <https://accounts.odoo.com/my/subscription>`__, a short message will appear
-    specifying which database is problematic:
-
-    .. image:: on_premise/unlink_db_name_collision.png
-       :align: center
-
-    In this case, you need to change the UUID on your test databases to solve this
-    issue. You will find more information about this in :ref:`this section <duplicate_premise>`.
-
-    For your information, we identify database with UUID. Therefore, each database
-    should have a distinct UUID to ensure that registration and invoicing proceed
-    effortlessly for your and for us.
-
-* Check your network and firewall settings
-
-  * The Update notification must be able to reach Odoo's subscription
-    validation servers. In other words, make sure that the Odoo server is able
-    to open outgoing connections towards:
-
-      * services.odoo.com on port 443 (or 80)
-      * services.openerp.com on port 443 (or 80) for older deployments
-
-  * Once you activated your database, you must keep these ports open, as the
-    Update notification runs once a week.
-
-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:: on_premise/add_more_users.png
-   :align: center
-   :alt: This database will expire in X days, you have more users than your subscription allows
-
-
-When the message appears you have 30 days before the expiration.
-The countdown is updated everyday.
-
-Solutions
-~~~~~~~~~
-
-- **Add more users** on your subscription: follow the link and Validate
-  the upsell quotation and pay for the extra users.
-- **Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_
-  and **Reject** the upsell quotation.
-
-Once your database has the correct number of users, the expiration message
-will disappear automatically after a few days, when the next verification occurs.
-We understand that it can be a bit frightening to see the countdown,
-so you can :ref:`force an Update Notification <force_ping>`  to make the message disappear
-right away.
-
-Database expired error message
-------------------------------
-
-If your database reaches its expiration date before your renew your subscription,
-you will encounter this message:
-
-.. image:: on_premise/database_expired.png
-   :align: center
-   :alt: This database has expired.
-
-This **blocking** message appears after a non-blocking message that lasts 30 days.
-If you fail to take action before the end of the countdown, the database is expired.
-
-Solutions
-~~~~~~~~~
-
-* Renew your subscription: follow the link and renew your subscription - note that
-    if you wish to pay by Wire Transfer, your subscription will effectively be renewed
-    only when the payment arrives, which can take a few days. Credit card payments are
-    processed immediately.
-* Contact our `Support <https://www.odoo.com/help>`__
-
-None of those solutions worked for you? Please contact our
-`Support <https://www.odoo.com/help>`__
-
-.. _force_ping:
-
-.. _duplicate_premise:
-
-Duplicate a database
-====================
-
-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:: on_premise/db_manager.gif
-   :align: center
-
-When you duplicate a local database, it is **strongly** advised to change
-the duplicated database's uuid (Unniversally Unique Identifier), since this
-uuid is how your database identifies itself with our servers. Having two
-databases with the same uuid could result in invoicing problems or registration
-problems down the line.
-
-.. note::
-   From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a
-   manual operation is no longer required.
-
-The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical -->
-System Parameters`, we advise you to use a `uuid generator <https://www.uuidtools.com>`_ or to
-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:: on_premise/db_uuid.png
-   :align: center

content/administration/maintain/supported_versions.rst

@@ -5,16 +5,13 @@
 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
-   <odoo_online>` hosting every two months. Odoo Online users can then benefit from the latest
-   features of Odoo.
+Users hosted on **Odoo Online** may use intermediary versions (sometimes called *SaaS versions*) that are
+supported as well. These versions are not published for Odoo.sh or On-Premise
+installations.
 
-   - 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?
 =====================================
@@ -23,136 +20,38 @@ This matrix shows the support status of every version.
 
 **Major releases are in bold type.**
 
-.. list-table::
-   :header-rows: 1
-   :widths: auto
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+|                    | Odoo Online | Odoo.sh  | On-Premise   |   Release date |                                              |
++====================+=============+==========+==============+================+==============================================+
+| **Odoo 14.0**      |    |green|  | |green|  |   |green|    | October 2020   |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| Odoo 13.saas~4     |    |green|  | N/A      | N/A          | August 2019    |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| **Odoo 13.0**      |    |green|  | |green|  |   |green|    | October 2019   |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| Odoo 12.saas~3     |    |green|  | N/A      | N/A          | August 2019    |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| **Odoo 12.0**      |    |green|  | |green|  |   |green|    | October 2018   | *End-of-support is planned for October 2021* |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| Odoo 11.saas~3     |   |orange|  | N/A      | N/A          | April 2018     |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| **Odoo 11.0**      |   |orange|  | |orange| |    |red|     | October 2017   |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| Odoo 10.saas~15    |   |orange|  | N/A      | N/A          | March 2017     |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| Odoo 10.saas~14    |   |orange|  | N/A      | N/A          | January 2017   |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| **Odoo 10.0**      |   |orange|  | |orange| |    |red|     | October 2016   |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| Odoo 9.saas~11     |   |orange|  | N/A      | N/A          | May 2016       |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| **Odoo 9.0**       |   |orange|  | N/A      |    |red|     | October 2015   |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| Odoo 8.saas~6      |   |orange|  | N/A      | N/A          | February 2015  |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
+| **Odoo 8.0**       |   |orange|  | N/A      |    |red|     | September 2014 |                                              |
++--------------------+-------------+----------+--------------+----------------+----------------------------------------------+
 
-   * -
-     - Odoo Online
-     - Odoo.sh
-     - On-Premise
-     - Release date
-     - End of support
-   * - Odoo saas~16.3
-     - |green|
-     - N/A
-     - N/A
-     - June 2023
-     - September 2023 (planned)
-   * - Odoo saas~16.2
-     - |green|
-     - N/A
-     - N/A
-     - March 2023
-     - July 2023 (planned)
-   * - Odoo saas~16.1
-     - |red|
-     - N/A
-     - N/A
-     - February 2023
-     - April 2023
-   * - **Odoo 16.0**
-     - |green|
-     - |green|
-     - |green|
-     - October 2022
-     - October 2025 (planned)
-   * - Odoo saas~15.2
-     - |red|
-     - N/A
-     - N/A
-     - March 2022
-     - January 2023
-   * - Odoo saas~15.1
-     - |red|
-     - N/A
-     - N/A
-     - February 2022
-     - July 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**
-     - |red|
-     - |red|
-     - |red|
-     - October 2019
-     - October 2022
-   * - 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::
 
@@ -162,15 +61,19 @@ This matrix shows the support status of every version.
 
     N/A Never released for this platform
 
+    |orange| Some of our older customers may still run this version on our Odoo Online servers, we provide help only on blocking issues and advise you to upgrade.
+
     🏁 Future version, not released yet
 
-.. |green| raw:: html
 
-   <span class="text-success" style="font-size: 32px; line-height: 0.5">●</span>
+.. |green| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6IzAwYTcwMCIvPjwvc3ZnPg==
+   :width: 15
 
-.. |red| raw:: html
+.. |red| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6I2QwMDAwMCIvPjwvc3ZnPg==
+   :width: 15
 
-   <span class="text-danger" style="font-size: 32px; line-height: 0.5">●</span>
+.. |orange| image:: data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciIHZpZXdCb3g9IjAgMCAyMzIuMTkgMjMyLjE5Ij48Y2lyY2xlIGN4PSIxMTYuMDkiIGN5PSIxMTYuMDkiIHI9IjExNi4wOSIgc3R5bGU9ImZpbGw6I2ZmYTcwMCIvPjwvc3ZnPg==
+   :width: 15
 
 I run an older version of Odoo/OpenERP/TinyERP
 ==============================================

content/administration/maintain/update.rst

@@ -104,7 +104,6 @@ and you're all set.
 
 Source Install (Tarball)
 ------------------------
-
 If you have originally installed Odoo with the "tarball" version (source code archive), you have
 to replace the installation directory with a newer version. First download the latest tarball
 from Odoo.com. They are updated daily and include the latest security fixes (see step #1)
@@ -124,7 +123,6 @@ Finally, restart the Odoo service or reboot the machine, and you are all set.
 
 Source Install (Github)
 -----------------------
-
 If you have originally installed Odoo with a full Github clone of the official repositories, the
 update procedure requires you to pull the latest source code via git.
 Change into the directory for each repository (the main Odoo repository, and the Enterprise

content/administration/odoo_sh/advanced.rst

@@ -1,12 +1,13 @@
 :nosearch:
 
-========
+=================
 Advanced
-========
+=================
 
 .. toctree::
    :titlesonly:
 
    advanced/containers
    advanced/submodules
+   advanced/upgrade_your_database
    advanced/frequent_technical_questions

content/administration/odoo_sh/advanced/containers.rst

@@ -1,7 +1,7 @@
 
-==========
+==================================
 Containers
-==========
+==================================
 
 Overview
 ========
@@ -17,7 +17,7 @@ The platform will take care to install these dependencies in your containers.
 `The pip requirements specifiers <https://pip.pypa.io/en/stable/reference/pip_install/#requirement-specifiers>`_
 documentation can help you write a :file:`requirements.txt` file.
 To have a concrete example,
-check out the `requirements.txt file of Odoo <{GITHUB_PATH}/requirements.txt>`_.
+check out the `requirements.txt file of Odoo <https://github.com/odoo/odoo/blob/14.0/requirements.txt>`_.
 
 The :file:`requirements.txt` files of submodules are taken into account as well. The platform
 looks for :file:`requirements.txt` files in each folder containing Odoo modules: Not in the module folder itself,
@@ -167,16 +167,16 @@ 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/cli>`.
+: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*":
 
 ::
 
-  2018-02-19 10:51:39,267 4 INFO ? odoo: Odoo version {BRANCH}
+  2018-02-19 10:51:39,267 4 INFO ? odoo: Odoo version 13.0
   2018-02-19 10:51:39,268 4 INFO ? odoo: Using configuration file at /home/odoo/.config/odoo/odoo.conf
-  2018-02-19 10:51:39,268 4 INFO ? odoo: addons paths: ['/home/odoo/data/addons/{BRANCH}', '/home/odoo/src/user', '/home/odoo/src/enterprise', '/home/odoo/src/themes', '/home/odoo/src/odoo/addons', '/home/odoo/src/odoo/odoo/addons']
+  2018-02-19 10:51:39,268 4 INFO ? odoo: addons paths: ['/home/odoo/data/addons/13.0', '/home/odoo/src/user', '/home/odoo/src/enterprise', '/home/odoo/src/themes', '/home/odoo/src/odoo/addons', '/home/odoo/src/odoo/odoo/addons']
 
 **Be careful**, especially with your production database.
 Operations that you perform running this Odoo server instance are not isolated:
@@ -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:: containers/pdb_sh.png
+.. image:: ./media/pdb_sh.png
     :align: center
     :alt: Console screenshot showing ``pdb`` running in an Odoo.sh shell.

content/administration/odoo_sh/advanced/frequent_technical_questions.rst

@@ -1,9 +1,9 @@
 
 .. _odoosh-advanced-frequent_technical_questions:
 
-============================
+==================================
 Frequent Technical Questions
-============================
+==================================
 
 "Scheduled actions do not run at the exact time they were expected"
 -------------------------------------------------------------------
@@ -29,3 +29,4 @@ We advise that:
 - Your scheduled actions should be
   `idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
   cause side-effects if they are started more often than expected.
+

content/administration/odoo_sh/advanced/submodules.rst

@@ -1,9 +1,9 @@
 
 .. _odoosh-advanced-submodules:
 
-==========
+==================================
 Submodules
-==========
+==================================
 
 Overview
 ========
@@ -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:: submodules/advanced-submodules-button.png
+.. image:: ./media/advanced-submodules-button.png
    :align: center
 
 A dialog with a form is shown. Fill the inputs as follows:
@@ -53,18 +53,18 @@ 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:: submodules/advanced-submodules-dialog.png
+.. image:: ./media/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:: submodules/advanced-submodules-github-sshurl.png
+.. image:: ./media/advanced-submodules-github-sshurl.png
   :align: center
 
 .. _odoosh-advanced-submodules-withgit:
 
 With Git (advanced)
--------------------
+---------------------
 
 In a terminal, in the folder where your Git repository is cloned,
 checkout the branch in which you want to add a submodule:

content/administration/odoo_sh/advanced/upgrade_your_database.rst

@@ -0,0 +1,48 @@
+
+=====================
+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,8 +1,8 @@
 :nosearch:
 
-===========
+=================
 Get started
-===========
+=================
 
 .. toctree::
    :titlesonly:

content/administration/odoo_sh/getting_started/branches.rst

@@ -1,32 +1,32 @@
-========
+
+==================================
 Branches
-========
+==================================
 
 Overview
 ========
 
 The branches view gives you an overview of the different branches your repository has.
 
-.. image:: branches/interface-branches.png
+.. image:: ./media/interface-branches.png
    :align: center
 
 .. _odoosh-gettingstarted-branches-stages:
 
 Stages
-======
+===============
 
 Odoo.sh offers three different stages for your branches: production, staging and development.
 
 You can change the stage of a branch by drag and dropping it into the stage section title.
 
-.. image:: branches/interface-branches-stagechange.png
+.. image:: ./media/interface-branches-stagechange.png
    :align: center
 
 .. _stage_production:
 
 Production
 ----------
-
 This is the branch holding the code on which your production database runs.
 There can be only one production branch.
 
@@ -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/cli>`.
+: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,
@@ -59,7 +59,6 @@ will automatically be set back to the development stage after 30 days.
 
 Staging
 -------
-
 Staging branches are meant to test your new features using the production data without compromising
 the actual production database with test records. They will create databases that are neutralized
 duplicates of the production database.
@@ -72,7 +71,7 @@ The neutralization includes:
 * Disabling outgoing emails by intercepting them with a mailcatcher. An
   :ref:`interface to view <odoosh-gettingstarted-branches-tabs-mails>` the emails sent by your
   database is provided. That way, you do not have to worry about sending test emails to your contacts.
-* Setting payment providers and shipping providers in test mode.
+* Setting payment acquirers and shipping providers in test mode.
 * Disabling IAP services
 
 The latest database will be kept alive indefinitely, older ones from the same branch may get garbage collected
@@ -84,9 +83,9 @@ The unit tests are not performed as, in Odoo, they currently rely on the demo da
 production database. In the future, if Odoo supports to run the unit tests without the demo data,
 Odoo.sh will then consider running the tests on staging databases.
 
+
 Development
 -----------
-
 Development branches create new databases using the demo data to run the unit tests.
 The installed modules are the ones included in your branches. You can change this list of modules
 to install in your :ref:`project Settings <odoosh-gettingstarted-settings-modules-installation>`.
@@ -108,10 +107,9 @@ After that, they can be automatically garbage collected to make room for new dat
 
 Merging your branches
 ---------------------
-
 You can merge your branches easily by drag and dropping them into each other.
 
-.. image:: branches/interface-branches-merge.png
+.. image:: ./media/interface-branches-merge.png
    :align: center
 
 When you want to test the changes of your development branches with the production data,
@@ -149,17 +147,16 @@ If you test configuration changes in staging branches, and want them to be appli
 .. _odoosh-gettingstarted-branches-tabs:
 
 Tabs
-====
+=============
 
 History
 -------
-
 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:: branches/interface-branches-history.png
+.. image:: ./media/interface-branches-history.png
    :align: center
 
 For each event, a status is displayed in the top right-hand corner.
@@ -171,38 +168,36 @@ When an operation is successful, you can access the database thanks to the *conn
 
 Mails
 -----
-
 This tab contains the mail catcher. It displays an overview of the emails sent by your database.
 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:: branches/interface-branches-mails.png
+.. image:: ./media/interface-branches-mails.png
    :align: center
    :scale: 50%
 
 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:: branches/interface-branches-shell.png
+.. image:: ./media/interface-branches-shell.png
    :align: center
 
 You can open multiple tabs and drag-and-drop them to arrange the layout as you wish,
 for instance side by side.
 
+
 .. Note::
   Long running shell instances are not guaranteed. Idle shells can be
   disconnected at anytime in order to free up resources.
 
 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:: branches/interface-branches-editor.png
+.. image:: ./media/interface-branches-editor.png
    :align: center
 
 You can open multiple tabs and drag-and-drop them to arrange the layout as you wish,
@@ -210,23 +205,19 @@ for instance side by side.
 
 Monitoring
 ----------
-
 This link contains various monitoring metrics of the current build.
 
-.. image:: branches/interface-branches-monitoring.png
+.. image:: ./media/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:: branches/interface-branches-logs.png
+.. image:: ./media/interface-branches-logs.png
    :align: center
 
 Different logs are available:
@@ -247,11 +238,10 @@ The fetching is automatically stopped after 5 minutes. You can restart it using
 
 Backups
 -------
-
 A list of the backups available for download and restore, the ability to perform a manual backup and to import a
 database.
 
-.. image:: branches/interface-branches-backups.png
+.. image:: ./media/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.
@@ -267,16 +257,16 @@ This server only keeps one month of backups: 7 daily and 4 weekly backups.
 Dedicated backup servers keep the same backups, as well as 3 additional monthly backups.
 To restore or download one of these monthly backups, please `contact us <https://www.odoo.com/help>`_.
 
-If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
-dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
-as either the container will be changed by the installation of new pip packages, either the database itself will be
-changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
+If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python 
+dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list), 
+as either the container will be changed by the installation of new pip packages, either the database itself will be 
+changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially 
 break things.
 
-If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
-by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
-as an extra precaution, you can make a backup manually before making big changes in your production sources in case
-something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
+If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done 
+by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course, 
+as an extra precaution, you can make a backup manually before making big changes in your production sources in case 
+something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups 
 to 5 per day.
 
 The *import database* feature accepts database archives in the format provided by:
@@ -287,24 +277,13 @@ The *import database* feature accepts database archives in the format provided b
 * the Odoo.sh backup download button of this *Backups* tab,
 * the Odoo.sh dump download button in the :ref:`Builds view <odoosh-gettingstarted-builds>`.
 
-.. _odoo_sh/upgrade:
-
-Upgrade
--------
-
-Available for production and staging branches for valid projects.
-
-.. seealso::
-    :doc:`Upgrade - Odoo.sh <../../upgrade/odoo_sh>`
-
 .. _odoosh-gettingstarted-branches-tabs-settings:
 
 Settings
 --------
-
 Here you can find a couple of settings that only apply to the currently selected branch.
 
-.. image:: branches/interface-branches-settings.jpg
+.. image:: ./media/interface-branches-settings.jpg
    :align: center
 
 **Behaviour upon new commit**
@@ -321,7 +300,7 @@ back from staging to development will automatically be set to 'Do nothing'.
 
 Choose the modules to install automatically for your development builds.
 
-.. image:: branches/interface-settings-modulesinstallation.png
+.. image:: ./media/interface-settings-modulesinstallation.png
    :align: center
 
 * *Install only my modules* will install the modules of the branch only. This is the default option.
@@ -403,19 +382,18 @@ 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 documentation about :ref:`SPF
-<email_communication/spf_compliant>` and :ref:`DKIM <email_communication/dkim_compliant>`.
+The configuration steps are explained in the :ref:`Discuss app documentation <discuss-email_servers-spf-compliant>`.
 
 .. Warning::
   Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host can lead to the
   delivery of your emails as spam in your contacts inbox.
 
+
 Shell commands
 ==============
-
 In the top right-hand corner of the view, different shell commands are available.
 
-.. image:: branches/interface-branches-shellcommands.png
+.. image:: ./media/interface-branches-shellcommands.png
    :align: center
 
 Each command can be copied in the clipboard to be used in a terminal,
@@ -425,7 +403,6 @@ such as ``<URL>``, ``<PATH>``, ...
 
 Clone
 -----
-
 Download the Git repository.
 
 .. code-block:: bash
@@ -441,7 +418,6 @@ The *run* button is not available for this command, as it is meant to be used on
 
 Fork
 ----
-
 Create a new branch based on the current branch.
 
 .. code-block:: bash
@@ -458,7 +434,6 @@ Uploads the new branch *feature-1* on your remote repository.
 
 Merge
 -----
-
 Merge the current branch in another branch.
 
 .. code-block:: bash
@@ -475,10 +450,8 @@ Uploads the changes you just added in the *master* branch on your remote reposit
 
 SSH
 ---
-
 Setup
 ~~~~~
-
 In order to use SSH, you have to set up your profile SSH public key (if it is not already done).
 To do so, follow these steps:
 
@@ -489,12 +462,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:: branches/SSH-key-pasting.png
+   .. image:: ./media/SSH-key-pasting.png
       :align: center
 
 #. The key should appear below
 
-   .. image:: branches/SSH-key-appearing.png
+   .. image:: ./media/SSH-key-appearing.png
       :align: center
 
 Connection
@@ -508,7 +481,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:: branches/SSH-panel.png
+.. image:: ./media/SSH-panel.png
    :align: center
 
 Provided you have the :ref:`correct access rights <odoosh-gettingstarted-settings-collaborators>` on the project,
@@ -518,6 +491,7 @@ you'll be granted ssh access to the build.
   Long running ssh connections are not guaranteed. Idle connections will be
   disconnected in order to free up resources.
 
+
 Submodule
 ---------
 

content/administration/odoo_sh/getting_started/builds.rst

@@ -1,20 +1,19 @@
 
 .. _odoosh-gettingstarted-builds:
 
-======
+==================================
 Builds
-======
+==================================
 
 Overview
 ========
 
 In Odoo.sh, a build is considered as a database loaded by an Odoo server
-(`odoo/odoo <https://github.com/odoo/odoo>`_ & `odoo/enterprise
-<https://github.com/odoo/enterprise>`_) 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.
+(`odoo/odoo <https://github.com/odoo/odoo>`_ & `odoo/enterprise <https://github.com/odoo/enterprise>`_)
+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:: builds/interface-builds.png
+.. image:: ./media/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.
@@ -29,13 +28,13 @@ A successful build is highlighted in green.
 A build is considered failed if errors come up during its creation.
 A failed build is highlighted in red.
 
-If warnings come up during the creation, but there are no errors, the build is considered almost
-successful. It is highlighted in yellow to notify the developer warnings were raised.
+If warnings come up during the creation, but there are no errors, the build is considered almost successful.
+It is highlighted in yellow to notify the developer warnings were raised.
 
-Builds do not always create a database from scratch. For instance, when pushing a change on the
-production branch, the build created just starts the server with your new revision and tries to load
-the current production database on it. If no errors come up, the build is considered successful, and
-otherwise failed.
+Builds do not always create a database from scratch.
+For instance, when pushing a change on the production branch, the build created just starts the server
+with your new revision and tries to load the current production database on it.
+If no errors come up, the build is considered successful, and otherwise failed.
 
 Stages
 ======
@@ -49,15 +48,14 @@ If this build is successful, this database is considered as the production datab
 From then, pushes on the production branch will create new builds that attempt to load the database
 using a server running with the new revision.
 
-If the build is successful, or has warnings but no errors, the production database will now run with
-this build, along with the revision associated to this build.
+If the build is successful, or has warnings but no errors, the production database will now run with this build, along
+with the revision associated to this build.
 
-If the build fails to load or update the database, then the previous successful build is re-used to
-load the database, and therefore the database will run using a server running with the previous
-successful revision.
+If the build fails to load or update the database, then the previous successful build is re-used to load the database,
+and therefore the database will run using a server running with the previous successful revision.
 
-The build used to run the production database is always the first of the builds list. If a build
-fails, it is put after the build currently running the production database.
+The build used to run the production database is always the first of the builds list. If a build fails, it is
+put after the build currently running the production database.
 
 Staging
 -------
@@ -65,17 +63,18 @@ Staging
 Staging builds duplicate the production database,
 and try to load this duplicate with the revisions of the staging branches.
 
-Each time you push a new revision on a staging branch, the build created uses a new copy of the
-production database. The databases are not re-used between builds of the same branch. This ensures:
+Each time you push a new revision on a staging branch, the build created uses a new copy of the production database.
+The databases are not re-used between builds of the same branch. This ensures:
 
-* staging builds use databases that are close to what the production looks like, so you do not make
-  your tests with outdated data,
+* staging builds use databases that are close to what the production looks like,
+  so you do not make your tests with outdated data,
 
-* you can play around as much as you want in the same staging database, and you can then ask for a
-  rebuild when you want to restart with a new copy of the production.
+* you can play around as much as you want in the same staging database,
+  and you can then ask for a rebuild when you want to restart with a new copy of the production.
 
-Nevertheless, this means that if you make configuration changes in staging databases and do not
-apply them in the production, they will not be passed on the next build of the same staging branch.
+Nevertheless, this means that if you make configuration changes in staging databases
+and do not apply them in the production,
+they will not be passed on the next build of the same staging branch.
 
 Development
 -----------
@@ -87,38 +86,38 @@ as they are meant to raise errors if something wrong occurs.
 
 If all tests pass, and there is no error, the build will be considered successful.
 
-According to the list of modules to install and test, a development build can take up to 1 hour to
-be ready. This is due to the large number of tests set in the default Odoo modules suite.
+According to the list of modules to install and test, a development build can take up to 1 hour to be ready.
+This is due to the large number of tests set in the default Odoo modules suite.
 
 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.
+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:: builds/interface-builds-branches.png
+.. image:: ./media/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 the *Github* link. For other branches than the production, you can create a new
-build which will use the latest revision of the branch using the link *rebuild*. This last link is
-not available when there is already a build in progress for the branch.
+For each branch, you can access the last build's database using the *Connect* link and jump to the branch code using
+the *Github* link. For other branches than the production, you can create a new build which will use the latest revision
+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:: builds/interface-builds-build.png
+.. image:: ./media/interface-builds-build.png
    :align: center
 
-For each build, you can access the revision changes using the button with the Github icon. You can
-access the build's database as the administrator using the *Connect* button. Also, you can access
-the database with another user using the *Connect as* button, in the dropdown menu of the *Connect*
-button.
+For each build, you can access the revision changes using the button with the Github icon.
+You can access the build's database as the administrator using the *Connect* button.
+Also, you can access the database with another user using the *Connect as* button,
+in the dropdown menu of the *Connect* button.
 
 .. _odoosh-gettingstarted-builds-download-dump:
 
-.. image:: builds/interface-builds-build-dropdown.png
+.. image:: ./media/interface-builds-build-dropdown.png
    :align: center
 
 .. _odoosh-gettingstarted-builds-dropdown-menu:
 
-In the dropdown menu of the build, you can access the same features than in :ref:`the branches view
-<odoosh-gettingstarted-branches-tabs>`: *Logs*, *Web Shell*, *Editor*, *Outgoing e-mails*. You also
-have the possibility to *Download a dump* of the build's database.
+In the dropdown menu of the build, you can access the same features than in :ref:`the branches view <odoosh-gettingstarted-branches-tabs>`:
+*Logs*, *Web Shell*, *Editor*, *Outgoing e-mails*.
+You also have the possibility to *Download a dump* of the build's database.

content/administration/odoo_sh/getting_started/create.rst

@@ -1,25 +1,24 @@
 
 .. _odoosh-gettingstarted-create:
 
-===================
+==================================
 Create your project
-===================
+==================================
 
 Deploy your platform
 ====================
 
 Go to `Odoo.sh <https://www.odoo.sh/>`_ and hit the *Deploy your platform* button.
 
-.. image:: create/deploy.png
+.. image:: ./media/deploy.png
    :align: center
 
 Sign in with Github
 ===================
 
-Sign in with your Github account. If you do not have an account yet, hit the *Create an account*
-link.
+Sign in with your Github account. If you do not have an account yet, hit the *Create an account* link.
 
-.. image:: create/github-signin.png
+.. image:: ./media/github-signin.png
    :align: center
 
 Authorize Odoo.sh
@@ -27,62 +26,51 @@ Authorize Odoo.sh
 
 Grant Odoo.sh the required accesses to your account by clicking the *Authorize* button.
 
-.. image:: create/github-authorize.png
+.. image:: ./media/github-authorize.png
    :align: center
 
 Odoo.sh basically needs:
 
 * to know your Github login and email,
 * to create a new repository in case you decide to start from scratch,
-* to read your existing repositories, including the ones of your organizations, in case you want to
-  start from an existing repository,
+* to read your existing repositories, including the ones of your organizations, in case you want to start from an existing repository,
 * to create a webhook to be notified each time you push changes,
-* to commit changes to make your deployment easier, merging branches or adding new `submodules
-  <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ for example.
+* to commit changes to make your deployment easier, merging branches or adding new `submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ for example.
 
 Submit your project
 ===================
 
-Choose if you want to start from scratch by creating a new repository, or if you want to use an
-existing repository.
+Choose if you want to start from scratch by creating a new repository, or if you want to use an existing repository.
 
 Then, choose a name or select the repository you want to use.
 
-Choose the Odoo version you want to use. If you plan to import an existing database or an existing
-set of applications, you might need to choose the according version. If you start from scratch, use
-the latest version.
+Choose the Odoo version you want to use. If you plan to import an existing database or an existing set of applications, you might need to choose the according version. If you start from scratch, use the latest version.
 
-Enter your *subscription code*. This is also called *subscription referral*, *contract number* or
-*activation code*.
+Enter your *subscription code*. This is also called *subscription referral*, *contract number* or *activation code*.
 
 It should be the code of your Enterprise subscription that includes Odoo.sh.
 
-Partners can use their partnership codes to start a trial. Should their clients start a project,
-they ought to get an Enterprise subscription including Odoo.sh and use its subscription code. The
-partner will get 50% of the amount back as commission. Contact your sales representative or account
-manager in order to get it.
+Partners can use their partnership codes to start a trial. Should their clients start a project, they ought to get an Enterprise subscription including Odoo.sh and use its subscription code. The partner will get the full amount as back commission.
+Contact your sales representative or account manager in order to get it.
 
 When submitting the form, if you are notified your subscription is not valid, it either means:
 
 * it is not an existing subscription,
 * it is not a partnership subscription,
 * it is an enterprise subscription, but which does not include Odoo.sh,
-* it is neither a partnership subscription or an enterprise subscription (e.g. an online
-  subscription).
+* it is neither a partnership subscription or an enterprise subscription (e.g. an online subscription).
 
-In case of doubt with your subscription, please contact the `Odoo support
-<https://www.odoo.com/help>`_.
+In case of doubt with your subscription, please contact the `Odoo support <https://www.odoo.com/help>`_.
 
-.. image:: create/deploy-form.png
+.. image:: ./media/deploy-form.png
    :align: center
 
 You're done !
 =============
 
-You can start using Odoo.sh. Your first build is about to be created. You will soon be able to
-connect to your first database.
+You can start using Odoo.sh. Your first build is about to be created. You will soon be able to connect to your first database.
 
-.. image:: create/deploy-done.png
+.. image:: ./media/deploy-done.png
    :align: center
 
 .. _odoo_sh_import_your_database:
@@ -100,10 +88,9 @@ If you use community or custom modules, add them in a branch in your Github repo
 Databases hosted on the Odoo.com online platform do not have any custom modules.
 Users of these databases can therefore skip this step.
 
-You can structure your modules as you wish, Odoo.sh will automatically detect the folders containing
-Odoo addons. For instance, you can put all your modules folder in the root directory of your
-repository, or group the modules in folders by categories that you define (accounting, project,
-...).
+You can structure your modules as you wish, Odoo.sh will automatically detect the folders containing Odoo addons.
+For instance, you can put all your modules folder in the root directory of your repository,
+or group the modules in folders by categories that you define (accounting, project, ...).
 
 For community modules available in public Git repositories,
 you can also consider to add them using :ref:`Submodules <odoosh-advanced-submodules>`.
@@ -124,82 +111,77 @@ Access the URL :file:`/web/database/manager` of your on-premise database and dow
   If you cannot access the database manager, it may have been disabled by your system administrator.
   See the :ref:`database manager security documentation <db_manager_security>`.
 
-You will need the master password of your database server. If you do not have it, contact your
-system administrator.
+You will need the master password of your database server. If you do not have it, contact your system administrator.
 
-.. image:: create/create-import-onpremise-backup.png
+.. image:: ./media/create-import-onpremise-backup.png
    :align: center
 
 Choose a zip including the filestore as the backup format.
 
-.. image:: create/create-import-onpremise-backup-dialog.png
+.. image:: ./media/create-import-onpremise-backup-dialog.png
   :align: center
 
 Odoo Online databases
 ~~~~~~~~~~~~~~~~~~~~~
 
-`Access your databases manager <https://accounts.odoo.com/my/databases/manage>`_ and download a
-backup of your database.
+`Access your databases manager <https://accounts.odoo.com/my/databases/manage>`_ and download a backup of your database.
 
-.. image:: create/create-import-online-backup.png
-   :align: center
+.. image:: ./media/create-import-online-backup.png
+  :align: center
 
 .. Warning::
 
-  Online versions (e.g. *saas-**) are not supported on Odoo.sh.
+  Saas releases (e.g. *saas-**) are not supported on Odoo.sh.
 
 Upload the backup
 -----------------
 
-Then, in your Odoo.sh project, in the backups tab of your production branch, import the backup you
-just downloaded.
+Then, in your Odoo.sh project, in the backups tab of your production branch, import the backup you just downloaded.
 
-.. image:: create/create-import-production.png
+.. image:: ./media/create-import-production.png
    :align: center
 
-Once the backup imported, you can access the database using the *Connect* button in the history of
-the branch.
+Once the backup imported, you can access the database using the *Connect* button in the history of the branch.
 
-.. image:: create/create-import-production-done.png
-   :align: center
+.. image:: ./media/create-import-production-done.png
+  :align: center
 
 Check your outgoing email servers
 ---------------------------------
 
 There is a default mail server provided with Odoo.sh.
 To use it, there must be no enabled outgoing mail server configured in your database in
-:menuselection:`Settings --> Technical --> Outgoing Mail Servers` (:ref:`Developer mode
-<developer-mode>` must be activated).
+:menuselection:`Settings --> Technical --> Outgoing Mail Servers`
+(:ref:`Developer mode <developer-mode>` must be activated).
 
-After the import of your database, all outgoing email servers are disabled so you use the Odoo.sh
-email server provided by default.
+After the import of your database,
+all outgoing email servers are disabled so you use the Odoo.sh email server provided by default.
 
-.. warning::
-   Port 25 is (and will stay) closed. If you want to connect to an external SMTP server, you should
-   use ports 465 and 587.
+.. Warning::
+
+  Port 25 is (and will stay) closed. If you want to connect to an external SMTP server, you should use ports 465 and 587.
 
 Check your scheduled actions
 ----------------------------
 
 All scheduled actions are disabled after the import.
 
-This is to prevent your newly imported database to perform actions that could impact your running
-production, such as sending the mails remaining in the queue, processing mass mailings, or
-third-party services synchronization (Calendars, files hosting, ...).
+This is to prevent your newly imported database to perform actions that could impact your running production,
+such as sending the mails remaining in the queue, processing mass mailings, or third-party services synchronization
+(Calendars, files hosting, ...).
 
 If you plan to make the imported database your production, enable the scheduled actions you need.
-You can check what is enabled in the database of origin and enable the same actions in the imported
-database. Scheduled actions are located under :menuselection:`Settings --> Technical --> Automation
---> Scheduled Actions`.
+You can check what is enabled in the database of origin and enable the same actions in the imported database.
+Scheduled actions are located under :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`.
 
 Register your subscription
 --------------------------
 
 Your subscription is unlinked after the import.
 
-The imported database is considered a duplicate by default and the enterprise subscription is
-therefore removed, as you can only have one database linked per subscription.
+The imported database is considered a duplicate by default and the enterprise subscription is therefore removed,
+as you can only have one database linked per subscription.
 
-If you plan to make it your production, unlink your former database from the subscription, and
-register the newly imported database. Read the :doc:`database registration documentation
-<../../maintain/on_premise>` for instructions.
+If you plan to make it your production,
+unlink your former database from the subscription, and register the newly imported database.
+Read the :ref:`database registration documentation <db_premise>` for instructions.

content/administration/odoo_sh/getting_started/first_module.rst

@@ -1,14 +1,14 @@
-=================
+
+==================================
 Your first module
-=================
+==================================
 
 Overview
 ========
 
 This chapter helps you to create your first Odoo module and deploy it in your Odoo.sh project.
 
-This tutorial requires :ref:`you created a project on Odoo.sh <odoosh-gettingstarted-create>`, and
-you know your Github repository's URL.
+This tutorial requires :ref:`you created a project on Odoo.sh <odoosh-gettingstarted-create>`, and you know your Github repository's URL.
 
 Basic use of Git and Github is explained.
 
@@ -27,7 +27,7 @@ Create the development branch
 =============================
 
 From Odoo.sh
-------------
+-------------
 
 In the branches view:
 
@@ -37,24 +37,26 @@ In the branches view:
 
   |pic1|  |pic2|
 
-.. |pic1| image:: first_module/firstmodule-development-+.png
+.. |pic1| image:: ./media/firstmodule-development-+.png
    :width: 45%
 
-.. |pic2| image:: first_module/firstmodule-development-fork.png
+.. |pic2| image:: ./media/firstmodule-development-fork.png
    :width: 45%
 
+
 Once the build created, you can access the editor and browse to the folder *~/src/user* to access
 to the code of your development branch.
 
-.. image:: first_module/firstmodule-development-editor.png
-   :align: center
+.. image:: ./media/firstmodule-development-editor.png
+  :align: center
 
-.. image:: first_module/firstmodule-development-editor-interface.png
-   :align: center
+.. image:: ./media/firstmodule-development-editor-interface.png
+  :align: center
 
 From your computer
 ------------------
 
+
 Clone your Github repository on your computer:
 
 .. code-block:: bash
@@ -70,6 +72,7 @@ Create a new branch:
 
   $ git checkout -b feature-1 master
 
+
 Create the module structure
 ===========================
 
@@ -92,8 +95,8 @@ Or, from your computer, if you have an :ref:`installation of Odoo <setup/install
   $ ./odoo-bin scaffold my_module ~/src/odoo-addons/
 
 If you do not want to bother installing Odoo on your computer,
-you can also :download:`download this module structure template <first_module/my_module.zip>` in
-which you replace every occurrences of *my_module* to the name of your choice.
+you can also :download:`download this module structure template <media/my_module.zip>` in which you replace every occurrences of
+*my_module* to the name of your choice.
 
 The below structure will be generated:
 
@@ -116,11 +119,11 @@ The below structure will be generated:
       ├── templates.xml
       └── views.xml
 
-.. warning::
+.. Warning::
 
-   Do not use special characters other than the underscore ( _ ) for your module name, not even an
-   hyphen ( - ). This name is used for the Python classes of your module, and having classes name
-   with special characters other than the underscore is not valid in Python.
+  Do not use special characters other than the underscore ( _ ) for your module name, not even an hyphen ( - ).
+  This name is used for the Python classes of your module,
+  and having classes name with special characters other than the underscore is not valid in Python.
 
 Uncomment the content of the files:
 
@@ -138,7 +141,7 @@ Uncomment the content of the files:
   the manifest of your module, including for instance its title, description and data files to load.
   You just need to uncomment the access control list data file:
 
-  .. code-block:: python
+  .. code-block:: xml
 
     # 'security/ir.model.access.csv',
 
@@ -146,7 +149,7 @@ Manually
 --------
 
 If you want to create your module structure manually,
-you can follow the :doc:`/developer/tutorials/getting_started` tutorial to understand
+you can follow :doc:`Build an Odoo module </developer/howtos/backend>` to understand
 the structure of a module and the content of each file.
 
 Push the development branch
@@ -177,8 +180,8 @@ The above command is explained in the section
 <odoosh-gettingstarted-online-editor-push>` of the
 :ref:`Online Editor <odoosh-gettingstarted-online-editor>`
 chapter.
-It includes the explanation regarding the fact you will be prompted to type your username and
-password, and what to do if you use the two-factor authentication.
+It includes the explanation regarding the fact you will be prompted to type your username and password,
+and what to do if you use the two-factor authentication.
 
 Or, from your computer terminal:
 
@@ -198,27 +201,27 @@ Test your module
 
 Your branch should appear in your development branches in your project.
 
-.. image:: first_module/firstmodule-test-branch.png
+.. image:: ./media/firstmodule-test-branch.png
   :align: center
 
 In the branches view of your project,
 you can click on your branch name in the left navigation panel to access its history.
 
-.. image:: first_module/firstmodule-test-branch-history.png
+.. image:: ./media/firstmodule-test-branch-history.png
   :align: center
 
 You can see here the changes you just pushed, including the comment you set.
 Once the database ready, you can access it by clicking the *Connect* button.
 
-.. image:: first_module/firstmodule-test-database.png
+.. image:: ./media/firstmodule-test-database.png
   :align: center
 
 If your Odoo.sh project is configured to install your module automatically,
-you will directly see it amongst the database apps. Otherwise, it will be available in the apps to
-install.
+you will directly see it amongst the database apps. Otherwise, it will be available in the apps to install.
 
 You can then play around with your module, create new records and test your features and buttons.
 
+
 Test with the production data
 =============================
 
@@ -229,24 +232,23 @@ you can test it with the production data using a staging branch.
 
 You can either:
 
-* Make your development branch a staging branch, by drag and dropping it onto the *staging* section
-  title.
+* Make your development branch a staging branch, by drag and dropping it onto the *staging* section title.
 
-  .. image:: first_module/firstmodule-test-devtostaging.png
-     :align: center
+  .. image:: ./media/firstmodule-test-devtostaging.png
+    :align: center
 
 * Merge it in an existing staging branch, by drag and dropping it onto the given staging branch.
 
-  .. image:: first_module/firstmodule-test-devinstaging.png
-     :align: center
+  .. image:: ./media/firstmodule-test-devinstaging.png
+    :align: center
 
 You can also use the :code:`git merge` command to merge your branches.
 
-This will create a new staging build, which will duplicate the production database and make it run
-using a server updated with your latest changes of your branch.
+This will create a new staging build, which will duplicate the production database and make it run using a server
+updated with your latest changes of your branch.
 
-.. image:: first_module/firstmodule-test-mergedinstaging.png
-   :align: center
+.. image:: ./media/firstmodule-test-mergedinstaging.png
+  :align: center
 
 Once the database ready, you can access it using the *Connect* button.
 
@@ -255,24 +257,22 @@ Once the database ready, you can access it using the *Connect* button.
 Install your module
 -------------------
 
-Your module will not be installed automatically, you have to install it from the apps menu. Indeed,
-the purpose of the staging build is to test the behavior of your changes as it would be on your
-production, and on your production you would not like your module to be installed automatically, but
-on demand.
+Your module will not be installed automatically, you have to install it from the apps menu.
+Indeed, the purpose of the staging build is to test the behavior of your changes as it would be on your production,
+and on your production you would not like your module to be installed automatically, but on demand.
 
-Your module may not appear directly in your apps to install either, you need to update your apps
-list first:
+Your module may not appear directly in your apps to install either, you need to update your apps list first:
 
 * Activate the :ref:`developer mode <developer-mode>`
 * in the apps menu, click the *Update Apps List* button,
 * in the dialog that appears, click the *Update* button.
 
-  .. image:: first_module/firstmodule-test-updateappslist.png
+  .. image:: ./media/firstmodule-test-updateappslist.png
     :align: center
 
 Your module will then appear in the list of available apps.
 
-.. image:: first_module/firstmodule-test-mymoduleinapps.png
+.. image:: ./media/firstmodule-test-mymoduleinapps.png
   :align: center
 
 Deploy in production
@@ -283,7 +283,7 @@ and believe it is ready for production, you can merge your branch in the product
 
 Drag and drop your staging branch on the production branch.
 
-.. image:: first_module/firstmodule-test-mergeinproduction.png
+.. image:: ./media/firstmodule-test-mergeinproduction.png
   :align: center
 
 You can also use the :code:`git merge` command to merge your branches.
@@ -291,7 +291,7 @@ You can also use the :code:`git merge` command to merge your branches.
 This will merge the latest changes of your staging branch in the production branch,
 and update your production server with these latest changes.
 
-.. image:: first_module/firstmodule-test-mergedinproduction.png
+.. image:: ./media/firstmodule-test-mergedinproduction.png
   :align: center
 
 Once the database ready, you can access it using the *Connect* button.
@@ -307,16 +307,14 @@ you have to install it manually as explained in the
 Add a change
 ============
 
-This section explains how to add a change in your module by adding a new field in a model and deploy
-it.
+This section explains how to add a change in your module by adding a new field in a model and deploy it.
 
 From the Odoo.sh editor,
  * browse to your module folder *~/src/user/my_module*,
  * then, open the file *models/models.py*.
 
 Or, from your computer,
- * use the file browser of your choice to browse to your module folder
-   *~/src/odoo-addons/my_module*,
+ * use the file browser of your choice to browse to your module folder *~/src/odoo-addons/my_module*,
  * then, open the file *models/models.py* using the editor of your choice,
    such as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ...
 
@@ -352,8 +350,8 @@ and modify a view stored in database.
 In order to be applied in existing databases, such as your production database,
 these changes requires the module to be updated.
 
-If you would like the update to be performed automatically by the Odoo.sh platform when you push
-your changes, increase your module version in its manifest.
+If you would like the update to be performed automatically by the Odoo.sh platform when you push your changes,
+increase your module version in its manifest.
 
 Open the module manifest *__manifest__.py*.
 
@@ -369,8 +367,7 @@ with
 
   'version': '0.2',
 
-The platform will detect the change of version and trigger the update of the module upon the new
-revision deployment.
+The platform will detect the change of version and trigger the update of the module upon the new revision deployment.
 
 Browse to your Git folder.
 
@@ -414,13 +411,13 @@ Or, from your computer terminal:
 
 The platform will then create a new build for the branch *feature-1*.
 
-.. image:: first_module/firstmodule-test-addachange-build.png
-   :align: center
+.. image:: ./media/firstmodule-test-addachange-build.png
+  :align: center
 
-Once you tested your changes, you can merge your changes in the production branch, for instance by
-drag-and-dropping the branch on the production branch in the Odoo.sh interface. As you increased the
-module version in the manifest, the platform will update the module automatically and your new field
-will be directly available. Otherwise you can manually update the module within the apps list.
+Once you tested your changes, you can merge your changes in the production branch, for instance by drag-and-dropping the
+branch on the production branch in the Odoo.sh interface. As you increased the module version in the manifest,
+the platform will update the module automatically and your new field will be directly available.
+Otherwise you can manually update the module within the apps list.
 
 Use an external Python library
 ==============================
@@ -428,18 +425,10 @@ Use an external Python library
 If you would like to use an external Python library which is not installed by default,
 you can define a *requirements.txt* file listing the external libraries your modules depends on.
 
-.. note::
-   - It is not possible to install or upgrade system packages on an Odoo.sh database (e.g., apt
-     packages). However, under specific conditions, packages can be considered for installation.
-     This also applies to **Python modules** requiring system packages for their compilation, and
-     **third-party Odoo modules**.
-   - **PostgreSQL extensions** are not supported on Odoo.sh.
-   - For more information, consult our `FAQ <https://www.odoo.sh/faq#install_dependencies>`_.
-
 The platform will use this file to automatically install the Python libraries your project needs.
 
-The feature is explained in this section by using the `Unidecode library
-<https://pypi.python.org/pypi/Unidecode>`_ in your module.
+The feature is explained in this section by using the `Unidecode library <https://pypi.python.org/pypi/Unidecode>`_ in
+your module.
 
 Create a file *requirements.txt* in the root folder of your repository
 
@@ -453,8 +442,8 @@ Add
 
   unidecode
 
-Then use the library in your module, for instance to remove accents from characters in the name
-field of your model.
+Then use the library in your module, for instance to remove accents from characters in the name field of your
+model.
 
 Open the file *models/models.py*.