khanh.pndc/odoo-docs
1
0
Fork 0
mirror of https://github.com/odoo/documentation.git synced 2025-12-12 07:29:27 +07:00
Code Issues Packages Projects Releases Wiki Activity
Files
6874b14169c35b19bb47fa2864c1e61c3c8ca9a3
odoo-docs/locale/sources/administration.pot
Tiffany Chang (tic) 6874b14169 [I18N] *: re-export pot files 
As per usual, leave off developer.pot and contributing.pot since we
don't translate them (not useful, can't really contribute to/dev in
Odoo without knowing English)

closes odoo/documentation#15640

Signed-off-by: Dylan Kiss (dyki) <dyki@odoo.com>
Signed-off-by: Tiffany Chang (tic) <tic@odoo.com>
2025-12-11 13:23:46 +00:00

6135 lines
290 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 19.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-12-11 10:43+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: ../../content/administration.rst:8
msgid "Database management"
msgstr ""
#: ../../content/administration.rst:10
msgid "These guides provide instructions on how to install, maintain and upgrade Odoo databases."
msgstr ""
#: ../../content/administration.rst:13
msgid ":doc:`History of Versions <administration/supported_versions>`"
msgstr ""
#: ../../content/administration.rst:16
#: ../../content/administration/on_premise/geo_ip.rst:9
msgid "Installation"
msgstr ""
#: ../../content/administration.rst:18
msgid "Depending on the intended use case, there are multiple ways to install Odoo - or not install it at all."
msgstr ""
#: ../../content/administration.rst:21
msgid ":doc:`Online <administration/odoo_online>` is the easiest way to use Odoo in production or to try it."
msgstr ""
#: ../../content/administration.rst:23
msgid ":doc:`Packaged installers <administration/on_premise/packages>` are suitable for testing Odoo and developing modules. They can be used for long-term production with additional deployment and maintenance work."
msgstr ""
#: ../../content/administration.rst:27
msgid ":doc:`Source install <administration/on_premise/source>` provides greater flexibility, as it allows, for example, running multiple Odoo versions on the same system. It is adequate to develop modules and can be used as a base for production deployment."
msgstr ""
#: ../../content/administration.rst:31
msgid "A `Docker <https://hub.docker.com/_/odoo/>`_ base image is available for development or deployment."
msgstr ""
#: ../../content/administration.rst:37
msgid "Editions"
msgstr ""
#: ../../content/administration.rst:39
msgid "There are two different editions."
msgstr ""
#: ../../content/administration.rst:41
msgid "**Odoo Community** is the free and open-source version of the software, licensed under the `GNU LGPLv3 <https://github.com/odoo/odoo/blob/master/LICENSE>`_. It is the core upon which Odoo Enterprise is built."
msgstr ""
#: ../../content/administration.rst:45
msgid "**Odoo Enterprise** is the shared source version of the software, giving access to more functionalities, including functional support, upgrades, and hosting. `Pricing <https://www.odoo.com/pricing-plan>`_ starts from one app free."
msgstr ""
#: ../../content/administration.rst:50
msgid ":doc:`Switch from Community to Enterprise <administration/on_premise/community_to_enterprise>` at any time (except for the source install)."
msgstr ""
#: ../../content/administration/hosting.rst:3
msgid "Hosting"
msgstr ""
#: ../../content/administration/hosting.rst:8
msgid "Change hosting solution"
msgstr ""
#: ../../content/administration/hosting.rst:10
msgid "The instructions to change the hosting type of a database depend on the current solution used and to which solution the database should be moved."
msgstr ""
#: ../../content/administration/hosting.rst:14
msgid "Transferring an on-premise database"
msgstr ""
#: ../../content/administration/hosting.rst:17
#: ../../content/administration/hosting.rst:92
msgid "To Odoo Online"
msgstr ""
#: ../../content/administration/hosting.rst:20
#: ../../content/administration/hosting.rst:95
msgid "Odoo Online is *not* compatible with **non-standard apps**."
msgstr ""
#: ../../content/administration/hosting.rst:21
msgid "The database's current version must be :doc:`supported <supported_versions>`."
msgstr ""
#: ../../content/administration/hosting.rst:23
msgid "Create a :ref:`duplicate of the database <on-premise/duplicate>`."
msgstr ""
#: ../../content/administration/hosting.rst:24
msgid "In this duplicate, uninstall all **non-standard apps**."
msgstr ""
#: ../../content/administration/hosting.rst:25
msgid "Use the database manager to grab a *dump with filestore*."
msgstr ""
#: ../../content/administration/hosting.rst:26
#: ../../content/administration/hosting.rst:98
msgid "`Create a support ticket <https://www.odoo.com/help-form>`_ including the following:"
msgstr ""
#: ../../content/administration/hosting.rst:28
#: ../../content/administration/hosting.rst:100
msgid "your **subscription number**,"
msgstr ""
#: ../../content/administration/hosting.rst:29
msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`), and"
msgstr ""
#: ../../content/administration/hosting.rst:30
msgid "the **dump** as an attachment or as a link to the file (required for 60 MB+ files)."
msgstr ""
#: ../../content/administration/hosting.rst:32
#: ../../content/administration/hosting.rst:107
msgid "Odoo then makes sure the database is compatible before putting it online. In case of technical issues during the process, Odoo might contact you."
msgstr ""
#: ../../content/administration/hosting.rst:36
#: ../../content/administration/hosting.rst:111
msgid "If you have time constraints, `create a support ticket <https://www.odoo.com/help-form>`_ as soon as possible to schedule the transfer."
msgstr ""
#: ../../content/administration/hosting.rst:40
#: ../../content/administration/hosting.rst:78
msgid "To Odoo.sh"
msgstr ""
#: ../../content/administration/hosting.rst:42
#: ../../content/administration/hosting.rst:85
msgid "Follow the instructions found in :ref:`the Import a database section <odoo-sh/create/import>` of the Odoo.sh *Create a project* documentation."
msgstr ""
#: ../../content/administration/hosting.rst:46
msgid "Transferring an Odoo Online database"
msgstr ""
#: ../../content/administration/hosting.rst:49
msgid "Odoo Online's :ref:`intermediary versions <supported_versions>` are not supported by Odoo.sh or on-premise. Therefore, if the database to transfer is running an intermediary version, it must be upgraded first to the next :ref:`major version <supported_versions>`, waiting for its release if necessary."
msgstr ""
#: ../../content/administration/hosting.rst:55
msgid "Transferring an online database running on Odoo 16.3 would require first upgrading it to Odoo 17.0."
msgstr ""
#: ../../content/administration/hosting.rst:59
msgid "Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database name on the `Odoo Online database manager <https://www.odoo.com/my/databases/>`_ to display its version number."
msgstr ""
#: ../../content/administration/hosting.rst:63
msgid "If there is an active Odoo subscription linked to the database being migrated, reach out to the Customer Service Manager or `contact Odoo support <https://www.odoo.com/help>`_ to complete the subscription transfer."
msgstr ""
#: ../../content/administration/hosting.rst:68
#: ../../content/administration/hosting.rst:120
msgid "To on-premise"
msgstr ""
#: ../../content/administration/hosting.rst:70
#: ../../content/administration/hosting.rst:80
msgid "Download a database backup by signing in to `the Odoo Online database manager <https://www.odoo.com/my/databases/>`_, clicking the :icon:`fa-gear` (:guilabel:`gear`) button next to the database name, then selecting :icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to the file being too large, `contact Odoo support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/hosting.rst:75
#: ../../content/administration/hosting.rst:123
msgid "Restore the database from the database manager on your local server using the backup."
msgstr ""
#: ../../content/administration/hosting.rst:89
msgid "Transferring an Odoo.sh database"
msgstr ""
#: ../../content/administration/hosting.rst:97
msgid "Uninstall all **non-standard apps** in a staging build before doing it in the production build."
msgstr ""
#: ../../content/administration/hosting.rst:101
msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`),"
msgstr ""
#: ../../content/administration/hosting.rst:102
msgid "which **branch** should be migrated,"
msgstr ""
#: ../../content/administration/hosting.rst:103
msgid "in which **region** you want the database to be hosted (Americas, Europe, or Asia),"
msgstr ""
#: ../../content/administration/hosting.rst:104
msgid "which user(s) will be the **administrator(s)**, and"
msgstr ""
#: ../../content/administration/hosting.rst:105
msgid "**when** (and in which timezone) you want the database to be up and running."
msgstr ""
#: ../../content/administration/hosting.rst:113
msgid "Select the **region** closest to most of your users to reduce latency."
msgstr ""
#: ../../content/administration/hosting.rst:114
msgid "Future **administrator(s)** must have an Odoo.com account."
msgstr ""
#: ../../content/administration/hosting.rst:115
msgid "The **date and time** you want the database to be up and running are helpful to organize the switch from the Odoo.sh server to the Odoo Online servers."
msgstr ""
#: ../../content/administration/hosting.rst:117
msgid "Databases are **not reachable** during their migration."
msgstr ""
#: ../../content/administration/hosting.rst:122
msgid "Download a :ref:`backup of your Odoo.sh production database <odoo-sh/branches/tabs/backups>`."
msgstr ""
#: ../../content/administration/mobile.rst:3
msgid "Odoo mobile apps"
msgstr ""
#: ../../content/administration/mobile.rst:5
msgid "Two kind of Odoo mobile app exist: the progressive web app (PWA) and store apps. Using the PWA is recommended."
msgstr ""
#: ../../content/administration/mobile.rst:9
msgid "Progressive web app (PWA)"
msgstr ""
#: ../../content/administration/mobile.rst:11
msgid "PWAs are web-based applications designed to function across different devices and platforms, leveraging web browsers to deliver user experiences similar to native apps."
msgstr ""
#: ../../content/administration/mobile.rst:14
msgid "The Odoo PWA features include:"
msgstr ""
#: ../../content/administration/mobile.rst:16
msgid "Quick access by adding the PWA to a device's home screen"
msgstr ""
#: ../../content/administration/mobile.rst:17
msgid "Seamless and borderless navigation experience"
msgstr ""
#: ../../content/administration/mobile.rst:18
msgid "Push notifications"
msgstr ""
#: ../../content/administration/mobile.rst:19
msgid "SSO authentication"
msgstr ""
#: ../../content/administration/mobile.rst:21
msgid "To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an Odoo database. The instructions to install a PWA depend on the platform and browser used."
msgstr ""
#: ../../content/administration/mobile.rst:26
msgid "Android"
msgstr ""
#: ../../content/administration/mobile.rst:28
msgid "**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install app`, and tap :guilabel:`Install`."
msgstr ""
#: ../../content/administration/mobile.rst:31
msgid "**Firefox**: open Firefox's menu (:guilabel:`⋮`), select :guilabel:`Install`, and either touch and hold the Odoo icon or tap :guilabel:`Add automatically`."
msgstr ""
#: ../../content/administration/mobile.rst:34
msgid "The PWA can also be installed with **Samsung Internet**, **Edge**, and **Opera**."
msgstr ""
#: ../../content/administration/mobile.rst:36
msgid "iOS"
msgstr ""
#: ../../content/administration/mobile.rst:38
msgid "**Safari**: open the **Share** menu by tapping the square with an arrow pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA details if desired, and tap :guilabel:`Add`."
msgstr ""
#: ../../content/administration/mobile.rst:42
msgid "On iOS 16.4 and above, the PWA can also be installed with **Chrome**, **Firefox**, and **Edge**."
msgstr ""
#: ../../content/administration/mobile.rst:45
msgid "Desktop"
msgstr ""
#: ../../content/administration/mobile.rst:47
msgid "**Chrome** and **Edge**: click the installation icon at the right of the address bar and click :guilabel:`Install`."
msgstr ""
#: ../../content/administration/mobile.rst:51
msgid "`Google Chrome Help: Use progressive web apps <https://support.google.com/chrome/answer/9658361>`_"
msgstr ""
#: ../../content/administration/mobile.rst:53
msgid "`MDN Web Docs: Installing and uninstalling web apps <https://developer.mozilla.org/en-US/docs/Web/Progressive_web_apps/Guides/Installing>`_"
msgstr ""
#: ../../content/administration/mobile.rst:55
msgid "`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge <https://support.microsoft.com/en-us/topic/install-manage-or-uninstall-apps-in-microsoft-edge-0c156575-a94a-45e4-a54f-3a84846f6113>`_"
msgstr ""
#: ../../content/administration/mobile.rst:58
msgid "Store apps"
msgstr ""
#: ../../content/administration/mobile.rst:60
msgid "The Odoo mobile apps are available for download on the `Google Play Store <https://play.google.com/store/apps/details?id=com.odoo.mobile>`_ and `Apple App Store <https://apps.apple.com/app/odoo/id1272543640>`_."
msgstr ""
#: ../../content/administration/mobile.rst:65
msgid "The iOS app might not be updated and might be deprecated at some point in the future."
msgstr ""
#: ../../content/administration/mobile.rst:67
msgid "While the store apps support multi-accounts, they are not compatible with SSO authentication."
msgstr ""
#: ../../content/administration/neutralized_database.rst:3
msgid "Neutralized database"
msgstr ""
#: ../../content/administration/neutralized_database.rst:5
msgid "A neutralized database is a non-production database on which several parameters are deactivated. This enables one to carry out tests without the risk of launching specific automated processes that could impact production data (e.g., sending emails to customers). Live access is removed and turned into a testing environment."
msgstr ""
#: ../../content/administration/neutralized_database.rst:11
msgid "**Any testing database created is a neutralized database:**"
msgstr ""
#: ../../content/administration/neutralized_database.rst:13
msgid "testing backup databases"
msgstr ""
#: ../../content/administration/neutralized_database.rst:14
msgid "duplicate databases"
msgstr ""
#: ../../content/administration/neutralized_database.rst:15
msgid "for Odoo.sh: staging and development databases"
msgstr ""
#: ../../content/administration/neutralized_database.rst:18
msgid "A database can also be neutralized when upgrading, as it is vital to do some tests before switching to a new version."
msgstr ""
#: ../../content/administration/neutralized_database.rst:22
msgid "Deactivated features"
msgstr ""
#: ../../content/administration/neutralized_database.rst:24
msgid "Here is a non-exhaustive list of the deactivated features:"
msgstr ""
#: ../../content/administration/neutralized_database.rst:26
msgid "all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)"
msgstr ""
#: ../../content/administration/neutralized_database.rst:27
msgid "outgoing emails"
msgstr ""
#: ../../content/administration/neutralized_database.rst:28
msgid "bank synchronization"
msgstr ""
#: ../../content/administration/neutralized_database.rst:29
msgid "payment providers"
msgstr ""
#: ../../content/administration/neutralized_database.rst:30
msgid "delivery methods"
msgstr ""
#: ../../content/administration/neutralized_database.rst:31
msgid ":abbr:`IAP (In-App Purchase)` tokens"
msgstr ""
#: ../../content/administration/neutralized_database.rst:32
msgid "website visibility (prevent search engines from indexing your site)"
msgstr ""
#: ../../content/administration/neutralized_database.rst:35
msgid "**A red banner at the top of the screen is displayed on the neutralized database so that it can be seen immediately.**"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:3
msgid "Odoo.com account"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:5
msgid "Open the `Connection & Security page <https://www.odoo.com/my/security>`_ on your Odoo.com account portal to:"
msgstr ""
#: ../../content/administration/odoo_accounts.rst:8
msgid "Change your :guilabel:`Password`."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:11
msgid "When you create a database, a user linked to your Odoo.com account is generated on the database. Changing your Odoo.com account's password will also modify the password used to sign in with that user to the database."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:14
msgid "You can set a database-specific password for that user by going to the :ref:`database's settings <users/change-password>`. However, you will still be able to sign in with your Odoo.com account's password."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:18
msgid "Enable :guilabel:`Two-factor authentication` using an authenticator app."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:21
msgid "Refer to the :doc:`Two-factor authentication documentation <../applications/general/users/2fa>` for more information. The process to enable it for a database user and for your Odoo.com account is similar."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:25
msgid ":guilabel:`Log out from all devices` signed in to your Odoo.com account, except for the current session."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:29
msgid "To log out from the current session, click the :icon:`fa-user-circle-o` (:guilabel:`user`) icon in the top right and select :icon:`fa-sign-out` :guilabel:`Logout`."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:32
msgid "Enable :ref:`developer mode <developer-mode>` to add a :ref:`developer API key <api/external_api/keys>`."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:35
msgid ":guilabel:`Delete` your account."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:38
msgid "Deleting your Odoo.com account is **irreversible**. Once deleted, your account **cannot be retrieved**."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:41
msgid "Open the `Account Information page <https://www.odoo.com/my/account>`_ to edit your account details, including your **email address**."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:45
msgid "When you create a database, a user linked to your Odoo.com account is generated on the database. Changing your Odoo.com account's email address does not modify the email address used to sign in with that user."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:48
msgid "You can set a database-specific email address for that user by clicking your avatar in the top-right corner of the database and selecting :guilabel:`My Preferences`. You will still need to sign in to the database using the email address used at the time of the database creation."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:51
msgid "To change the email address used to sign in to a database, `contact Odoo Support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_accounts.rst:55
msgid "In addition to the database you create, all databases you are :ref:`invited to join <users/add-individual>` with your Odoo.com account's email address will be displayed under the `database manager <https://www.odoo.com/my/databases>`_."
msgstr ""
#: ../../content/administration/odoo_online.rst:3
#: ../../content/administration/odoo_sh/getting_started/create.rst:121
#: ../../content/administration/supported_versions.rst:29
#: ../../content/administration/upgrade.rst:14
#: ../../content/administration/upgrade.rst:109
#: ../../content/administration/upgrade.rst:330
msgid "Odoo Online"
msgstr ""
#: ../../content/administration/odoo_online.rst:5
msgid "`Odoo Online <https://www.odoo.com/trial>`_ offers private databases hosted and managed by Odoo. Odoo Online databases can be accessed using any web browser and do not require a local installation. They can be used for long-term production or to thoroughly test Odoo, including customizations that do not require custom code."
msgstr ""
#: ../../content/administration/odoo_online.rst:11
msgid "To quickly try out Odoo, shared `demo databases <https://demo.odoo.com>`_ are available for testing. No registration is required; however, each database is only available for a few hours."
msgstr ""
#: ../../content/administration/odoo_online.rst:15
msgid "Odoo Online is incompatible with custom modules or modules from the `Odoo Apps Store <https://apps.odoo.com/apps>`_."
msgstr ""
#: ../../content/administration/odoo_online.rst:21
msgid "Database manager"
msgstr ""
#: ../../content/administration/odoo_online.rst:23
msgid "To manage an Odoo Online database, open to the `database manager <https://www.odoo.com/my/databases>`_ and sign in as the database administrator."
msgstr ""
#: ../../content/administration/odoo_online.rst:29
msgid "Domain names"
msgstr ""
#: ../../content/administration/odoo_online.rst:31
msgid ":doc:`Configure a custom domain name <../applications/websites/website/configuration/domain_names>` by selecting a database and clicking :icon:`fa-globe` :guilabel:`Domain Names`."
msgstr ""
#: ../../content/administration/odoo_online.rst:35
msgid ":ref:`Register a domain name for free <domain-name/register>`."
msgstr ""
#: ../../content/administration/odoo_online.rst:40
msgid "Tags"
msgstr ""
#: ../../content/administration/odoo_online.rst:42
msgid "Add tags to identify and sort databases by selecting a database and clicking :icon:`fa-tags` :guilabel:`Tags`. In the dialog box, enter a tag, click the :icon:`fa-plus-circle` (:guilabel:`plus`) button, and click :guilabel:`Save`."
msgstr ""
#: ../../content/administration/odoo_online.rst:47
msgid "Search for tags in the :icon:`fa-search` search bar at the top right."
msgstr ""
#: ../../content/administration/odoo_online.rst:52
msgid "Hide"
msgstr ""
#: ../../content/administration/odoo_online.rst:54
msgid "Permanently hide the database from the database manager by selecting it and clicking :icon:`fa-eye-slash` :guilabel:`Hide`. In the dialog box, click :guilabel:`Yes, I don't need it anymore`."
msgstr ""
#: ../../content/administration/odoo_online.rst:59
msgid "It is possible to access a hidden database through its URL."
msgstr ""
#: ../../content/administration/odoo_online.rst:64
msgid "Manage"
msgstr ""
#: ../../content/administration/odoo_online.rst:66
msgid "Access all other database management options by selecting it and clicking :icon:`fa-gears` :guilabel:`Manage`."
msgstr ""
#: ../../content/administration/odoo_online.rst:70
msgid "Switch plans"
msgstr ""
#: ../../content/administration/odoo_online.rst:72
msgid "Switch `pricing plans <https://www.odoo.com/pricing>`_ by clicking :guilabel:`Switch` under the desired plan."
msgstr ""
#: ../../content/administration/odoo_online.rst:78
#: ../../content/administration/odoo_sh/getting_started/branches.rst:521
#: ../../content/administration/odoo_sh/getting_started/settings.rst:123
#: ../../content/administration/odoo_sh/getting_started/settings.rst:168
#: ../../content/administration/upgrade.rst:3
msgid "Upgrade"
msgstr ""
#: ../../content/administration/odoo_online.rst:80
msgid "Launch a :ref:`database upgrade <upgrade-request-test>` by clicking :guilabel:`Upgrade`."
msgstr ""
#: ../../content/administration/odoo_online.rst:83
msgid "This option is only displayed when an upgrade is available."
msgstr ""
#: ../../content/administration/odoo_online.rst:88
msgid "Rename"
msgstr ""
#: ../../content/administration/odoo_online.rst:90
msgid "Rename and change the URL of a database by clicking :guilabel:`Rename`. In the dialog box, enter a :guilabel:`New name` and click :guilabel:`Rename`."
msgstr ""
#: ../../content/administration/odoo_online.rst:96
msgid "Duplicate"
msgstr ""
#: ../../content/administration/odoo_online.rst:98
msgid "Create a copy of the database by clicking :guilabel:`Duplicate`. In the dialog box, enter a :guilabel:`New name` and click :guilabel:`Duplicate`."
msgstr ""
#: ../../content/administration/odoo_online.rst:102
msgid "By default, the :guilabel:`For testing purposes` option is enabled. It disables all external actions (emails, payments, delivery orders, etc.) on the duplicated database."
msgstr ""
#: ../../content/administration/odoo_online.rst:104
msgid "Duplicates expire after 15 days."
msgstr ""
#: ../../content/administration/odoo_online.rst:105
msgid "A maximum of five duplicates can be created per database. Under extraordinary circumstances, contact `Odoo Support <https://www.odoo.com/help>`_ to extend the limit."
msgstr ""
#: ../../content/administration/odoo_online.rst:111
#: ../../content/administration/odoo_sh/getting_started/create.rst:97
msgid "Download a backup"
msgstr ""
#: ../../content/administration/odoo_online.rst:113
msgid "Download a ZIP file containing a database backup by clicking :guilabel:`Download Backup`."
msgstr ""
#: ../../content/administration/odoo_online.rst:116
msgid "Databases are backed up daily as per the `Odoo Cloud Hosting SLA <https://www.odoo.com/cloud-sla>`_."
msgstr ""
#: ../../content/administration/odoo_online.rst:118
msgid "If the :guilabel:`Download Backup` option is disabled, it means the database is too large to be downloaded using the database manager. Contact `Odoo Support <https://www.odoo.com/help>`_ to request an alternative download solution."
msgstr ""
#: ../../content/administration/odoo_online.rst:125
msgid "View admin activity logs"
msgstr ""
#: ../../content/administration/odoo_online.rst:127
msgid "View the logs of all actions taken by Odoo employees or the database administrator on the database by clicking :guilabel:`View Admin Activity Logs`."
msgstr ""
#: ../../content/administration/odoo_online.rst:131
msgid "Actions taken by Odoo employees are typically the result of requests submitted to Odoo support, done within the context of a quick start project, or necessary to maintain the database."
msgstr ""
#: ../../content/administration/odoo_online.rst:137
msgid "Transfer ownership"
msgstr ""
#: ../../content/administration/odoo_online.rst:139
msgid "Create a support ticket to request a database ownership transfer by clicking :guilabel:`Transfer Ownership`."
msgstr ""
#: ../../content/administration/odoo_online.rst:145
#: ../../content/administration/odoo_sh/getting_started/branches.rst:803
msgid "Delete"
msgstr ""
#: ../../content/administration/odoo_online.rst:147
msgid "Delete the database and close its related subscription by clicking :guilabel:`Delete`. In the dialog box, click :guilabel:`Delete`."
msgstr ""
#: ../../content/administration/odoo_online.rst:151
msgid "All the database's data will be deleted instaneously for all users and **cannot be restored**. It is recommended to :ref:`download a backup <odoo-online/download>` before deleting a database."
msgstr ""
#: ../../content/administration/odoo_online.rst:155
msgid "After deletion, the database's name becomes available to anyone."
msgstr ""
#: ../../content/administration/odoo_online.rst:160
msgid "Web services"
msgstr ""
#: ../../content/administration/odoo_online.rst:162
msgid "To retrieve a list of all databases displayed under the `database manager <https://www.odoo.com/my/databases>`_ programmatically, call the `list` method of the `odoo.database` model via an :doc:`external JSON-2 API <../developer/reference/external_api>` call."
msgstr ""
#: ../../content/administration/odoo_sh.rst:6
#: ../../content/administration/supported_versions.rst:30
#: ../../content/administration/upgrade.rst:22
#: ../../content/administration/upgrade.rst:132
#: ../../content/administration/upgrade.rst:341
msgid "Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh.rst:8
msgid "Odoo.sh is the official cloud platform for hosting and managing Odoo applications. It offers a range of features such as web shell, module dependencies, continuous integration, and SSH access."
msgstr ""
#: ../../content/administration/odoo_sh/advanced.rst:5
msgid "Advanced"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:4
msgid "Containers"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:7
#: ../../content/administration/odoo_sh/advanced/submodules.rst:9
#: ../../content/administration/odoo_sh/first_module.rst:6
#: ../../content/administration/odoo_sh/getting_started/builds.rst:14
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9
#: ../../content/administration/odoo_sh/getting_started/settings.rst:6
#: ../../content/administration/odoo_sh/getting_started/status.rst:6
msgid "Overview"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:9
msgid "Each build is isolated within its own container (Linux namespaced container)."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:11
msgid "The base is an Ubuntu system, where all of Odoo's required dependencies, as well as common useful packages, are installed."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:14
msgid "If your project requires additional Python dependencies, or more recent releases, you can define a :file:`requirements.txt` file in the root of your branches listing them. 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 <https://github.com/odoo/odoo/blob/19.0/requirements.txt>`_."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:22
msgid "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, but in their parent folder."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:27
msgid "Directory structure"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:29
msgid "As the containers are Ubuntu based, their directory structure follows the linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview <https://help.ubuntu.com/community/LinuxFilesystemTreeOverview#Main_directories>`_ explains the main directories."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:33
msgid "Here are the Odoo.sh pertinent directories:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:73
msgid "Both Python 2.7 and 3.5 are installed in the containers. However:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:75
msgid "If your project is configured to use Odoo 10.0, the Odoo server runs with Python 2.7."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:76
msgid "If your project is configured to use Odoo 11.0 or above, the Odoo server runs with Python 3.5."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:79
msgid "Database shell"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:81
msgid "While accessing a container with the shell, you can access the database using *psql*."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:92
msgid "**Be careful !** `Use transactions <https://www.postgresql.org/docs/current/static/sql-begin.html>`_ (*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes (*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:97
msgid "The transaction mechanism is your safety net in case of mistake. You simply have to rollback your changes to revert your database to its previous state."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:100
msgid "For example, it may happen that you forget to set your *WHERE* condition."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:111
msgid "In such a case, you can rollback to revert the unwanted changes that you just mistakenly did, and rewrite the statement:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:122
msgid "However, do not forget to either commit or rollback your transaction after having done it. Open transactions may lock records in your tables and your running database may wait for them to be released. It can cause a server to hang indefinitely."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:126
msgid "In addition, when possible, use your staging databases to test your statements first. It gives you an extra safety net."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:129
msgid "Run an Odoo server"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:131
msgid "You can start an Odoo server instance from a container shell. You won't be able to access it from the outside world with a browser, but you can for instance:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:134
msgid "use the Odoo shell,"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:146
msgid "install a module,"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:152
msgid "update a module,"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:158
msgid "run the tests for a module,"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:164
msgid "In the above commands, the argument:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:166
msgid "``--stop-after-init`` will immediately shutdown the server instance after it completed the operations you asked."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:168
msgid "More options are available and detailed in the :doc:`CLI documentation </developer/reference/cli>`."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:171
msgid "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*\":"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:180
msgid "**Be careful**, especially with your production database. Operations that you perform running this Odoo server instance are not isolated: Changes will be effective in the database. Always, make your tests in your staging databases."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:185
msgid "Debugging in Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:187
msgid "Debugging an Odoo.sh build is not really different than another Python app. This article only explains the specificities and limitations of the Odoo.sh platform, and assumes that you already know how to use a debugger."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:189
msgid "If you don't know how to debug a Python application yet, there are multiple introductory courses that can be easily found on the Internet."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:191
msgid "You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As the server is run outside a shell, you cannot launch the debugger directly from your Odoo instance backend as the debugger needs a shell to operate."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:194
msgid "`pdb <https://docs.python.org/3/library/pdb.html>`_ is installed by default in every container."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:196
msgid "If you want to use `pudb <https://pypi.org/project/pudb/>`_ or `ipdb <https://pypi.org/project/ipdb/>`_ you have to install it before."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:198
msgid "To do so, you have two options:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:200
msgid "temporary (only in the current build):"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:206
msgid "or"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:212
msgid "permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` file."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:215
msgid "Then edit the code where you want to trigger the debugger and add this:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:223
msgid "The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you run Odoo from a shell."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:225
msgid "Save the file and then run the Odoo Shell:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:231
msgid "Finally, *via* the Odoo Shell, you can trigger the piece of code/function/method you want to debug."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:-1
msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6
msgid "Frequent Technical Questions"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9
msgid "\"Scheduled actions do not run at the exact time they were expected\""
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11
msgid "On the Odoo.sh platform, we cannot guarantee an exact running time for scheduled actions."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13
msgid "This is due to the fact that there might be multiple customers on the same server, and we must guarantee a fair share of the server for every customer. Scheduled actions are therefore implemented slightly differently than on a regular Odoo server, and are run on a *best effort* policy."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16
msgid "Do not expect any scheduled action to be run more often than every 5 min."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19
msgid "Are there \"best practices\" regarding scheduled actions?"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21
msgid "**Odoo.sh always limits the execution time of scheduled actions (*aka* crons).** Therefore, you must keep this fact in mind when developing your own crons."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24
msgid "We advise that:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26
msgid "Your scheduled actions should work on small batches of records."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27
msgid "Your scheduled actions should commit their work after processing each batch; this way, if they get interrupted by the time-limit, there is no need to start over."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36
msgid "How can I automate tasks when an IP address change occurs?"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38
msgid "**Odoo.sh notifies project administrators of IP address changes.** Additionally, when the IP address of a production instance changes, an HTTP `GET` request is made to the path `/_odoo.sh/ip-change` with the new IP address included as a query string parameter (`new`), along with the previous IP address as an additional parameter (`old`)."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43
msgid "This mechanism allows custom actions to be applied in response to the IP address change (e.g., sending an email, contacting a firewall API, configuring database objects, etc.)"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46
msgid "For security reasons, the `/_odoo.sh/ip-change` route is accessible only internally by the platform itself and returns a `403` response if accessed through any other means."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49
msgid "Here is a pseudo-implementation example:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:6
#: ../../content/administration/odoo_sh/getting_started/settings.rst:249
msgid "Submodules"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:11
msgid "A `Git submodule <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ allows you to integrate other Git projects into your code, without the need to copy-paste all their code."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:14
msgid "Indeed, your custom modules can depend on modules from other repositories. Regarding Odoo, this feature allows you to add modules from other Git repositories into the branches of your repository. Adding these dependencies in your branch through submodules makes the deployment of your code and servers easier, as you can clone the repositories added as submodules at the same time you clone your own repository."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:19
msgid "Besides, you can choose the branch of the repository added as submodule and you have the control of the revision you want. It's up to you to decide whether you want to pin the submodule to a specific revision and when you want to update to a newer revision."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:24
msgid "In Odoo.sh, the submodules give you the possibility to use and depend on modules available in other repositories. The platform will detect that you added modules through submodules in your branches and add them to your addons path automatically so you can install them in your databases."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:28
msgid "If you add private repositories as submodules in your branches, you need to configure a deploy key in your Odoo.sh project settings and in your repository settings. Otherwise Odoo.sh won't be allowed to download them. The procedure is detailed in the chapter :ref:`Settings > Submodules <odoosh-gettingstarted-settings-submodules>`."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:34
msgid "Adding a submodule"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:37
msgid "With Odoo.sh (simple)"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:40
msgid "For now it is not possible to add **private** repositories with this method. You can nevertheless do so :ref:`with Git <odoosh-advanced-submodules-withgit>`."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:43
msgid "On Odoo.sh, in the branches view of your project, choose the branch in which you want to add a submodule."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:45
msgid "In the upper right corner, click on the *Submodule* button, and then on *Run*."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:50
msgid "A dialog with a form is shown. Fill the inputs as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:52
msgid "Repository URL: The SSH URL of the repository."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:53
msgid "Branch: The branch you want to use."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:54
msgid "Path: The folder in which you want to add this submodule in your branch."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:59
msgid "On Github, you can get the repository URL with the *Clone or download* button of the repository. Make sure to *use SSH*."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:67
msgid "With Git (advanced)"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:69
msgid "In a terminal, in the folder where your Git repository is cloned, checkout the branch in which you want to add a submodule:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:76
msgid "Then, add the submodule using the command below:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:82
#: ../../content/administration/odoo_sh/advanced/submodules.rst:94
#: ../../content/administration/odoo_sh/first_module.rst:362
#: ../../content/administration/odoo_sh/first_module.rst:501
msgid "Replace"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:84
msgid "*<git@yourprovider.com>:<username/repository.git>* by the SSH URL of the repository you want to add as submodule,"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:85
msgid "*<branch>* by the branch you want to use in the above repository,"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:86
msgid "*<path>* by the folder in which you want to add this submodule."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:88
msgid "Commit and push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:96
msgid "<remote> by the repository on which you want to push your changes. For a standard Git setup, this is *origin*."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:97
msgid "<branch> by the branch on which you want to push your changes. Most likely the branch you used :code:`git checkout` on in the first step."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:100
msgid "You can read the `git-scm.com documentation <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ for more details about the Git submodules. For instance, if you would like to update your submodules to have their latest revision, you can follow the chapter `Pulling in Upstream changes <https://git-scm.com/book/en/v2/Git-Tools-Submodules#_pulling_in_upstream_changes_from_the_submodule_remote>`_."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:107
msgid "Ignore modules"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/submodules.rst:109
msgid "If you're adding a repository that contains a lot of modules, you may want to ignore some of them in case there are any that are installed automatically. To do so, you can prefix your submodule folder with a :code:`.`. The platform will ignore this folder and you can hand pick your modules by creating symlinks to them from another folder."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:3
msgid "Your first module"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:8
msgid "This chapter helps you to create your first Odoo module and deploy it in your Odoo.sh project."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:10
msgid "This tutorial requires you created a project on Odoo.sh, and you know your Github repository's URL."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:13
msgid "Basic use of Git and Github is explained."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:15
msgid "The below assumptions are made:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:17
msgid "*~/src* is the directory where are located the Git repositories related to your Odoo projects,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:18
msgid "*odoo* is the Github user,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:19
msgid "*odoo-addons* is the Github repository,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:20
msgid "*feature-1* is the name of a development branch,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:21
msgid "*master* is the name of the production branch,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:22
msgid "*my_module* is the name of the module."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:24
msgid "Replace these by the values of your choice."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:27
msgid "Create the development branch"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:30
msgid "From Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:32
msgid "In the branches view:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:34
msgid "hit the :code:`+` button next to the development stage,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:35
msgid "choose the branch *master* in the *Fork* selection,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:36
msgid "type *feature-1* in the *To* input."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:38
msgid "|pic1| |pic2|"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:40
#: ../../content/administration/odoo_sh/first_module.rst:40
msgid "pic1"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:43
#: ../../content/administration/odoo_sh/first_module.rst:43
msgid "pic2"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:46
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:56
msgid "From your computer"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:58
msgid "Clone your Github repository on your computer:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:67
msgid "Create a new branch:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:74
msgid "Create the module structure"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:77
msgid "Scaffolding the module"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:79
msgid "While not necessary, scaffolding avoids the tedium of setting the basic Odoo module structure. You can scaffold a new module using the executable *odoo-bin*."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:82
msgid "From the Odoo.sh editor, in a terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:88
msgid "Or, from your computer, if you have an installation of Odoo:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:94
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:98
msgid "The below structure will be generated:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:121
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:125
msgid "Uncomment the content of the files:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:127
msgid "*models/models.py*, an example of model with its fields,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:129
msgid "*views/views.xml*, a tree and a form view, with the menus opening them,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:131
msgid "*demo/demo.xml*, demo records for the above example model,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:133
msgid "*controllers/controllers.py*, an example of controller implementing some routes,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:135
msgid "*views/templates.xml*, two example qweb views used by the above controller routes,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:137
msgid "*__manifest__.py*, 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:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:146
msgid "Manually"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:148
msgid "If you want to create your module structure manually, you can follow the :doc:`/developer/tutorials/server_framework_101` tutorial to understand the structure of a module and the content of each file."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:153
msgid "Push the development branch"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:155
msgid "Stage the changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:161
#: ../../content/administration/odoo_sh/first_module.rst:397
msgid "Commit your changes"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:167
msgid "Push your changes to your remote repository"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:169
msgid "From an Odoo.sh editor terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:175
msgid "The above command is explained in the section :ref:`Commit & Push your changes <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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:183
#: ../../content/administration/odoo_sh/first_module.rst:385
#: ../../content/administration/odoo_sh/first_module.rst:411
msgid "Or, from your computer terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:189
msgid "You need to specify *-u origin feature-1* for the first push only. From that point, to push your future changes from your computer, you can simply use"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:197
msgid "Test your module"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:199
msgid "Your branch should appear in your development branches in your project."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:204
msgid "In the branches view of your project, you can click on your branch name in the left navigation panel to access its history."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:210
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:216
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:220
msgid "You can then play around with your module, create new records and test your features and buttons."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:223
msgid "Test with the production data"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:225
msgid "You need to have a production database for this step. You can create it if you do not have it yet."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:227
msgid "Once you tested your module in a development build with the demo data and believe it is ready, you can test it with the production data using a staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:230
msgid "You can either:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:232
msgid "Make your development branch a staging branch, by drag and dropping it onto the *staging* section title."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:238
msgid "Merge it in an existing staging branch, by drag and dropping it onto the given staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:243
#: ../../content/administration/odoo_sh/first_module.rst:289
msgid "You can also use the :code:`git merge` command to merge your branches."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:245
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:251
#: ../../content/administration/odoo_sh/first_module.rst:297
msgid "Once the database ready, you can access it using the *Connect* button."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:256
#: ../../content/administration/odoo_sh/first_module.rst:300
msgid "Install your module"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:258
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:263
msgid "Your module may not appear directly in your apps to install either, you need to update your apps list first:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:266
msgid "Activate the :ref:`developer mode <developer-mode>`"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:267
msgid "in the apps menu, click the *Update Apps List* button,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:268
msgid "in the dialog that appears, click the *Update* button."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:273
msgid "Your module will then appear in the list of available apps."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:279
msgid "Deploy in production"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:281
msgid "Once you tested your module in a staging branch with your production data, and believe it is ready for production, you can merge your branch in the production branch."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:284
msgid "Drag and drop your staging branch on the production branch."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:291
msgid "This will merge the latest changes of your staging branch in the production branch, and update your production server with these latest changes."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:302
msgid "Your module will not be installed automatically, you have to install it manually as explained in the :ref:`above section about installing your module in staging databases <odoosh-gettingstarted-firstmodule-productiondata-install>`."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:310
msgid "Add a change"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:312
msgid "This section explains how to add a change in your module by adding a new field in a model and deploy it."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:317
msgid "From the Odoo.sh editor,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:316
msgid "browse to your module folder *~/src/user/my_module*,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:317
msgid "then, open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:323
msgid "Or, from your computer,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:320
msgid "use the file browser of your choice to browse to your module folder *~/src/odoo-addons/my_module*,"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:322
msgid "then, open the file *models/models.py* using the editor of your choice, such as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:325
msgid "Then, after the description field"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:331
msgid "Add a datetime field"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:337
msgid "Then, open the file *views/views.xml*."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:339
#: ../../content/administration/odoo_sh/first_module.rst:475
msgid "After"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:345
#: ../../content/administration/odoo_sh/first_module.rst:452
#: ../../content/administration/odoo_sh/first_module.rst:469
#: ../../content/administration/odoo_sh/first_module.rst:481
msgid "Add"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:351
msgid "These changes alter the database structure by adding a column in a table, and modify a view stored in database."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:354
msgid "In order to be applied in existing databases, such as your production database, these changes requires the module to be updated."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:357
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:360
msgid "Open the module manifest *__manifest__.py*."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:368
#: ../../content/administration/odoo_sh/first_module.rst:507
msgid "with"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:374
msgid "The platform will detect the change of version and trigger the update of the module upon the new revision deployment."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:377
msgid "Browse to your Git folder."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:379
msgid "Then, from an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:391
msgid "Then, stage your changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:403
msgid "Push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:405
msgid "From an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:417
msgid "The platform will then create a new build for the branch *feature-1*."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:422
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:428
msgid "Use an external Python library"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:430
msgid "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."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:434
msgid "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**."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:438
msgid "**PostgreSQL extensions** are not supported on Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:439
msgid "For more information, consult our `FAQ <https://www.odoo.sh/faq#install_dependencies>`_."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:441
msgid "The platform will use this file to automatically install the Python libraries your project needs."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:443
msgid "The feature is explained in this section by using the `Unidecode library <https://pypi.python.org/pypi/Unidecode>`_ in your module."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:446
msgid "Create a file *requirements.txt* in the root folder of your repository"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:448
msgid "From the Odoo.sh editor, create and open the file ~/src/user/requirements.txt."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:450
msgid "Or, from your computer, create and open the file ~/src/odoo-addons/requirements.txt."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:458
msgid "Then use the library in your module, for instance to remove accents from characters in the name field of your model."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:461
msgid "Open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:463
msgid "Before"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:497
msgid "Adding a Python dependency requires a module version increase for the platform to install it."
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:499
msgid "Edit the module manifest *__manifest__.py*"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:513
msgid "Stage and commit your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:521
msgid "Then, push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:523
msgid "In an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/first_module.rst:529
msgid "In your computer terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:5
msgid "Getting started"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:8
msgid "Main components"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:10
msgid "When working with Odoo.sh, it is important to understand the main components involved. While they are all interconnected, each one plays a distinct role in the development and deployment of Odoo applications:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:14
msgid "**GitHub repository**: a version-controlled space where the Odoo applications' source code is stored. It tracks every change, supports collaboration, and can be either public or private."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:0
msgid "Example of a GitHub repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:20
msgid "**Odoo.sh project**: a Platform as a Service (PaaS) that integrates with GitHub and enables streamlined development, testing, and deployment of Odoo applications. It includes tools such as automated backups, staging environments, and continuous integration pipelines."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:0
msgid "Example of an Odoo.sh project"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:27
msgid "**Odoo database**: a database stores all the operational data used and generated by Odoo applications, such as business records, configurations, and user data."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:0
msgid "Example of an Odoo database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:33
msgid "Together, they form a cohesive pipeline from code development to a live business use."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:36
msgid "User types"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:38
msgid "Odoo.sh involves different types of users, each with a specific role in the project lifecycle:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:40
msgid "GitHub users: developers with access to the GitHub repository linked to the Odoo.sh project. Access to the repository does not automatically make someone a collaborator on the Odoo.sh project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:44
msgid "Odoo.sh collaborators: individuals managing the Odoo.sh project. Each collaborator must be linked to a GitHub user. However, collaborators are not the same as database users."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started.rst:47
msgid "Database users: end-users of the deployed Odoo database. They interact with the live system but are not involved in development or project management."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:3
msgid "Branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:5
msgid "The branches view provides an overview of the different branches in your repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:10
#: ../../content/administration/odoo_sh/getting_started/builds.rst:43
msgid "Stages"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:12
msgid "Odoo.sh offers three different branch stages:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:14
msgid ":ref:`Production <odoo-sh/branches/stages/production>`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:15
msgid ":ref:`Staging <odoo-sh/branches/stages/staging>`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:16
msgid ":ref:`Development <odoo-sh/branches/stages/development>`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:18
msgid "You can change the stage of a branch by dragging and dropping it under the desired stage."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "Changing the stage of a branch"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:24
msgid "Development branches can be moved under :guilabel:`Staging`. If you try to move a development branch under :guilabel:`Production`, a warning message will be displayed explaining that you can only have one production branch per project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:27
msgid "Staging branches can be moved under :guilabel:`Development`, but it is not possible to move them under :guilabel:`Production`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:29
msgid "The production branch can only be moved under :guilabel:`Development`. If you try to move it under :guilabel:`Staging`, you can only perform a merge. Refer to the :ref:`merging <odoo-sh/branches/stages/merging>` section for a detailed explanation of this process."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:37
#: ../../content/administration/odoo_sh/getting_started/branches.rst:499
#: ../../content/administration/odoo_sh/getting_started/builds.rst:48
#: ../../content/administration/odoo_sh/getting_started/settings.rst:132
msgid "Production"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:39
msgid "The production branch contains the code used to run the production database. There can be only one production branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:42
msgid "When you push a new commit to this branch, the production server is updated with the revised code and restarted."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:45
msgid "If the changes require a module update, such as changing a form view, and you want the update to be performed automatically, you can increase the module's version number in its manifest file (:file:`__manifest__.py`). The platform then performs the update, during which the instance will be held temporarily unavailable for maintenance reasons."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:50
msgid "This method is equivalent to upgrading the module using the :guilabel:`Apps` menu or the `-u` switch on :doc:`the command line <../../../developer/reference/cli>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:54
msgid "If the changes prevent the server from restarting or if the module update fails, the server is automatically reverted to the previous successful code revision, and the database is rolled back to its previous state. Access to the failed update's log to troubleshoot it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:57
msgid "The demo data is not loaded, as it is not intended for use on a production database. The `unit tests <https://en.wikipedia.org/wiki/Unit_testing>`_ are not performed, as it would increase the unavailability time of the production database during the update."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:61
msgid "Odoo.sh automatically backs up the production database. It keeps seven daily, four weekly, and three monthly backups. Each backup includes the database dump, the filestore (attachments and binary fields), logs, and sessions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:66
msgid "When using **trial projects**, the production branch and all staging branches are automatically set back to the development stage after **30 days**."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:72
#: ../../content/administration/odoo_sh/getting_started/branches.rst:502
#: ../../content/administration/odoo_sh/getting_started/builds.rst:69
#: ../../content/administration/odoo_sh/getting_started/settings.rst:87
msgid "Staging"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:74
msgid "Staging branches are meant to test new features using production data without compromising the actual production database with test records. They create neutralized duplicates of the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:78
msgid "The neutralization disables:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:80
msgid "Scheduled actions"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:83
msgid "To test them, trigger them manually or re-enable them. Be aware that the platform will trigger them less often if no one is using the database in order to save resources."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:86
msgid "Outgoing emails"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:89
msgid "They are instead intercepted using a mail catcher. An :ref:`interface to view the emails <odoo-sh/branches/tabs/mails>` sent by the database is provided in your Odoo.sh project. That way, no emails are sent to your contacts."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:93
msgid "IAP services"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:95
msgid "Payment providers and shipping connectors"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:98
msgid "They are put into test mode."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:100
msgid "If you configure or view changes in a staging database, make sure to record them (noting them step by step, reproducing in production, etc.) or write them directly in the branch's modules, using XML data files to override the default configuration or views. Check the :ref:`first module documentation <odoo-sh/module/add>` to view examples."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:106
msgid "Unit tests are not performed. They rely on demo data, which is not loaded into the production and staging databases. If Odoo starts supporting running the units without demo data, Odoo.sh will then consider running the tests on staging databases."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:110
msgid "Staging databases are not automatically backed up. Nevertheless, you can restore a backup of the production database in a staging branch for testing purposes or to manually recover data that has been accidently deleted from the production database. It is possible to create manual backups of staging databases."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:118
#: ../../content/administration/odoo_sh/getting_started/branches.rst:505
#: ../../content/administration/odoo_sh/getting_started/builds.rst:89
#: ../../content/administration/odoo_sh/getting_started/settings.rst:57
msgid "Development"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:120
msgid "Development branches create new databases using demo data to run the unit tests. The installed modules are those included in the branch. You can change this list of modules to install in the :doc:`project settings <settings>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:124
msgid "When pushing a commit to a development branch, a new server is started, with a database created from scratch, and the branch is updated. The demo data is loaded, and the unit tests are performed by default to verify that the changes do not break any of the features being tested. You can disable the tests or allow specific tests to be run with custom tags by going to the :ref:`branch's settings <odoo-sh/branches/tabs/settings>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:130
msgid "Similarly to staging branches, emails are not sent but are intercepted by a mail catcher, and scheduled actions are not triggered as long as the database is not in use."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:133
msgid "Development databases are not automatically backed up, and manual backups are not possible."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:136
msgid "Databases created for development branches are intended to last approximately three days. After that, they can be automatically garbage-collected to make room for new databases without prior notice."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:143
msgid "Merging branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:145
msgid "You can merge your branches by dragging and dropping them into each other."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "Merging branches into each other"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:150
msgid "To test the changes of development branches with the production data, you can either:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:152
msgid "Merge the development branch into a staging branch by dragging and dropping it onto the desired branch; or"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:0
msgid "Merging a development branch into a staging branch"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:158
msgid "Drag and drop the development branch under the :guilabel:`Staging` section to make it a staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:0
msgid "Moving a development branch under staging"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:164
msgid "When the changes are ready for production, drag and drop the staging branch into the production branch to merge and deploy them."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:168
msgid "You can merge development branches into the production branch directly. However, changes will not be validated against the production data through a staging branch, so there is a higher risk of encountering issues in the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:171
msgid "You can merge development branches into each other, and staging branches into each other."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:172
msgid "You can also use `git merge` directly on your workstation to merge your branches. Odoo.sh is notified when new revisions are pushed to your branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:175
msgid "Merging a staging branch into the production branch only merges the source code. Any changes made to the staging database are not passed to the production database. However, if you modify the code in the repository, it will be passed to the production branch when merging."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:179
msgid "If you test configuration changes in staging branches, and want them to be applied to the production branch, you have to, either:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:182
msgid "Write the configuration changes in XML data files to overide the default configuration or views in the branch, and then increase the version of the module in its manifest (:file:`__manifest__.py`) to trigger the module update when merging the staging branch in the production branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:187
msgid "This method is recommended for better scalability of your developments, as you will use the Git versioning features for all configuration changes, thereby ensuring traceability of your changes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:191
msgid "Pass them manually from the staging database to the production one by copying and pasting them."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:196
msgid "Tabs"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:201
#: ../../content/administration/odoo_sh/getting_started/settings.rst:58
#: ../../content/administration/odoo_sh/getting_started/settings.rst:88
#: ../../content/administration/odoo_sh/getting_started/settings.rst:133
msgid "History"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:203
msgid "The :guilabel:`History` tab gives an overview of the branch history:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:205
msgid "The commit messages and their authors"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:206
msgid "The various events linked to the platform, such as stage changes, database imports, and backup restores"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches' history tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:212
msgid "A status in the top right corner of each event indicates the current operation on the database (e.g., installation, update, backup import) or its outcome (e.g., test feedback, successful backup import). If an operation is successful, a :guilabel:`Connect` button appears, allowing you to access the database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:220
#: ../../content/administration/odoo_sh/getting_started/branches.rst:396
#: ../../content/administration/odoo_sh/getting_started/settings.rst:78
#: ../../content/administration/odoo_sh/getting_started/settings.rst:108
#: ../../content/administration/odoo_sh/getting_started/settings.rst:153
msgid "Mails"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:222
msgid "The :guilabel:`Mails` tab contains the mail catcher, which provides an overview of emails sent by the database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:226
msgid "The mail catcher is available for development and staging branches. Emails from the production database are actually sent and are not intercepted by the mail catcher."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches' mails tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:235
msgid "Shell"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:237
msgid "The :guilabel:`Shell` tab provides shell access to the container."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:239
msgid "Clicking :guilabel:`Shell` opens a new browser tab where you can run basic Linux commands (`ls`, `top`). You can open a shell on the database by running `psql`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches' shell tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:246
msgid "You can open multiple shell tabs at once and arrange their layout by dragging and dropping them."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:249
msgid "Production instance shells are highlighted in red to emphasize the danger of manipulating production instances directly, while staging/development instance shells are highlighted in yellow."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:252
msgid "Long-running shell instances/idle shell sessions can be terminated at any time to free up resources."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:258
msgid "Commands"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:260
msgid "Here is an overview of useful commands that you can run an Odoo.sh database terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:262
msgid "`odoo-bin shell`: to open an Odoo shell"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:263
msgid "`odoo-update`: to update modules in the database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:264
msgid "`odoosh-restart`: to restart Odoo.sh services (http or cron)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:265
msgid "`odoosh-storage`: to check the storage usage of your instance's container filesystem"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:266
msgid "`psql`: to open a database shell"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:267
msgid "`mutt`: to check how emails appear on text clients (staging and development instances)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:268
msgid "`lnav ~/logs/odoo.log`: to navigate in your instance's :file:`odoo.log` file"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:269
msgid "`ncdu`: to launch the disk usage analyzer with an interactive interface"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:270
msgid "`grep`: to filter and find information in log or configuration files"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:275
msgid "Editor"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:277
msgid "Clicking :guilabel:`Editor` opens a new browser tab to access an online integrated development environment (IDE) to edit the source code. You can also open terminals, Python consoles, and Odoo shell consoles."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches' editor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:284
msgid "You can open multiple tabs and drag and drop them to arrange the layout as you wish."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:287
msgid ":doc:`Online editor documentation <online-editor>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:292
msgid "Monitor"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:294
msgid "The :guilabel:`Monitor` tab displays various performance monitoring metrics of the current build."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:296
msgid "Zoom in with your cursor to adjust the time range or select it manually from the time range selector. It is also possible to change the time zone."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The time range selector in the branches monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:303
msgid "Technical logs always use the :abbr:`UTC (Coordinated Universal Time)`. To analyze these logs together with your monitoring metrics, ensure :abbr:`UTC (Coordinated Universal Time)` is selected in the monitoring tool."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:306
msgid "Similarly, when sending a support ticket, ensure the information you share is based on :abbr:`UTC (Coordinated Universal Time)`, as Odoo uses this time zone to investigate performance issues."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:310
msgid "The information is aggregated periodically. When this is the case, a blue dotted line is displayed, along with the tag :guilabel:`Aggregate Date`. This means that the data before this date will appear flattened when compared to the data after this date. Therefore, when using the monitoring tool, it is recommended to focus on recent events to get the most detailed information possible."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:316
msgid "Dotted Lines of other colors help you relate to other changes on the build (database import, git push, etc.)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "CPU monitoring aggregated data"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:323
msgid "On each graph, an 𝕚 (:guilabel:`information`) icon is displayed in the top-left corner. Hover your mouse over it to get more details about what the graph represents."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:329
msgid "Metrics"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:334
msgid "System"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:336
msgid "The :guilabel:`Memory` graph displays information about memory consumption:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:338
msgid ":guilabel:`Memory container` represents Odoo workers and container processes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:339
msgid ":guilabel:`Memory postgresql` represents the database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The memory graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:344
msgid "The :guilabel:`CPU` graph displays information about CPU consumption:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:346
msgid ":guilabel:`CPU http` represents Odoo workers."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:347
msgid ":guilabel:`CPU cron/mail` represents scheduled actions and incoming emails."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:348
msgid ":guilabel:`CPU postgresql` (database processes)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:349
msgid ":guilabel:`CPU other` represents webshells, the editor, etc."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The cpu graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:354
msgid "The :guilabel:`Storage` graph displays information about the storage used:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:356
msgid ":guilabel:`Container` represents the filestore, log files, and user files."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:357
msgid ":guilabel:`Postgresql` represents the database and indexes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The storage graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:365
msgid "HTTP"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:367
msgid "The :guilabel:`Requests` graph displays information about the number of HTTP requests per second:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:369
msgid ":guilabel:`HTTP successes` represents successful requests."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:370
msgid ":guilabel:`HTTP errors` represents failed requests (check :file:`odoo.log`)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:371
msgid ":guilabel:`HTTP rate limited` represents declined requests, possibly due to lack of workers."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The requests graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:376
msgid "The :guilabel:`Concurrent requests (max)` graph displays the maximum number of concurrent HTTP requests per second."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The concurrent rquests graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:383
msgid "Database workers determine the number of concurrent requests that can be managed simultaneously. It is essential to have enough workers to handle all incoming requests as they arrive. However, having additional workers beyond this does not improve the speed at which requests are processed."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:387
msgid "The :guilabel:`Average Response time` displays the average response time to HTTP requests (in milliseconds)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The average response time graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:398
msgid "The :guilabel:`Incoming` graph displays data about the daily number of incoming emails:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:400
msgid ":guilabel:`Received Emails` represents emails successfuly received."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:401
msgid ":guilabel:`Received Emails bounced` represents emails unsuccessfully received."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The incoming graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:406
msgid "The :guilabel:`Outgoing` graph displays data about the daily number of outgoing emails:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:408
msgid ":guilabel:`Sent Emails` represents emails successfully sent."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:409
msgid ":guilabel:`Sent Emails bounced` represents emails unsuccessfully sent."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The outgoing graph in the monitor tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:417
#: ../../content/administration/odoo_sh/getting_started/settings.rst:68
#: ../../content/administration/odoo_sh/getting_started/settings.rst:98
#: ../../content/administration/odoo_sh/getting_started/settings.rst:143
msgid "Logs"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:419
msgid "The :guilabel:`Logs` tab offers a real-time view of your server's logs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches log tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:424
msgid "Different logs are available:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:426
msgid "`pip.log`: the Python dependencies installation"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:427
msgid "`install.log`: the database installation (for development branches, tests are included)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:428
msgid "`odoosh-import-database.log`: the last imported dump process"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:429
msgid "`odoo.log`: the running server"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:430
msgid "`update.log`: the database updates"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:431
msgid "`pg_slow_queries.log`: psql queries that take an unusual amount of time"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:432
msgid "`sh_webshell.log`: the actions taken in the webshell"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:433
msgid "`sh_editor.log`: the actions taken in the editor"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:434
msgid "`neutralize.log`: the neutralization of the database (only staging)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "Logs scrolling automatically"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:439
msgid "When new lines are added to the logs, they are displayed automatically. If you scroll to the bottom, the browser scrolls automatically each time a new line is added."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:442
msgid "You can pause the logs fetching process by clicking the :icon:`fa-pause` (:guilabel:`pause`) button in the upper right corner. Otherwise, the process stops after five minutes. You can restart it by clicking the :icon:`fa-play` (:guilabel:`play`) button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:449
#: ../../content/administration/odoo_sh/getting_started/settings.rst:118
#: ../../content/administration/odoo_sh/getting_started/settings.rst:163
msgid "Backups"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:451
msgid "The :guilabel:`Backups` tab lists the available backups to download and restore, lets you perform a manual backup and import a database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches backups tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:457
msgid "The production database is automatically backed up daily. Seven daily, four weekly, and three monthly backups are kept. Each backup includes the database dump, the filestore (attachments and binary fields), logs, and sessions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:462
msgid "You can refer to `the estimated scheduling of automatic backups <https://docs.google.com/spreadsheets/d/e/2PACX-1vSJpyyyQ7kr5WSutkrDE3ybgpYySogseN7x2Og6fIbpPYABHe0q8xq0y0xh7P-QSHkX3RTTVqKMIExy/pubhtml?gid=0&single=true>`_ to gain a better understanding of how the system works. This file is updated daily, taking the current day as the departure point."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:466
msgid "Staging and development databases are not automatically backed up. However, you can restore a backup of the production database in your staging branches, for testing purposes, or manually recover data that has been accidentally deleted from the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:470
msgid "The list contains the backups kept on the server of your production database. This server only keeps one month of backups: seven daily and four weekly backups."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:473
msgid "Dedicated backup servers keep the same backups, as well as three additional monthly backups. To restore or download one of these monthly backups, contact `Odoo Support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:477
msgid "When merging 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 an automatic backup (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, a backup is triggered as it may break something."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:483
msgid "If the merged commit does not update the version of a module or linked dependencies, then no backup is triggered by Odoo.sh, as neither the container nor the database is modified; therefore, the platform considers this safe enough. As an extra precaution, you can make a manual backup before modifiyng production sources."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:488
msgid "The purpose of manual backups is to create a specific snapshot of production or staging databases (not available for development). These remain available for seven days. However, there is a limit of five daily manual backups."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:496
msgid "Stage"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:497
msgid "Automatic backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:498
msgid "Manual backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:500
msgid "Yes (up to 3 months)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:501
#: ../../content/administration/odoo_sh/getting_started/branches.rst:504
msgid "Yes (3 days)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:503
#: ../../content/administration/odoo_sh/getting_started/branches.rst:506
#: ../../content/administration/odoo_sh/getting_started/branches.rst:507
msgid "No"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:509
msgid "The :guilabel:`Import Database` feature accepts database archives from:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:511
msgid "the standard Odoo database manager (available for on-premise Odoo servers under `/web/database/manager`)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:513
msgid "the Odoo Online databases manager"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:514
msgid "the Odoo.sh :guilabel:`Backups` tab (using the :icon:`fa-download` (:guilabel:`Download Options`) button)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:516
msgid "the Odoo.sh :doc:`Builds <builds>` view (by clicking :guilabel:`Download DB dump`)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:523
msgid "The :guilabel:`Upgrade` tab can be used to upgrade production and staging branches of valid projects. For more information about the upgrade process, refer to the :doc:`Upgrade documentation <../../upgrade>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches upgrade tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:533
msgid "Tools"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:535
msgid "The :guilabel:`Tools` tab contains the code profiler. It is used to start a profiling session, recording the activities of Odoo workers running in the instance for a maximum of five minutes. You can choose to terminate the session earlier, as running the tool for a shorter duration reduces the amount of noise in the report."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "Using the code profiler"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:543
msgid "After each session, an interactive flame graph is created to help you visualize how the Odoo workers allocate their time."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:547
msgid "Running the profiler consumes a lot of server resources, so avoid letting it run for too long. The goal is to record a specific action in your database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:553
#: ../../content/administration/odoo_sh/getting_started/settings.rst:3
#: ../../content/administration/odoo_sh/getting_started/settings.rst:83
#: ../../content/administration/odoo_sh/getting_started/settings.rst:128
#: ../../content/administration/odoo_sh/getting_started/settings.rst:173
#: ../../content/administration/odoo_sh/getting_started/settings.rst:182
msgid "Settings"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:555
msgid "The :guilabel:`Settings` tab lists the configuration options available for the currently selected branch. The options vary for each stage."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches settings tab"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:564
msgid "Behavior upon new commits"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:566
msgid "You can change the branch's behavior upon receiving a new commit for **development** and **staging** branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:569
msgid "By default, a **development** branch creates a new build and a staging branch updates the previous build. This is useful if the feature you are working on requires a specific configuration, as you would not need to manually configure it again after every commit."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:573
msgid "If you select :guilabel:`New build` for a **staging** branch, a fresh copy of the production build is created every time a commit is pushed."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:576
msgid "A branch that is moved from **staging** to **development** is set automatically to :guilabel:`Do nothing`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:582
msgid "Module installation"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:584
msgid "You can choose which modules should be installed automatically for **development** branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The settings tab module installation"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:589
msgid "To change the default behavior, untick the :guilabel:`Use Default` option under :guilabel:`Development build behavior` and select one of the following options under :guilabel:`Module Installation`:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:593
msgid ":guilabel:`Install only my modules (does not include submodules)`: only installs the branch's modules, excluding :doc:`submodules <../advanced/submodules>`. This is the default option."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:595
msgid ":guilabel:`Full installation (no test suite)`: installs the branch's modules, submodules, and all standard Odoo modules. When running the full installation, the test suite is disabled."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:597
msgid ":guilabel:`Install a list of modules`: installs the specified modules. To do so, enter their technical name, and separate them using commas (e.g., `sale_management,website,accountant`)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:601
msgid "If the test suite is enabled, installing all standard Odoo modules can take up to one hour."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:606
msgid "Test suite"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:608
msgid "By default, the test suite for **development** branches is enabled. You can restrict which tests are run by entering :ref:`test tags <developer/reference/testing/selection>` and separating them using commas (e.g., `custom_tags,at_install,post_install`)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:612
msgid "To disable the test suite entirely, untick :guilabel:`Validate the test suite on new builds`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:617
msgid "Odoo version"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:619
msgid "You can change the version of Odoo for **development** branches, for example, to test upgraded code or develop features while your production database is in the process of being upgraded to a newer version, by selecting another :guilabel:`Version`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:623
msgid "By default, :guilabel:`Latest` is selected as the :guilabel:`Revision`, and the sources of your Odoo server are updated weekly automatically to benefit from the latest bug, security, and performance fixes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:627
msgid "To choose a specific revision instead, select it using the :guilabel:`Revision` field."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:630
msgid "Revisions expire after three months. You will be notified by email when the revision's expiration date approaches. If you have not taken any action when it expires, the :guilabel:`Revision` field is automatically set back to :guilabel:`Latest`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The settings tab revisions"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:640
#: ../../content/administration/odoo_sh/getting_started/settings.rst:241
msgid "Custom domains"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:642
msgid "You can configure additional `<name>.odoo.com` domains or your own custom domains for all branch types."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:645
msgid "To use your own custom domain, it is necessary to:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:647
msgid "Own or purchase the domain name."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:648
msgid "Enter the domain name under :guilabel:`Custom domains` (e.g., `www.mycompany.com`), then click :guilabel:`Add domain`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:650
msgid "Configure the domain name (e.g., `www.mycompany.com`) using your registrar's domain name manager with a **CNAME** record value set to your production database domain name (e.g., `mycompany.odoo.com`)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:655
msgid "Bare domains (e.g., `mycompany.com`) are not accepted. They can only be configured using **A** records, which only accept IP addresses as their value. Therefore, a bare domain could suddenly cease to function, as the IP address of a database can change (e.g., following an upgrade, a hardware failure, a change of database hosting location)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:660
msgid "To have both your bare domain (e.g., `mycompany.com`) and *www* domain (e.g., `www.mycompany.com`) working, it is necessary to redirect the bare domain to the *www* domain. .com. Most domain managers provide a way to configure this redirection, commonly referred to as a web redirection."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:667
msgid "HTTPS/SSL"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:669
msgid "If the redirection is correctly set up, an SSL certificate is automatically generated using `Let's Encrypt <https://letsencrypt.org/about>`_ within the hour, meaning your domain will be accessible through HTTPS."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:676
msgid "SPF and DKIM compliance"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:678
msgid "If the domain of your email addresses uses the :abbr:`SPF (Sender Policy Framework)` or :abbr:`DKIM (DomainKeys Identified Mail)` authentication protocol, it is necessary to authorize Odoo as a sending host in the domain name settings to increase the deliverability of outgoing emails. For more information, refer to the :doc:`Configure DNS records to send emails in Odoo documentation <../../../applications/general/email_communication/email_domain>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:685
msgid "If Odoo is not authorized as a sending host, your outgoing emails may be flagged as spam."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:690
msgid "Shell commands"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:692
msgid "In the top right corner of the view, several shell commands are displayed. The commands can be copied using the clipboard button and then used in a terminal. In addition, some of them can be used directly from Odoo.sh's interface."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:-1
msgid "The branches shell commands shortcuts"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:702
msgid "Clone"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:704
msgid "The clone command is used to create a local copy of your Git repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:707
msgid ":command:`git clone --recurse-submodules --branch development git@github.com:my-organization/my-repository.git`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:709
msgid "`--recurse-submodules` to download the submodules of your repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:710
msgid "`--branch main` to check out to a specific branch of the repository (e.g., `development`)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:713
msgid "The run button is not available as the command is used to create a local copy on your machine."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:718
msgid "Fork"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:720
msgid "The fork command is used to create a new branch based on the current one."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:723
msgid ":command:`git checkout -b main-1 development && git push -u origin development-1`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:725
msgid ":command:`git checkout -b main-1 main` a command to create a new branch (e.g., `development-1`) based on the current branch (e.g., `development`)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:727
msgid ":command:`git push -u origin development-1` a command to upload the new branch (e.g., `development-1`) to the remote repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:733
msgid "Merge"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:735
msgid "The merge command is used to combine changes on one branch into another branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:738
msgid ":command:`git merge staging-1 && git push -u origin staging`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:740
msgid ":command:`git merge staging-1` a command to merge the changes of the current branch into another branch (e.g., `staging-1`)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:742
msgid ":command:`git push -u origin staging` a command to upload the merged changes to the remote repository branch (e.g., `staging`)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:748
msgid "SSH"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:750
msgid "The SSH command is used to connect to a build using SSH."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:752
msgid "To use the SSH command, it is necessary to set up an SSH key first. To do so:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:754
msgid "`Generate a new SSH key <https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent#generating-a-new-ssh-key>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:755
msgid "`Copy the SSH key to your clipboard <https://docs.github.com/en/authentication/connecting-to-github-with-ssh/adding-a-new-ssh-key-to-your-github-account#adding-a-new-ssh-key-to-your-account>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:756
msgid "On Odoo.sh, click your GitHub user in the top-right corner and select :guilabel:`Profile`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:0
msgid "Accessing a user's profile"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:761
msgid "Paste the SSH key under the :guilabel:`Add a key manually` field and click :guilabel:`Add`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:0
msgid "Adding an SSH key manually"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:767
msgid ":command:`ssh 25004381@my-user-my-repository-staging-25004381.dev.odoo.com`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:769
msgid "`25004381` the build ID"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:770
msgid "`my-user-my-repository-staging-25004381.dev.odoo.com` the domain used to connect to the build"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:772
msgid "Provided you have the necessary :ref:`access rights <odoosh-gettingstarted-settings-collaborators>` on the project, you will be granted SSH access to the build."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:776
msgid "Long-running SSH connections are not guaranteed. Idle connections can be disconnected to free up resources."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:782
msgid "Submodule"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:784
msgid "The submodule command is used to add a branch from another repository to your current branch as a submodule."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:788
msgid ":doc:`Submodules documentation <../advanced/submodules>`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:791
msgid ":command:`git submodule add -b master <URL> <PATH> && git commit -a && git push -u origin staging`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:793
msgid ":command:`git submodule add -b master <URL> <PATH>` a command to add a specific branch (e.g., `master`) of a repository (`<URL>`) as a submodule under the specified path (`<PATH>`) in your current branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:796
msgid ":command:`git commit -a` a command to commit all current changes"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:797
msgid ":command:`git push -u origin staging` a command to upload the changes of the current branch (e.g., `staging`) to the remote repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:805
msgid "The delete command is used to delete a branch from your repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:808
msgid "Once you delete a branch, there is no way to retrieve it unless a backup exists. Staging branches are not automatically backed up, but can be manually. Development branches cannot be backed up."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:812
msgid ":command:`git push origin :staging && git branch -D staging`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:814
msgid ":command:`git push origin :staging` a command to delete a specific branch (e.g., `staging`) on the remote repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:816
msgid ":command:`git branch -D staging` a command to delete the specific branch on your local copy of the repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:820
msgid "Before deleting a branch, refer to the :ref:`Backups section <odoo-sh/branches/tabs/backups>` to better understand how they work and when you should create a manual backup."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:3
msgid "Builds"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:5
msgid "In Odoo.sh, a build is a database loaded by an Odoo server (`odoo/odoo <https://github.com/odoo/odoo>`_ and `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 proper behavior of the server, the database, and the features associated with that revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:-1
msgid "Overiew of the builds"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:19
msgid "In the :guilabel:`Builds` overview, a row represents a branch, and a cell within that row represents a build of that branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:22
msgid "Most builds are created after pushes to your GitHub repository branches. They can also be created through other operations, such as importing a database on Odoo.sh or requesting a rebuild for a branch in your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:26
msgid "Builds can have three possible statuses:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:28
msgid "A build is considered **successful** if no errors or warnings occur during its creation. Successful builds are highlighted in **green**."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:30
msgid "A build is considered **almost successful** if warnings occur, but there are no errors. Almost successful builds are highlighted in **yellow**."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:32
msgid "A build is considered **failed** if errors occur during its creation. Failed builds are highlighted in **red**."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:36
msgid "Builds do not always create a database from scratch. For instance, when pushing a change on the production branch, the created build starts the server with your new revision and tries to load the current production database on it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:50
msgid "The first build of a production branch creates a database from scratch. If this build is successful, this database will become the production database of your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:53
msgid "From then on, pushes to the production branch will create new builds that attempt to load the database using a server running the new revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:56
msgid "If the build is successful or almost successful, the production database will run with this build and its associated revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:59
msgid "If the build fails to load or update the database, the previous successful build is reused to load the database. In that case, the database continues to run using the previous successful revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:63
msgid "The build used to run the production database is always the first in the builds list. If a build fails, it is placed after the build currently running the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:71
msgid "Staging builds duplicate the production database and attempt to load this copy using the revisions of the staging branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:74
msgid "Each time you push a new revision to a staging branch, the resulting build uses a fresh copy of the production database. Databases are not reused between builds of the same branch. This ensures that:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:77
msgid "Staging builds use databases that closely match the current production state, so your tests are not performed on outdated data."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:79
msgid "You can freely experiment within a staging database. When you want to start over with a new copy of the production database, you can request a rebuild."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:82
msgid "However, this also means that if you make configuration changes in a staging database and do not apply them in production, those changes will not be present in the next build of the same staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:91
msgid "Development builds create new databases, load the demo data, and run the unit tests."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:93
msgid "A build will be considered failed if tests fail during installation, as they are designed to raise errors when something is wrong."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:96
msgid "If all tests pass and no errors occur, the build is considered successful."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:99
msgid "Depending on the list of modules to install and test, a development build can take up to one hour to be ready. This is due to the large number of tests included in the default Odoo module suite."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:105
msgid "Features"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:107
msgid "The production branch always appears first. Other branches are ordered by the time of their last created build. The stage highlighted in purple corresponds to the stage selected in the :guilabel:`Branches` menu."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:112
msgid "You can filter branches using the search bar."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:-1
msgid "The branches menu"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:117
msgid "For each branch, you can:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:119
msgid "Access the latest build's database by clicking :guilabel:`Connect`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:120
msgid "Jump to the branch's code by clicking :guilabel:`Github`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:121
msgid "Create a new build by clicking :guilabel:`Rebuild`. It uses the latest revision of the branch (it is not available if a build is already in progress for that branch)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:124
msgid "For each build, you can:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:126
msgid "View the revision changes by clicking the :icon:`fa-github` (:guilabel:`GitHub`) icon."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:127
msgid "Access the build's database as the administrator by clicking :guilabel:`Connect` or as another user by clicking the :icon:`fa-caret-down` (:guilabel:`More Actions`) button next to :guilabel:`Connect` and selecting :guilabel:`Connect as`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:130
msgid "Access the same tools as in the branches view by clicking the :icon:`fa-caret-down` (:guilabel:`More Actions`) button next to :guilabel:`Connect` and selecting :guilabel:`Logs`, :guilabel:`Web Shell`, :guilabel:`Editor`, :guilabel:`Outgoing e-mails` (for the staging and development stages), :guilabel:`Monitoring`, and :guilabel:`Download DB dump` (for the production and staging stages)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:-1
msgid "A build's options"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:3
msgid "Create a project"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:6
msgid "Deploy a platform"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:8
msgid "Visit `Odoo.sh <https://www.odoo.sh>`_ and click :guilabel:`Deploy your platform`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "The Deploy your platform button on Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:13
msgid "Sign in with a `GitHub <https://github.com>`_ account."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "Signing in to GitHub"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:18
msgid "Authorize Odoo.sh by clicking :guilabel:`Authorize odoo` twice."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "Granting Odoo.sh permissions to perform actions and access data on GitHub"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "Granting Odoo.sh additional permissions to perform actions and access data on GitHub"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:27
msgid "Odoo.sh requests GitHub to:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:29
msgid "Access your GitHub login and email."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:30
msgid "Create a new repository, in case you start from scratch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:31
msgid "Access existing repositories, including organization ones, in case you start from an existing repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:33
msgid "Create a webhook to notify you each time changes are pushed."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:34
msgid "Commit changes for easier deployment."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:36
msgid "Fill in the :guilabel:`Deploy your platform` form and click :guilabel:`Deploy`:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:38
msgid ":guilabel:`Github repository`: to create a new repository, choose :guilabel:`New repository` and enter a name; to use an existing one, choose :guilabel:`Existing repository` and select it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:40
msgid ":guilabel:`Odoo Version`: select the major version of Odoo you want to use."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:43
msgid "Use the latest major version of Odoo version when creating a new repository. If you are planning to import an existing database or applications, it might be required that their versions match."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:46
msgid "If you are starting on Odoo Online and plan to migrate to Odoo.sh later, create your database using `odoo.com/start-lts <https://www.odoo.com/start-lts>`_ to ensure compatibility, as minor versions are not supported by Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:50
msgid ":guilabel:`Subscription Code`: enter your Odoo Enterprise subscription code that includes Odoo.sh. It is also sometimes called the *subscription referral*, *contract number*, or *activation code*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:55
msgid "Partners can use their partnership codes to initiate a trial (trial builds are limited to 1 GB storage and two staging). If a client proceeds to start a project, they must subscribe to an Odoo Enterprise plan that includes Odoo.sh hosting and use their subscription code."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:59
msgid ":guilabel:`Hosting location`: select the region where your platform will be hosted."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "The Deploy your platform form"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:67
msgid "Import a database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:69
msgid "Once your platform is deployed, you can import a database into your Odoo.sh project, provided it uses a :doc:`supported version <../../supported_versions>` of Odoo."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:73
msgid "Due to `Odoo's backup policy <https://www.odoo.com/cloud-sla>`_, the import process requires **four times** the size of your database dump in available storage. For example, a 10 GB dump file will require at least 40 GB of available space. We recommend allocating **more than four times×** the dump size temporarily, then reducing storage after the import is complete."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:78
msgid "If your project is a trial created with a partnership code, you can only import database dumps up to **1 GB** in size."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:82
msgid "Push modules in production"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:84
msgid "If you are using community or custom modules, add them to a branch in your GitHub repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:87
msgid "Databases hosted on Odoo Online do not support custom modules."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:89
msgid "Odoo.sh automatically detects folders containing Odoo modules. You can organize them however you prefer. For example, you can place them directly in the root directory of your repository or group them by category (e.g., `accounting`, `project`, etc.)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:93
msgid "For publicly available community modules, you may also consider using :doc:`submodules <../advanced/submodules>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:101
#: ../../content/administration/on_premise.rst:5
#: ../../content/administration/upgrade.rst:30
#: ../../content/administration/upgrade.rst:156
#: ../../content/administration/upgrade.rst:364
msgid "On-premise"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:103
msgid "Go to `/web/database/manager` on your on-premise Odoo instance and click :icon:`fa-floppy-o` :guilabel:`Backup`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "The on-premise web manager interface"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:109
msgid "Select :guilabel:`zip (includes filestore)` as the :guilabel:`Backup Format`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "Downloading an on-premise database backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:115
msgid "You will need the :guilabel:`Master Password` of your Odoo server. If you do not have it, contact your system administrator."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:117
msgid "If you cannot access the database manager, it may have been disabled by your system administrator. Refer to the :ref:`database manager security documentation <db_manager_security>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:123
msgid "Log in to your portal account and navigate to the `My Databases page <https://www.odoo.com/my/databases>`_, and download a backup by clicking the :icon:`fa-gear` (:guilabel:`gear`) icon, then :icon:`fa-cloud-download` :guilabel:`Download`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:0
msgid "Downloading an Odoo Online database backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:131
msgid "Only major versions of Odoo are compatible with Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:134
msgid "Upload the backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:136
msgid "In your Odoo.sh project, navigate to the :guilabel:`Backups` tab of your :guilabel:`Production` branch, and click :guilabel:`Import Database` to upload the backup you previously downloaded."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:-1
msgid "Importing a database backup on Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:142
msgid "Once the import is complete, you can access the database using the :guilabel:`Connect` button in the branch's :guilabel:`History` tab."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:146
msgid "Importing a backup **overwrites all data** currently in the branch. Consider downloading a manual backup beforehand if you want to preserve the existing data."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:150
msgid "Check outgoing email servers"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:152
msgid "Odoo.sh provides a default email server. To use it, ensure that **no outgoing mail server is enabled** in your database by enabling :ref:`developer mode <developer-mode>` and navigating to :menuselection:`Settings --> Technical --> Email: Outgoing Mail Servers`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:156
msgid "After importing your database, all configured outgoing mail servers are **disabled**, and the default Odoo.sh server is used."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:160
msgid "Port **25** is and will remain closed. If connecting to an external SMTP server, use port **465** or **587**."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:164
msgid "Check scheduled actions"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:166
msgid "Scheduled actions are **disabled by default** after importing your database. This prevents your newly imported database from performing potentially disruptive operations such as:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:169
msgid "sending queued emails,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:170
msgid "triggering mass mailings, or"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:171
msgid "syncing with third-party services (e.g., calendars, cloud storage)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:173
msgid "If you intend to use this imported database in production, **re-enable** only the scheduled actions you need by enabling :ref:`developer mode <developer-mode>` and going to :menuselection:`Settings --> Technical --> Automation: Scheduled Actions`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:178
msgid "Register the subscription"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:180
msgid "After import, the database is considered a **duplicate** and will be unlinked from your enterprise subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:184
msgid "You are allowed only one active database per subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:186
msgid "If you intend to make the imported database your production environment:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:188
msgid "Unlink your previous database from the subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:189
msgid "Register the new one."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:191
msgid "Refer to the :doc:`database registration documentation <../../on_premise>` for step-by-step instructions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6
msgid "Online Editor"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11
msgid "The online editor allows you to edit the source code of your builds from a web browser. It also gives you the possibility to open terminals, Python consoles, Odoo Shell consoles and `Notebooks <https://jupyterlab.readthedocs.io/en/stable/user/notebook.html>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18
msgid "You can access the editor of a build through :ref:`the branches tabs <odoo-sh/branches/tabs>`, :ref:`the builds dropdown menu <odoo-sh/builds/stages/features>` or by adding */odoo-sh/editor* to your build domain name (e.g. *https://odoo-addons-master-1.dev.odoo.com/odoo-sh/editor*)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25
msgid "Edit the source code"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27
msgid "The working directory is composed of the following folders:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49
msgid "You can edit the source code (files under */src*) in development and staging builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52
msgid "Your changes won't be propagated to a new build, you must commit them in your source code if you want to make them persist."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56
msgid "For production builds, the source code is read-only, because applying local changes on a production server is not a good practice."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59
msgid "The source code of your Github repository is located under */src/user*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60
msgid "The source code of Odoo is located under"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62
msgid "*/src/odoo* (`odoo/odoo <https://github.com/odoo/odoo>`_),"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63
msgid "*/src/enterprise* (`odoo/enterprise <https://github.com/odoo/enterprise>`_),"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64
msgid "*/src/themes* (`odoo/design-themes <https://github.com/odoo/design-themes>`_)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66
msgid "To open a file in the editor, just double-click on it in the file browser panel on the left."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71
msgid "You can then begin to make your changes. You can save your changes with the menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` shortcut."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77
msgid "If you save a Python file which is under your Odoo server addons path, Odoo will detect it and reload automatically so your changes are reflected immediately, without having to restart the server manually."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84
msgid "However, if the change is a data stored in database, such as the label of a field, or a view, you have to update the according module to apply the change. You can update the module of the currently opened file by using the menu :menuselection:`Odoo --> Update current module`. Note that the file considered as currently opened is the file focused in the text editor, not the file highlighted in the file browser."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93
msgid "You can also open a terminal and execute the command:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102
msgid "Commit & Push your changes"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104
msgid "You have the possibility to commit and push your changes to your Github repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106
msgid "Open a terminal (:menuselection:`File --> New --> Terminal`),"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107
msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108
msgid "Stage your changes using :code:`git add`,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109
msgid "Commit your changes using :code:`git commit`,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110
msgid "Push your changes using :code:`git push https HEAD:<branch>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112
msgid "In this last command,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114
msgid "*https* is the name of your *HTTPS* Github remote repository (e.g. https://github.com/username/repository.git),"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116
msgid "HEAD is the reference to the latest revision you committed,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117
msgid "<branch> must be replaced by the name of the branch to which you want to push the changes, most-likely the current branch if you work in a development build."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124
msgid "The SSH Github remote is not used because your SSH private key is not hosted in your build containers (for obvious security concerns) nor forwarded through an SSH Agent (as you access this editor through a web browser) and you therefore cannot authenticate yourself to Github using SSH. You have to use the HTTPS remote of your Github repository to push your changes, which is added automatically named as *https* in your Git remotes. You will be prompted to enter your Github username and password. If you activated the two-factor authentication on Github, you can create a `personal access token <https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/>`_ and use it as password. Granting the ``repo`` permission suffices."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137
msgid "The Git source folder *~/src/user* is not checked out on a branch but rather on a detached revision: This is because builds work on specific revisions rather than branches. In other words, this means you can have multiple builds on the same branch, but on different revisions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141
msgid "Once your changes are pushed, according to your :ref:`branch push behavior <odoo-sh/branches/tabs/settings>`, a new build may be created. You can continue to work in the editor you pushed from, as it will have the same revision as the new build that was created, but always make sure to be in an editor of a build using the latest revision of your branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148
msgid "Consoles"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150
msgid "You can open Python consoles, which are `IPython interactive shells <https://ipython.readthedocs.io/en/stable/interactive/tutorial.html>`_. One of the most interesting addition to use a Python console rather than a IPython shell within a terminal is the `rich display <https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-display>`_ capabilities. Thanks to this, you will be able to display objects in HTML."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158
msgid "You can for instance display cells of a CSV file using `pandas <https://pandas.pydata.org/pandas-docs/stable/tutorials.html>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164
msgid "You can also open an Odoo Shell console to play around with the Odoo registry and model methods of your database. You can also directly read or write on your records."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169
msgid "In an Odoo Console, transactions are automatically committed. This means, for instance, that changes in records are applied effectively in the database. If you change the name of a user, the name of the user is changed in your database as well. You therefore should use Odoo consoles carefully on production databases."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174
msgid "You can use *env* to invoke models of your database registry, e.g. :code:`env['res.users']`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184
msgid "The class :code:`Pretty` gives you the possibility to easily display lists and dicts in a pretty way, using the `rich display <https://ipython.readthedocs.io/en/stable/config/integrating.html#rich-display>`_ mentioned above."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192
msgid "You can also use `pandas <https://pandas.pydata.org/pandas-docs/stable/tutorials.html>`_ to display graphs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:8
msgid "The settings allow you to manage the configuration of your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:14
msgid "Project name"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:16
msgid "The name of your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:21
msgid "This defines the address that will be used to access your production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:23
msgid "Addresses of your staging and development builds are derived from this name and assigned automatically. However, when you change your project name, only future builds will use the new name."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:29
msgid "Collaborators"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:31
msgid "Manage the Github users who can access your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:36
msgid "There are three levels of users:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:38
msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:40
msgid ":guilabel:`Tester`: has access to the *Staging* and *Development* databases and their tooling. This role is for users conducting User Acceptance Tests. Testers can work with copies of production data but cannot access the production database through the Odoo.sh tooling."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:44
msgid ":guilabel:`Developer`: has access only to the *Development* databases and their tooling. This role is for developers who propose code modifications but are not allowed to access production and staging databases through the Odoo.sh tooling."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:54
msgid "Developer"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:55
msgid "Tester"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:56
msgid "Admin"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:59
#: ../../content/administration/odoo_sh/getting_started/settings.rst:60
#: ../../content/administration/odoo_sh/getting_started/settings.rst:61
#: ../../content/administration/odoo_sh/getting_started/settings.rst:64
#: ../../content/administration/odoo_sh/getting_started/settings.rst:65
#: ../../content/administration/odoo_sh/getting_started/settings.rst:66
#: ../../content/administration/odoo_sh/getting_started/settings.rst:69
#: ../../content/administration/odoo_sh/getting_started/settings.rst:70
#: ../../content/administration/odoo_sh/getting_started/settings.rst:71
#: ../../content/administration/odoo_sh/getting_started/settings.rst:74
#: ../../content/administration/odoo_sh/getting_started/settings.rst:75
#: ../../content/administration/odoo_sh/getting_started/settings.rst:76
#: ../../content/administration/odoo_sh/getting_started/settings.rst:79
#: ../../content/administration/odoo_sh/getting_started/settings.rst:80
#: ../../content/administration/odoo_sh/getting_started/settings.rst:81
#: ../../content/administration/odoo_sh/getting_started/settings.rst:84
#: ../../content/administration/odoo_sh/getting_started/settings.rst:85
#: ../../content/administration/odoo_sh/getting_started/settings.rst:86
#: ../../content/administration/odoo_sh/getting_started/settings.rst:89
#: ../../content/administration/odoo_sh/getting_started/settings.rst:90
#: ../../content/administration/odoo_sh/getting_started/settings.rst:91
#: ../../content/administration/odoo_sh/getting_started/settings.rst:95
#: ../../content/administration/odoo_sh/getting_started/settings.rst:96
#: ../../content/administration/odoo_sh/getting_started/settings.rst:100
#: ../../content/administration/odoo_sh/getting_started/settings.rst:101
#: ../../content/administration/odoo_sh/getting_started/settings.rst:105
#: ../../content/administration/odoo_sh/getting_started/settings.rst:106
#: ../../content/administration/odoo_sh/getting_started/settings.rst:110
#: ../../content/administration/odoo_sh/getting_started/settings.rst:111
#: ../../content/administration/odoo_sh/getting_started/settings.rst:115
#: ../../content/administration/odoo_sh/getting_started/settings.rst:116
#: ../../content/administration/odoo_sh/getting_started/settings.rst:121
#: ../../content/administration/odoo_sh/getting_started/settings.rst:125
#: ../../content/administration/odoo_sh/getting_started/settings.rst:126
#: ../../content/administration/odoo_sh/getting_started/settings.rst:130
#: ../../content/administration/odoo_sh/getting_started/settings.rst:131
#: ../../content/administration/odoo_sh/getting_started/settings.rst:134
#: ../../content/administration/odoo_sh/getting_started/settings.rst:135
#: ../../content/administration/odoo_sh/getting_started/settings.rst:136
#: ../../content/administration/odoo_sh/getting_started/settings.rst:141
#: ../../content/administration/odoo_sh/getting_started/settings.rst:146
#: ../../content/administration/odoo_sh/getting_started/settings.rst:151
#: ../../content/administration/odoo_sh/getting_started/settings.rst:156
#: ../../content/administration/odoo_sh/getting_started/settings.rst:161
#: ../../content/administration/odoo_sh/getting_started/settings.rst:166
#: ../../content/administration/odoo_sh/getting_started/settings.rst:171
#: ../../content/administration/odoo_sh/getting_started/settings.rst:176
#: ../../content/administration/odoo_sh/getting_started/settings.rst:179
#: ../../content/administration/odoo_sh/getting_started/settings.rst:180
#: ../../content/administration/odoo_sh/getting_started/settings.rst:181
#: ../../content/administration/odoo_sh/getting_started/settings.rst:186
#: ../../content/administration/supported_versions.rst:35
#: ../../content/administration/supported_versions.rst:36
#: ../../content/administration/supported_versions.rst:37
#: ../../content/administration/supported_versions.rst:59
#: ../../content/administration/supported_versions.rst:60
#: ../../content/administration/supported_versions.rst:61
#: ../../content/administration/supported_versions.rst:65
#: ../../content/administration/supported_versions.rst:66
#: ../../content/administration/supported_versions.rst:67
msgid "|green|"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:63
#: ../../content/administration/odoo_sh/getting_started/settings.rst:93
#: ../../content/administration/odoo_sh/getting_started/settings.rst:138
msgid "1-click connect"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:73
#: ../../content/administration/odoo_sh/getting_started/settings.rst:103
#: ../../content/administration/odoo_sh/getting_started/settings.rst:148
msgid "Shell/SSH"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:113
#: ../../content/administration/odoo_sh/getting_started/settings.rst:158
msgid "Monitoring"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:177
#: ../../content/administration/odoo_sh/getting_started/status.rst:3
msgid "Status"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:189
msgid "Those roles only apply to the usage of Odoo.sh. It is important to reflect the user roles attribution within the repository on GitHub. Please refer to the GitHub documentation section on `Managing a branch protection rule <https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/managing-a-branch-protection-rule>`_ for detailed guidance."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:207
msgid "Public Access"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:209
msgid "Allow public access to your development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:214
msgid "If activated, this option exposes the Builds page publicly, allowing visitors to view logs of development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:216
msgid "Production and staging builds are excluded, visitors can only see their status."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:221
msgid "GitHub commit statuses"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:223
msgid "This option enables Odoo.sh to push commit statuses to your GitHub repository when a build is created or updated. It requires a GitHub token with permissions to push commit statuses to the repository. Refer to `GitHub's documentation on personal access tokens <https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens>`_ for instructions to create yours."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:229
msgid "GitHub's **fine-grained personal tokens** have an expiration date and will be disabled if they fail to update the commit status. You can replace the token at any time on Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:232
msgid "The commit statuses pushed to GitHub can have the following contexts:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:234
msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:235
msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:236
msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:237
msgid ":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page will push a test status on the last commit of your repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:243
msgid "To configure additional domains please refer to the corresponding branch's :ref:`settings tab <odoo-sh/branches/tabs/settings>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:251
msgid "Configure the deploy keys for the private repositories you use as submodules in your branches to allow Odoo.sh to download them."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:255
msgid "These settings are required for **private repositories** only. If you are looking on how to set up your submodules, instructions are available in the chapter :ref:`Submodules <odoosh-advanced-submodules>` of this documentation."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:262
msgid "When a repository is private, it is not possible to publicly download its branches and revisions. For that reason, you need to configure a deploy key for Odoo.sh, so the remote Git server allows our platform to download the revisions of this private repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:267
msgid "To configure the deploy key for a private repository, proceed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:269
msgid "in the input, paste the SSH URL of your private sub-repository and click on *Add*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:271
msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:272
msgid "it can be another Git server than Github, such as Bitbucket, Gitlab or even your own self-hosted server"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:275
msgid "copy the public key,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:277
msgid "it should look like *ssh-rsa some...random...characters...here...==*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:279
msgid "in the settings of the private sub-repository, add the public key amongst the deploy keys."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:281
msgid "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:282
msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:283
msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:284
msgid "Self-hosted: append the key to the git user’s authorized_keys file in its .ssh directory"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:287
msgid "Storage Size"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:289
msgid "This section shows the storage size used by your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:294
msgid "Storage size is computed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:296
msgid "the size of the PostgreSQL database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:298
msgid "the size of the disk files available in your container: database filestore, sessions storage directory..."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:301
msgid "In case you want to analyze disk usage, you can run the tool `ncdu <https://dev.yorhel.nl/ncdu/man>`_ in your Web Shell."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:304
msgid "Should your production database size grow to exceed what's provisioned in your subscription, it will automatically be synchronized with it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:308
msgid "Database Workers"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:310
msgid "Additional database workers can be configured here. More workers help increase the load your production database is able to handle. If you add more, it will automatically be synchronized with your subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:318
msgid "Adding more workers will not magically solve all performance issues. It only allows the server to handle more connections at the same time. If some operations are unusually slow, it's most likely a problem with the code, if it's not due to your own customizations you can open a ticket `here <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:324
msgid "Staging Branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:326
msgid "Additional staging branches allow you to develop and test more features at the same time. If you add more, it will automatically be synchronized with your subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:333
msgid "Activation"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:335
msgid "Shows the status of the project's activation. You can change the project's activation code if needed."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/status.rst:8
msgid "The status page shows statistics regarding the servers your project uses. It includes the servers availability."
msgstr ""
#: ../../content/administration/on_premise.rst:8
msgid "Register a database"
msgstr ""
#: ../../content/administration/on_premise.rst:10
msgid "To register your database, enter your subscription code in the banner in the app dashboard. If the registration is successful, the banner will turn green and display the database expiration date."
msgstr ""
#: ../../content/administration/on_premise.rst:14
msgid "The expiration date is also displayed at the bottom of the Settings page."
msgstr ""
#: ../../content/administration/on_premise.rst:19
msgid "Duplicate a database"
msgstr ""
#: ../../content/administration/on_premise.rst:21
msgid "Duplicate a database by accessing the database manager on your server (`<odoo-server>/web/database/manager`). Typically, you want to duplicate your production database into a neutralized testing database. It can be done by checking the neutralize box when prompted, which executes all :file:`neutralize.sql` scripts for every installed module."
msgstr ""
#: ../../content/administration/on_premise.rst:27
msgid "Common error messages and solutions"
msgstr ""
#: ../../content/administration/on_premise.rst:30
msgid "Registration error"
msgstr ""
#: ../../content/administration/on_premise.rst:32
msgid "In case of a registration error, the following message should be displayed."
msgstr ""
#: ../../content/administration/on_premise.rst:-1
msgid "Database registration error message"
msgstr ""
#: ../../content/administration/on_premise.rst:37
msgid "To resolve the issue:"
msgstr ""
#: ../../content/administration/on_premise.rst:39
msgid "Check the **validity of your Odoo Enterprise subscription** by verifying if your subscription details have the tag :guilabel:`In Progress` on your `Odoo Account <https://accounts.odoo.com/my/subscription>`_ or contact your Account Manager."
msgstr ""
#: ../../content/administration/on_premise.rst:43
msgid "Ensure that **no other database is linked** to the subscription code, as only one database can be linked per subscription."
msgstr ""
#: ../../content/administration/on_premise.rst:47
msgid "If a test or a development database is needed, you can :ref:`duplicate a database <on-premise/duplicate>`."
msgstr ""
#: ../../content/administration/on_premise.rst:50
msgid "Verify that **no databases share the same UUID** (Universally Unique Identifier) by opening your `Odoo Contract <https://accounts.odoo.com/my/subscription>`_. If two or more databases share the same UUID, their name will be displayed."
msgstr ""
#: ../../content/administration/on_premise.rst:-1
msgid "Database UUID error message"
msgstr ""
#: ../../content/administration/on_premise.rst:57
msgid "If that is the case, manually change the database(s) UUID or `send a support ticket <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/on_premise.rst:60
msgid "As the update notification must be able to reach Odoo's subscription validation servers, ensure your **network and firewall settings** allow the Odoo server to open outgoing connections towards:"
msgstr ""
#: ../../content/administration/on_premise.rst:64
msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`"
msgstr ""
#: ../../content/administration/on_premise.rst:65
msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`"
msgstr ""
#: ../../content/administration/on_premise.rst:67
msgid "These ports must be kept open even after registering a database, as the update notification runs once a week."
msgstr ""
#: ../../content/administration/on_premise.rst:71
msgid "Too many users error"
msgstr ""
#: ../../content/administration/on_premise.rst:73
msgid "If you have more users in a local database than provisioned in your Odoo Enterprise subscription, the following message should be displayed."
msgstr ""
#: ../../content/administration/on_premise.rst:-1
msgid "Too many users on a database error message"
msgstr ""
#: ../../content/administration/on_premise.rst:79
msgid "When the message appears, you have 30 days to act before the database expires. The countdown is updated every day."
msgstr ""
#: ../../content/administration/on_premise.rst:82
#: ../../content/administration/on_premise.rst:102
msgid "To resolve the issue, either:"
msgstr ""
#: ../../content/administration/on_premise.rst:84
msgid "**Add more users** to your subscription by clicking the :guilabel:`Upgrade your subscription` link displayed in the message to validate the upsell quotation and pay for the extra users."
msgstr ""
#: ../../content/administration/on_premise.rst:86
msgid ":ref:`Deactivate users <users/deactivate>` and **reject** the upsell quotation."
msgstr ""
#: ../../content/administration/on_premise.rst:88
msgid "Once your database has the correct number of users, the expiration message disappears automatically after a few days, when the next verification occurs."
msgstr ""
#: ../../content/administration/on_premise.rst:92
msgid "Database expired error"
msgstr ""
#: ../../content/administration/on_premise.rst:94
msgid "If your database expires before you renew your subscription, the following message should be displayed."
msgstr ""
#: ../../content/administration/on_premise.rst:-1
msgid "Database expired error message"
msgstr ""
#: ../../content/administration/on_premise.rst:100
msgid "This message appears if you fail to act before the end of the 30-day countdown."
msgstr ""
#: ../../content/administration/on_premise.rst:104
msgid "Click the :guilabel:`Renew your subscription` link displayed in the message and complete the process. If you pay by wire transfer, your subscription will be renewed when the payment arrives which can take a few days. Credit card payments are processed immediately."
msgstr ""
#: ../../content/administration/on_premise.rst:107
msgid "`Send a support ticket <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:6
msgid "Switch from Community to Enterprise"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:8
msgid "Depending on your current installation, there are multiple ways to upgrade your community version. In any case the basic guidelines are:"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:12
#: ../../content/administration/on_premise/community_to_enterprise.rst:31
#: ../../content/administration/on_premise/community_to_enterprise.rst:63
#: ../../content/administration/on_premise/community_to_enterprise.rst:80
msgid "Backup your community database"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:17
#: ../../content/administration/on_premise/community_to_enterprise.rst:62
msgid "Shutdown your server"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:19
msgid "Install the web_enterprise module"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:21
msgid "Restart your server"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:23
msgid "Enter your Odoo Enterprise Subscription code"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:29
msgid "On Linux, using an installer"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:33
msgid "Stop the odoo service"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:39
msgid "Install the enterprise .deb (it should install over the community package)"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:45
msgid "Update your database to the enterprise packages using"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:51
msgid "You should be able to connect to your Odoo Enterprise instance using your usual mean of identification. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:57
msgid "On Linux, using the source code"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:59
msgid "There are many ways to launch your server when using sources, and you probably have your own favourite. You may need to adapt sections to your usual workflow."
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:64
msgid "Update the ``--addons-path`` parameter of your launch command (see :doc:`../on_premise/source`)"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:65
msgid "Install the web_enterprise module by using"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:71
msgid "Depending on the size of your database, this may take some time."
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:73
msgid "Restart your server with the updated addons path of point 3. You should be able to connect to your instance. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:78
msgid "On Windows"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:82
msgid "Uninstall Odoo Community (using the Uninstall executable in the installation folder) - PostgreSQL will remain installed"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:88
msgid "Launch the Odoo Enterprise Installer and follow the steps normally. When choosing the installation path, you can set the folder of the Community installation (this folder still contains the PostgreSQL installation). Uncheck ``Start Odoo`` at the end of the installation"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:96
msgid "Using a command window, update your Odoo Database using this command (from the Odoo installation path, in the server subfolder)"
msgstr ""
#: ../../content/administration/on_premise/community_to_enterprise.rst:103
msgid "No need to manually launch the server, the service is running. You should be able to connect to your Odoo Enterprise instance using your usual mean of identification. You can then link your database with your Odoo Enterprise Subscription by entering the code you received by e-mail in the form input"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:3
msgid "System configuration"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:5
msgid "This document describes basic steps to set up Odoo in production or on an internet-facing server. It follows :doc:`installation <../on_premise>`, and is not generally necessary for a development systems that is not exposed on the internet."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:10
msgid "If you are setting up a public server, be sure to check our :ref:`security` recommendations!"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:15
msgid "dbfilter"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:17
msgid "Odoo is a multi-tenant system: a single Odoo system may run and serve a number of database instances. It is also highly customizable, with customizations (starting from the modules being loaded) depending on the \"current database\"."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:21
msgid "This is not an issue when working with the backend (web client) as a logged-in company user: the database can be selected when logging in, and customizations loaded afterwards."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:25
msgid "However it is an issue for non-logged users (portal, website) which aren't bound to a database: Odoo needs to know which database should be used to load the website page or perform the operation. If multi-tenancy is not used that is not an issue, there's only one database to use, but if there are multiple databases accessible Odoo needs a rule to know which one it should use."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:31
msgid "That is one of the purposes of :option:`--db-filter <odoo-bin --db-filter>`: it specifies how the database should be selected based on the hostname (domain) that is being requested. The value is a `regular expression`_, possibly including the dynamically injected hostname (``%h``) or the first subdomain (``%d``) through which the system is being accessed."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:37
msgid "For servers hosting multiple databases in production, especially if ``website`` is used, dbfilter **must** be set, otherwise a number of features will not work correctly."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:42
msgid "Configuration samples"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:44
msgid "Show only databases with names beginning with 'mycompany'"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:46
#: ../../content/administration/on_premise/deploy.rst:58
#: ../../content/administration/on_premise/deploy.rst:153
#: ../../content/administration/on_premise/deploy.rst:280
msgid "in :ref:`the configuration file <reference/cmdline/config_file>` set:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:53
msgid "Show only databases matching the first subdomain after ``www``: for example the database \"mycompany\" will be shown if the incoming request was sent to ``www.mycompany.com`` or ``mycompany.co.uk``, but not for ``www2.mycompany.com`` or ``helpdesk.mycompany.com``."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:67
msgid "Setting a proper :option:`--db-filter <odoo-bin --db-filter>` is an important part of securing your deployment. Once it is correctly working and only matching a single database per hostname, it is strongly recommended to block access to the database manager screens, and to use the ``--no-database-list`` startup parameter to prevent listing your databases, and to block access to the database management screens. See also security_."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:76
#: ../../content/administration/on_premise/source.rst:193
msgid "PostgreSQL"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:78
msgid "By default, PostgreSQL only allows connection over UNIX sockets and loopback connections (from \"localhost\", the same machine the PostgreSQL server is installed on)."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:82
msgid "UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same machine, and is the default when no host is provided, but if you want Odoo and PostgreSQL to execute on different machines [#different-machines]_ it will need to `listen to network interfaces`_ [#remote-socket]_, either:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:87
msgid "Only accept loopback connections and `use an SSH tunnel`_ between the machine on which Odoo runs and the one on which PostgreSQL runs, then configure Odoo to connect to its end of the tunnel"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:90
msgid "Accept connections to the machine on which Odoo is installed, possibly over ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo to connect over the network"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:95
#: ../../content/administration/on_premise/deploy.rst:145
#: ../../content/administration/on_premise/deploy.rst:235
#: ../../content/administration/on_premise/deploy.rst:275
msgid "Configuration sample"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:97
msgid "Allow tcp connection on localhost"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:98
msgid "Allow tcp connection from 192.168.1.x network"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:100
msgid "in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:108
msgid "in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:119
msgid "Configuring Odoo"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:121
msgid "Out of the box, Odoo connects to a local postgres over UNIX socket via port 5432. This can be overridden using :ref:`the database options <reference/cmdline/server/database>` when your Postgres deployment is not local and/or does not use the installation defaults."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:126
msgid "The :doc:`packaged installers <packages>` will automatically create a new user (``odoo``) and set it as the database user."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:129
msgid "The database management screens are protected by the ``admin_passwd`` setting. This setting can only be set using configuration files, and is simply checked before performing database alterations. It should be set to a randomly generated value to ensure third parties can not use this interface."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:134
msgid "All database operations use the :ref:`database options <reference/cmdline/server/database>`, including the database management screen. For the database management screen to work requires that the PostgreSQL user have ``createdb`` right."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:138
msgid "Users can always drop databases they own. For the database management screen to be completely non-functional, the PostgreSQL user needs to be created with ``no-createdb`` and the database must be owned by a different PostgreSQL user."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:142
msgid "the PostgreSQL user *must not* be a superuser"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:147
msgid "connect to a PostgreSQL server on 192.168.1.2"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:148
msgid "port 5432"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:149
msgid "using an 'odoo' user account,"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:150
msgid "with 'pwd' as a password"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:151
msgid "filtering only db with a name beginning with 'mycompany'"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:168
msgid "SSL Between Odoo and PostgreSQL"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:170
msgid "Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL. in Odoo the db_sslmode control the ssl security of the connection with value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or 'verify-full'"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:175
msgid "`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:180
msgid "Builtin server"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:182
msgid "Odoo includes built-in HTTP, cron, and live-chat servers, using either multi-threading or multi-processing."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:185
msgid "The **multi-threaded** server is a simpler server primarily used for development, demonstrations, and its compatibility with various operating systems (including Windows). A new thread is spawned for every new HTTP request, even for long-lived connections such as websocket. Extra daemonic cron threads are spawned too. Due to a Python limitation (GIL), it doesn't make the best use of the hardware."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:191
msgid "The multi-threaded server is the default server, also for docker containers. It is selected by leaving the :option:`--workers <odoo-bin --workers>` option out or setting it to ``0``."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:194
msgid "The **multi-processing** server is a full-blown server primarily used for production. It is not liable to the same Python limitation (GIL) on resource usage and hence makes the best use of the hardware. A pool of workers is created upon server startup. New HTTP requests are queued by the OS until there are workers ready to process them. An extra event-driven HTTP worker for the live chat is spawned on an alternative port. Extra cron workers are spawned too. A configurable process reaper monitors resource usage and can kill/restart failed workers."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:201
msgid "The multi-processing server is opt-in. It is selected by setting the :option:`--workers <odoo-bin --workers>` option to a non-null integer."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:205
msgid "Because it is highly customized for Linux servers, the multi-processing server is not available on Windows."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:209
msgid "Worker number calculation"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:211
msgid "Rule of thumb : (#CPU * 2) + 1"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:212
msgid "Cron workers need CPU"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:213
msgid "1 worker ~= 6 concurrent users"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:216
msgid "memory size calculation"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:218
msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:219
msgid "A heavy worker, when all computed field are well designed, SQL requests are well designed, ... is estimated to consume around 1GB of RAM"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:220
msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:222
msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:225
#: ../../content/administration/on_premise/deploy.rst:413
msgid "LiveChat"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:227
msgid "In multi-processing, a dedicated LiveChat worker is automatically started and listens on the :option:`--gevent-port <odoo-bin --gevent-port>`. By default, the HTTP requests will keep accessing the normal HTTP workers instead of the LiveChat one. You must deploy a proxy in front of Odoo and redirect incoming requests whose path starts with ``/websocket/`` to the LiveChat worker. You must also start Odoo in :option:`--proxy-mode <odoo-bin --proxy-mode>` so it uses the real client headers (such as hostname, scheme, and IP) instead of the proxy ones."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:237
msgid "Server with 4 CPU, 8 Thread"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:238
msgid "60 concurrent users"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:240
msgid "60 users / 6 = 10 <- theoretical number of worker needed"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:241
msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:242
msgid "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to measure cpu load, and check if it's between 7 and 7.5 ."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:243
msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:245
msgid "in :ref:`the configuration file <reference/cmdline/config_file>`:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:261
msgid "HTTPS"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:263
msgid "Whether it's accessed via website/web client or web service, Odoo transmits authentication information in cleartext. This means a secure deployment of Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via just about any SSL termination proxy, but requires the following setup:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:268
msgid "Enable Odoo's :option:`proxy mode <odoo-bin --proxy-mode>`. This should only be enabled when Odoo is behind a reverse proxy"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:269
msgid "Set up the SSL termination proxy (`Nginx termination example`_)"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:270
msgid "Set up the proxying itself (`Nginx proxying example`_)"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:271
msgid "Your SSL termination proxy should also automatically redirect non-secure connections to the secure port"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:277
msgid "Redirect http requests to https"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:278
msgid "Proxy requests to odoo"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:286
msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:362
msgid "HTTPS Hardening"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:364
msgid "Add the `Strict-Transport-Security` header to all requests, in order to prevent browsers from ever sending a plain HTTP request to this domain. You will need to maintain a working HTTPS service with a valid certificate on this domain at all times, otherwise your users will see security alerts or be entirely unable to access it."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:370
msgid "Force HTTPS connections during a year for every visitor in NGINX with the line:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:376
msgid "Additional configuration can be defined for the `session_id` cookie. The `Secure` flag can be added to ensure it is never transmitted over HTTP and `SameSite=Lax` to prevent authenticated `CSRF`_."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:387
msgid "Odoo as a WSGI Application"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:389
msgid "It is also possible to mount Odoo as a standard WSGI_ application. Odoo provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. That script should be customized (possibly after copying it from the setup directory) to correctly set the configuration directly in :mod:`odoo.tools.config` rather than through the command-line or a configuration file."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:395
msgid "However the WSGI server will only expose the main HTTP endpoint for the web client, website and webservice API. Because Odoo does not control the creation of workers anymore it can not setup cron or livechat workers"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:400
msgid "Cron Workers"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:402
msgid "Starting one of the built-in Odoo servers next to the WSGI server is required to process cron jobs. That server must be configured to only process crons and not HTTP requests using the :option:`--no-http <odoo-bin --no-http>` cli option or the ``http_enable = False`` configuration file setting."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:407
msgid "On Linux-like systems, using the multi-processing server over the multi-threading one is recommended to benefit from better hardware usage and increased stability, i.e., using the :option:`--workers=-1 <odoo-bin --workers>` and :option:`--max-cron-threads=n <odoo-bin --max-cron-threads>` cli options."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:415
msgid "Using a gevent-compatible WSGI server is required for the correct operation of the live chat feature. That server should be able to handle many simultaneous long-lived connections but doesn't need a lot of processing power. All requests whose path starts with ``/websocket/`` should be directed to that server. A regular (thread/process-based) WSGI server should be used for all other requests."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:421
msgid "The Odoo cron server can also be used to serve the live chat requests. Just drop the :option:`--no-http <odoo-bin --no-http>` cli option from the cron server and make sure requests whose path starts with ``/websocket/`` are directed to this server, either on the :option:`--http-port <odoo-bin --http-port>` (multi-threading server) or on the :option:`--gevent-port <odoo-bin --gevent-port>` (multi-processing server)."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:430
msgid "Serving static files and attachments"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:432
msgid "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."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:437
msgid "Serving static files"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:439
msgid "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."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:443
msgid "It is recommended to set the ``Content-Security-Policy: default-src 'none'`` header on all images delivered by the web server. It is not strictly necessary as users cannot modify/inject content inside of modules' :file:`static/` folder and existing images are final (they do not fetch new resources by themselves). However, it is good practice."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:448
msgid "Using the above NGINX (https) configuration, the following ``map`` and ``location`` blocks should be added to serve static files via NGINX."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:475
msgid "The actual ``root`` and ``try_files`` directives are dependant on your installation, specifically on your :option:`--addons-path <odoo-bin --addons-path>`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:482
msgid "Debian package"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:484
msgid "Say Odoo has been installed via the **debian packages** for Community and Enterprise, and that the :option:`--addons-path <odoo-bin --addons-path>` is ``'/usr/lib/python3/dist-packages/odoo/addons'``."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:488
#: ../../content/administration/on_premise/deploy.rst:502
msgid "The ``root`` and ``try_files`` should be:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:495
msgid "Git sources"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:497
msgid "Say Odoo has been installed via the **sources**, that both the Community and Enterprise git repositories were cloned in :file:`/opt/odoo/community` and :file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-path <odoo-bin --addons-path>` is ``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:510
msgid "Serving attachments"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:512
msgid "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."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:517
msgid "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)."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:527
msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:529
msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:538
msgid "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."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:547
msgid "Security"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:549
msgid "For starters, keep in mind that securing an information system is a continuous process, not a one-shot operation. At any moment, you will only be as secure as the weakest link in your environment."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:553
msgid "So please do not take this section as the ultimate list of measures that will prevent all security problems. It's only intended as a summary of the first important things you should be sure to include in your security action plan. The rest will come from best security practices for your operating system and distribution, best practices in terms of users, passwords, and access control management, etc."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:559
msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:562
msgid "Always set a strong super-admin admin password, and restrict access to the database management pages as soon as the system is set up. See :ref:`db_manager_security`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:565
msgid "Choose unique logins and strong passwords for all administrator accounts on all databases. Do not use 'admin' as the login. Do not use those logins for day-to-day operations, only for controlling/managing the installation. *Never* use any default passwords like admin/admin, even for test/staging databases."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:570
msgid "Do **not** install demo data on internet-facing servers. Databases with demo data contain default logins and passwords that can be used to get into your systems and cause significant trouble, even on staging/dev systems."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:574
msgid "Use appropriate database filters ( :option:`--db-filter <odoo-bin --db-filter>`) to restrict the visibility of your databases according to the hostname. See :ref:`dbfilter`. You may also use :option:`-d <odoo-bin -d>` to provide your own (comma-separated) list of available databases to filter from, instead of letting the system fetch them all from the database backend."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:581
msgid "Once your ``db_name`` and ``dbfilter`` are configured and only match a single database per hostname, you should set ``list_db`` configuration option to ``False``, to prevent listing databases entirely, and to block access to the database management screens (this is also exposed as the :option:`--no-database-list <odoo-bin --no-database-list>` command-line option)"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:587
msgid "Make sure the PostgreSQL user (:option:`--db_user <odoo-bin --db_user>`) is *not* a super-user, and that your databases are owned by a different user. For example they could be owned by the ``postgres`` super-user if you are using a dedicated non-privileged ``db_user``. See also :ref:`setup/deploy/odoo`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:592
msgid "Keep installations updated by regularly installing the latest builds, either via GitHub or by downloading the latest version from https://www.odoo.com/page/download or http://nightly.odoo.com"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:596
msgid "Configure your server in multi-process mode with proper limits matching your typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:599
msgid "Run Odoo behind a web server providing HTTPS termination with a valid SSL certificate, in order to prevent eavesdropping on cleartext communications. SSL certificates are cheap, and many free options exist. Configure the web proxy to limit the size of requests, set appropriate timeouts, and then enable the :option:`proxy mode <odoo-bin --proxy-mode>` option. See also :ref:`https_proxy`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:606
msgid "If you need to allow remote SSH access to your servers, make sure to set a strong password for **all** accounts, not just `root`. It is strongly recommended to entirely disable password-based authentication, and only allow public key authentication. Also consider restricting access via a VPN, allowing only trusted IPs in the firewall, and/or running a brute-force detection system such as `fail2ban` or equivalent."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:612
msgid "Consider installing appropriate rate-limiting on your proxy or firewall, to prevent brute-force attacks and denial of service attacks. See also :ref:`login_brute_force` for specific measures."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:616
msgid "Many network providers provide automatic mitigation for Distributed Denial of Service attacks (DDOS), but this is often an optional service, so you should consult with them."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:620
msgid "Whenever possible, host your public-facing demo/test/staging instances on different machines than the production ones. And apply the same security precautions as for production."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:624
msgid "If your public-facing Odoo server has access to sensitive internal network resources or services (e.g. via a private VLAN), implement appropriate firewall rules to protect those internal resources. This will ensure that the Odoo server cannot be used accidentally (or as a result of malicious user actions) to access or disrupt those internal resources. Typically this can be done by applying an outbound default DENY rule on the firewall, then only explicitly authorizing access to internal resources that the Odoo server needs to access. `Systemd IP traffic access control <http://0pointer.net/blog/ip-accounting-and-access-lists-with-systemd.html>`_ may also be useful to implement per-process network access control."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:635
msgid "If your public-facing Odoo server is behind a Web Application Firewall, a load-balancer, a transparent DDoS protection service (like CloudFlare) or a similar network-level device, you may wish to avoid direct access to the Odoo system. It is generally difficult to keep the endpoint IP addresses of your Odoo servers secret. For example they can appear in web server logs when querying public systems, or in the headers of emails posted from Odoo. In such a situation you may want to configure your firewall so that the endpoints are not accessible publicly except from the specific IP addresses of your WAF, load-balancer or proxy service. Service providers like CloudFlare usually maintain a public list of their IP address ranges for this purpose."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:646
msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:649
msgid "Setup daily backups of your databases and filestore data, and copy them to a remote archiving server that is not accessible from the server itself."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:652
msgid "Deploying Odoo on Linux is strongly recommended over Windows. Should you choose nevertheless to deploy on a Windows platform, a thorough security hardening review of the server should be conducted and is outside of the scope of this guide."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:660
msgid "Blocking Brute Force Attacks"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:662
msgid "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."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:666
msgid "The log entries will have the following form."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:668
msgid "Failed login::"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:672
msgid "Successful login::"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:677
msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:679
msgid "For example, the following fail2ban filter definition should match a failed login::"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:686
msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:688
msgid "Here is what it could look like for blocking the IP for 15 minutes when 10 failed login attempts are detected from the same IP within 1 minute::"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:702
msgid "Database Manager Security"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:704
msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:706
msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:709
msgid "If the management screens must not be accessible at all, you should set ``list_db`` configuration option to ``False``, to block access to all the database selection and management screens."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:715
msgid "It is strongly recommended to disable the Database Manager for any internet-facing system! It is meant as a development/demo tool, to make it easy to quickly create and manage databases. It is not designed for use in production, and may even expose dangerous features to attackers. It is also not designed to handle large databases, and may trigger memory limits."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:721
msgid "On production systems, database management operations should always be performed by the system administrator, including provisioning of new databases and automated backups."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:724
msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``dbfilter`` too) so that the system can determine the target database for each request, otherwise users will be blocked as they won't be allowed to choose the database themselves."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:729
msgid "If the management screens must only be accessible from a selected set of machines, use the proxy server's features to block access to all routes starting with ``/web/database`` except (maybe) ``/web/database/selector`` which displays the database-selection screen."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:733
msgid "If the database-management screen should be left accessible, the ``admin_passwd`` setting must be changed from its ``admin`` default: this password is checked before allowing database-alteration operations."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:737
msgid "It should be stored securely, and should be generated randomly e.g."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:743
msgid "which generates a 32-character pseudorandom printable string."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:746
msgid "Reset the master password"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:748
msgid "There may be instances where the master password is misplaced, or compromised, and needs to be reset. The following process is for system administrators of an Odoo on-premise database detailing how to manually reset and re-encrypt the master password."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:753
msgid ":doc:`../odoo_accounts`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:755
msgid "When creating a new on-premise database, a random master password is generated. Odoo recommends using this password to secure the database. This password is implemented by default, so there is a secure master password for any Odoo on-premise deployment."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:760
msgid "When creating an Odoo on-premise database the installation is accessible to anyone on the internet, until this password is set to secure the database."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:763
msgid "The master password is specified in the Odoo configuration file (`odoo.conf` or `odoorc` (hidden file)). The Odoo master password is needed to modify, create, or delete a database through the graphical user interface (GUI)."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:768
msgid "Locate configuration file"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:770
msgid "First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden file))."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:774
#: ../../content/administration/on_premise/packages.rst:130
#: ../../content/administration/on_premise/source.rst:70
#: ../../content/administration/on_premise/source.rst:133
#: ../../content/administration/on_premise/source.rst:158
#: ../../content/administration/on_premise/source.rst:180
#: ../../content/administration/on_premise/source.rst:211
#: ../../content/administration/on_premise/source.rst:242
#: ../../content/administration/on_premise/source.rst:331
#: ../../content/administration/on_premise/source.rst:400
#: ../../content/administration/on_premise/source.rst:463
msgid "Windows"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:776
msgid "The configuration file is located at: `c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:778
#: ../../content/administration/on_premise/packages.rst:25
#: ../../content/administration/on_premise/source.rst:52
#: ../../content/administration/on_premise/source.rst:129
#: ../../content/administration/on_premise/source.rst:152
#: ../../content/administration/on_premise/source.rst:174
#: ../../content/administration/on_premise/source.rst:202
#: ../../content/administration/on_premise/source.rst:231
#: ../../content/administration/on_premise/source.rst:274
#: ../../content/administration/on_premise/source.rst:391
#: ../../content/administration/on_premise/source.rst:453
msgid "Linux"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:780
msgid "Depending on how Odoo is installed on the Linux machine, the configuration file is located in one of two different places:"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:783
msgid "Package installation: `/etc/odoo.conf`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:784
msgid "Source installation: `~/.odoorc`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:787
msgid "Change old password"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:789
msgid "Once the appropriate file has been opened, proceed to modify the old password in the configuration file to a temporary password."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:794
#: ../../content/administration/on_premise/deploy.rst:842
msgid "Graphical user interface"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:796
msgid "After locating the configuration file, open it using a (:abbr:`GUI (graphical user interface)`). This can be achieved by simply double clicking on the file. Then, the device should have a default :abbr:`GUI (graphical user interface)` to open the file with."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:800
msgid "Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`, for example. This password can be anything, as long as it is saved temporarily. Make sure to modify all characters after the `=`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:805
#: ../../content/administration/on_premise/deploy.rst:824
msgid "The line appears like this: `admin_passwd = $pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:809
#: ../../content/administration/on_premise/deploy.rst:828
msgid "The modified line appears like this: `admin_passwd = newpassword1234`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:811
#: ../../content/administration/on_premise/deploy.rst:851
msgid "Command-line interface"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:813
msgid "Modify the master password line using the following Unix command detailed below."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:815
msgid "Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and edit the configuration file. To modify the configuration file, enter the following command: :command:`sudo nano /etc/odoo.conf`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:819
msgid "After opening the configuration file, modify the master password line `admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This password can be anything, as long as it is saved temporarily. Make sure to modify all characters after the `=`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:831
msgid "It is essential that the password is changed to something else, rather than triggering a new password reset by adding a semicolon `;` at the beginning of the line. This ensures the database is secure throughout the entire password reset process."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:836
msgid "Restart Odoo server"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:838
msgid "After setting the temporary password, a restart of the Odoo server is **required**."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:844
msgid "To restart the Odoo server, first, type `services` into the Windows :guilabel:`Search` bar. Then, select the :guilabel:`Services` application, and scroll down to the :guilabel:`Odoo` service."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:848
msgid "Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or :guilabel:`Restart`. This action manually restarts the Odoo server."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:853
msgid "Restart the Odoo server by typing the command: :command:`sudo service odoo15 restart`"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:856
msgid "Change the number after `odoo` to fit the specific version the server is running on."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:859
msgid "Use web interface to re-encrypt password"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:861
msgid "First, navigate to `/web/database/manager` or `http://server_ip:port/web/database/manager` in a browser."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:865
msgid "Replace `server_ip` with the IP address of the database. Replace `port` with the numbered port the database is accessible from."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:868
msgid "Next, click :guilabel:`Set Master Password`, and type in the previously-selected temporary password into the :guilabel:`Master Password` field. Following this step, type in a :guilabel:`New Master Password`. The :guilabel:`New Master Password` is hashed (or encrypted), once the :guilabel:`Continue` button is clicked."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:873
msgid "At this point, the password has been successfully reset, and a hashed version of the new password now appears in the configuration file."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:877
msgid "For more information on Odoo database security, see this documentation: :ref:`db_manager_security`."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:881
msgid "Supported Browsers"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:883
msgid "Odoo supports the latest version of the following browsers."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:885
msgid "Google Chrome"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:886
msgid "Mozilla Firefox"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:887
msgid "Microsoft Edge"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:888
msgid "Apple Safari"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:891
msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software."
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:894
msgid "technically a tool like socat_ can be used to proxy UNIX sockets across networks, but that is mostly for software which can only be used over UNIX sockets"
msgstr ""
#: ../../content/administration/on_premise/deploy.rst:898
msgid "or be accessible only over an internal packet-switched network, but that requires secured switches, protections against `ARP spoofing`_ and precludes usage of WiFi. Even over secure packet-switched networks, deployment over HTTPS is recommended, and possible costs are lowered as \"self-signed\" certificates are easier to deploy on a controlled environment than over the internet."
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:3
msgid "Email gateway"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:5
msgid "The Odoo mail gateway allows you to inject directly all the received emails in Odoo."
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:7
msgid "Its principle is straightforward: your SMTP server executes the \"mailgate\" script for every new incoming email."
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:10
msgid "The script takes care of connecting to your Odoo database through XML-RPC, and send the emails via the `MailThread.message_process()` feature."
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:14
msgid "Prerequisites"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:16
msgid "Administrator access to the Odoo database."
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:17
msgid "Your own mail server such as Postfix or Exim."
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:18
msgid "Technical knowledge on how to configure an email server."
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:21
msgid "For Postfix"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:23
msgid "In you alias config (:file:`/etc/aliases`):"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:30
#: ../../content/administration/on_premise/email_gateway.rst:44
msgid "Resources"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:32
msgid "`Postfix <http://www.postfix.org/documentation.html>`_"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:33
msgid "`Postfix aliases <http://www.postfix.org/aliases.5.html>`_"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:34
msgid "`Postfix virtual <http://www.postfix.org/virtual.8.html>`_"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:37
msgid "For Exim"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:46
msgid "`Exim <https://www.exim.org/docs.html>`_"
msgstr ""
#: ../../content/administration/on_premise/email_gateway.rst:49
msgid "If you do not have access/manage your email server, use :ref:`incoming mail servers <email-inbound-custom-domain-incoming-server>`."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:3
msgid "Geo IP"
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:6
msgid "This documentation only applies to On-premise databases."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:11
msgid "Download both the GeoLite2 City and Country `databases <https://dev.maxmind.com/geoip/geoip2/geolite2/>`_. You should end up with two files called :file:`GeoLite2-City.mmdb` and :file:`GeoLite2-Country.mmdb`."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:15
msgid "Move the files to the folder :file:`/usr/share/GeoIP/`."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:22
msgid "Restart the server"
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:25
msgid "If you don't want to locate the geoip database in :file:`/usr/share/GeoIP/`, use the :option:`--geoip-city-db <odoo-bin --geoip-city-db>` and :option:`--geoip-country-db <odoo-bin --geoip-country-db>` options of the Odoo command line interface. These options take the absolute path to the GeoIP database file and use it as the GeoIP database. For example:"
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:36
msgid ":doc:`CLI documentation </developer/reference/cli>`."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:39
msgid "Test GeoIP geolocation in your Odoo website"
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:41
msgid "Edit a web page to include some geo-ip information such as the country name of the current request IP address. To do so:"
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:44
msgid "Go to your website. Open the web page that you want to test ``GeoIP``."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:45
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:46
msgid "Add the following piece of XML in the page :"
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:52
msgid "Save and refresh the page."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:54
msgid "Geo-ip is working if you read your country name displayed in bold in the middle of the page."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:56
msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:"
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:58
msgid "The browsing IP address is the localhost (``127.0.0.1``) or a local area network one. If you don't know, you can access your website using mobile data."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:60
msgid "You are using a reverse-proxy (apache, nginx) in front of Odoo but didn't start Odoo with the proxy-mode enabled. See :option:`proxy mode <odoo-bin --proxy-mode>`."
msgstr ""
#: ../../content/administration/on_premise/geo_ip.rst:62
msgid "The GeoIP database is corrupt, missing or unaccessible. In such case a warning was logged in the server logs."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:3
msgid "Packaged installers"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:5
msgid "Odoo provides packaged installers for Debian-based Linux distributions (Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL, etc.), and Windows for the Community and Enterprise editions."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:9
msgid "Official **Community** nightly packages with all relevant dependency requirements are available on the `nightly server <https://nightly.odoo.com>`_."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:13
msgid "Nightly packages may be difficult to keep up to date."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:15
msgid "Official **Community** and **Enterprise** packages can be downloaded from the `Odoo download page <https://www.odoo.com/page/download>`_."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:19
msgid "It is required to be logged in as a paying on-premise customer or partner to download the Enterprise packages."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:28
#: ../../content/administration/on_premise/source.rst:116
msgid "Prepare"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:30
msgid "Odoo needs a `PostgreSQL <https://www.postgresql.org/>`_ server to run properly."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:34
#: ../../content/administration/on_premise/packages.rst:70
#: ../../content/administration/on_premise/source.rst:281
msgid "Debian/Ubuntu"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:36
msgid "The default configuration for the Odoo 'deb' package is to use the PostgreSQL server on the same host as the Odoo instance. Execute the following command to install the PostgreSQL server:"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:44
#: ../../content/administration/on_premise/packages.rst:80
#: ../../content/administration/on_premise/packages.rst:114
msgid "Fedora"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:46
msgid "Make sure that the `sudo` command is available and well configured and, only then, execute the following command to install the PostgreSQL server:"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:57
#: ../../content/administration/on_premise/source.rst:423
msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in `version 0.12.6 <https://github.com/wkhtmltopdf/packaging/releases/tag/0.12.6.1-3>`_ for it to support headers and footers. Check out the `wkhtmltopdf wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the various versions."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:63
msgid "Repository"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:65
msgid "Odoo S.A. provides a repository that can be used to install the **Community** edition by executing the following commands:"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:78
msgid "Use the usual `apt-get upgrade` command to keep the installation up-to-date."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:90
msgid "Currently, there is no nightly repository for the Enterprise edition."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:93
msgid "Distribution package"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:95
msgid "Instead of using the repository, packages for both the **Community** and **Enterprise** editions can be downloaded from the `Odoo download page <https://www.odoo.com/page/download>`_."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:100
msgid "Ubuntu"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:103
msgid "Odoo 19 'deb' package currently supports `Ubuntu Noble (24.04LTS) <https://releases.ubuntu.com/noble>`_."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:106
msgid "Once downloaded, execute the following commands **as root** to install Odoo as a service, create the necessary PostgreSQL user, and automatically start the server:"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:117
msgid "Odoo 19 'rpm' package supports Fedora 42."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:119
msgid "Once downloaded, the package can be installed using the 'dnf' package manager:"
msgstr ""
#: ../../content/administration/on_premise/packages.rst:133
msgid "Windows packaging is offered for the convenience of testing or running single-user local instances but production deployment is discouraged due to a number of limitations and risks associated with deploying Odoo on a Windows platform."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:137
msgid "Download the installer from the `nightly server <https://nightly.odoo.com>`_ (Community only) or the Windows installer from the `Odoo download page <https://www.odoo.com/page/download>`_ (any edition."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:140
msgid "Execute the downloaded file."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:143
msgid "On Windows 8 and later, a warning titled *Windows protected your PC* may be displayed. Click **More Info** and then **Run anyway** to proceed."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:146
msgid "Accept the `UAC <https://en.wikipedia.org/wiki/User_Account_Control>`_ prompt."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:147
msgid "Go through the installation steps."
msgstr ""
#: ../../content/administration/on_premise/packages.rst:149
msgid "Odoo launches automatically at the end of the installation."
msgstr ""
#: ../../content/administration/on_premise/source.rst:3
msgid "Source install"
msgstr ""
#: ../../content/administration/on_premise/source.rst:5
msgid "The source 'installation' is not about installing Odoo but running it directly from the source instead."
msgstr ""
#: ../../content/administration/on_premise/source.rst:8
msgid "Using the Odoo source can be more convenient for module developers as it is more easily accessible than using packaged installers."
msgstr ""
#: ../../content/administration/on_premise/source.rst:11
msgid "It makes starting and stopping Odoo more flexible and explicit than the services set up by the packaged installers. Also, it allows overriding settings using :ref:`command-line parameters <reference/cmdline>` without needing to edit a configuration file."
msgstr ""
#: ../../content/administration/on_premise/source.rst:15
msgid "Finally, it provides greater control over the system's setup and allows to more easily keep (and run) multiple versions of Odoo side-by-side."
msgstr ""
#: ../../content/administration/on_premise/source.rst:19
msgid "Fetch the sources"
msgstr ""
#: ../../content/administration/on_premise/source.rst:21
msgid "There are two ways to obtain the source code of Odoo: as a ZIP **archive** or through **Git**."
msgstr ""
#: ../../content/administration/on_premise/source.rst:24
msgid "Archive"
msgstr ""
#: ../../content/administration/on_premise/source.rst:26
msgid "Community edition:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:28
#: ../../content/administration/on_premise/source.rst:34
msgid "`Odoo download page <https://www.odoo.com/page/download>`_"
msgstr ""
#: ../../content/administration/on_premise/source.rst:29
msgid "`GitHub Community repository <https://github.com/odoo/odoo>`_"
msgstr ""
#: ../../content/administration/on_premise/source.rst:30
msgid "`Nightly server <https://nightly.odoo.com>`_"
msgstr ""
#: ../../content/administration/on_premise/source.rst:32
msgid "Enterprise edition:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:35
msgid "`GitHub Enterprise repository <https://github.com/odoo/enterprise>`_"
msgstr ""
#: ../../content/administration/on_premise/source.rst:40
msgid "Git"
msgstr ""
#: ../../content/administration/on_premise/source.rst:43
msgid "It is required to have `Git <https://git-scm.com/>`_ installed, and it is recommended to have a basic knowledge of Git commands to proceed."
msgstr ""
#: ../../content/administration/on_premise/source.rst:46
msgid "To clone a Git repository, choose between cloning with HTTPS or SSH. In most cases, the best option is HTTPS. However, choose SSH to contribute to Odoo source code or when following the :doc:`Getting Started developer tutorial </developer/tutorials/server_framework_101>`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:56
#: ../../content/administration/on_premise/source.rst:74
#: ../../content/administration/on_premise/source.rst:92
msgid "Clone with HTTPS"
msgstr ""
#: ../../content/administration/on_premise/source.rst:63
#: ../../content/administration/on_premise/source.rst:81
#: ../../content/administration/on_premise/source.rst:99
msgid "Clone with SSH"
msgstr ""
#: ../../content/administration/on_premise/source.rst:88
#: ../../content/administration/on_premise/source.rst:141
#: ../../content/administration/on_premise/source.rst:164
#: ../../content/administration/on_premise/source.rst:186
#: ../../content/administration/on_premise/source.rst:216
#: ../../content/administration/on_premise/source.rst:256
#: ../../content/administration/on_premise/source.rst:354
#: ../../content/administration/on_premise/source.rst:412
#: ../../content/administration/on_premise/source.rst:474
msgid "Mac OS"
msgstr ""
#: ../../content/administration/on_premise/source.rst:107
msgid "**The Enterprise git repository does not contain the full Odoo source code**. It is only a collection of extra add-ons. The main server code is in the Community edition. Running the Enterprise version means running the server from the Community version with the `addons-path` option set to the folder with the Enterprise edition. It is required to clone both the Community and Enterprise repositories to have a working Odoo Enterprise installation."
msgstr ""
#: ../../content/administration/on_premise/source.rst:119
msgid "Python"
msgstr ""
#: ../../content/administration/on_premise/source.rst:121
msgid "Odoo requires **Python 3.10** or later to run."
msgstr ""
#: ../../content/administration/on_premise/source.rst:123
msgid "Minimum requirement updated from Python 3.7 to Python 3.10."
msgstr ""
#: ../../content/administration/on_premise/source.rst:131
msgid "Use a package manager to download and install Python 3 if needed."
msgstr ""
#: ../../content/administration/on_premise/source.rst:135
msgid "`Download the latest version of Python 3 <https://www.python.org/downloads/windows/>`_ and install it."
msgstr ""
#: ../../content/administration/on_premise/source.rst:138
msgid "During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make sure that **pip** is checked."
msgstr ""
#: ../../content/administration/on_premise/source.rst:143
msgid "Use a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_) to download and install Python 3 if needed."
msgstr ""
#: ../../content/administration/on_premise/source.rst:147
msgid "If Python 3 is already installed, make sure that the version is 3.10 or above, as previous versions are not compatible with Odoo."
msgstr ""
#: ../../content/administration/on_premise/source.rst:170
msgid "Verify that `pip <https://pip.pypa.io>`_ is also installed for this version."
msgstr ""
#: ../../content/administration/on_premise/source.rst:195
msgid "Odoo uses PostgreSQL as its database management system."
msgstr ""
#: ../../content/administration/on_premise/source.rst:197
msgid "Minimum requirement updated from PostgreSQL 12 to PostgreSQL 13."
msgstr ""
#: ../../content/administration/on_premise/source.rst:204
msgid "Use a package manager to download and install PostgreSQL (supported versions: 13.0 or above). It can be achieved by executing the following:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:213
msgid "`Download PostgreSQL <https://www.postgresql.org/download/windows>`_ (supported versions: 13.0 or above) and install it."
msgstr ""
#: ../../content/administration/on_premise/source.rst:218
msgid "Use `Postgres.app <https://postgresapp.com>`_ to download and install PostgreSQL (supported version: 13.0 or above)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:222
msgid "To make the command line tools bundled with Postgres.app available, make sure to set up the `$PATH` variable by following the `Postgres.app CLI tools instructions <https://postgresapp.com/documentation/cli-tools.html>`_."
msgstr ""
#: ../../content/administration/on_premise/source.rst:226
msgid "By default, the only user is `postgres`. As Odoo forbids connecting as `postgres`, create a new PostgreSQL user."
msgstr ""
#: ../../content/administration/on_premise/source.rst:239
#: ../../content/administration/on_premise/source.rst:264
msgid "Because the PostgreSQL user has the same name as the Unix login, it is possible to connect to the database without a password."
msgstr ""
#: ../../content/administration/on_premise/source.rst:244
msgid "Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program Files\\\\PostgreSQL\\\\<version>\\\\bin`) to the `PATH`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:246
msgid "Create a postgres user with a password using the pg admin gui:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:248
msgid "Open **pgAdmin**."
msgstr ""
#: ../../content/administration/on_premise/source.rst:249
msgid "Double-click the server to create a connection."
msgstr ""
#: ../../content/administration/on_premise/source.rst:250
msgid "Select :menuselection:`Object --> Create --> Login/Group Role`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:251
msgid "Enter the username in the **Role Name** field (e.g., `odoo`)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:252
msgid "Open the **Definition** tab, enter a password (e.g., `odoo`), and click **Save**."
msgstr ""
#: ../../content/administration/on_premise/source.rst:253
msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to `Yes`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:270
msgid "Dependencies"
msgstr ""
#: ../../content/administration/on_premise/source.rst:276
msgid "Using **distribution packages** is the preferred way of installing dependencies. Alternatively, install the Python dependencies with **pip**."
msgstr ""
#: ../../content/administration/on_premise/source.rst:283
msgid "On Debian/Ubuntu, the following commands should install the required packages:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:290
msgid "The `setup/debinstall.sh` script will parse the `debian/control <https://github.com/odoo/odoo/blob/19.0/debian/control>`_ file and install the found packages."
msgstr ""
#: ../../content/administration/on_premise/source.rst:293
msgid "Install with pip"
msgstr ""
#: ../../content/administration/on_premise/source.rst:296
msgid "Using pip may lead to security issues and broken dependencies; only do this if you know what you are doing."
msgstr ""
#: ../../content/administration/on_premise/source.rst:299
msgid "As some of the Python packages need a compilation step, they require system libraries to be installed."
msgstr ""
#: ../../content/administration/on_premise/source.rst:302
msgid "On Debian/Ubuntu, the following command should install these required libraries:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:308
msgid "Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of the Odoo Community directory."
msgstr ""
#: ../../content/administration/on_premise/source.rst:312
msgid "The Python packages in :file:`requirements.txt` are based on their stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo release. For example, for Odoo 15.0, the `python3-babel` package version is 2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is then chosen in the :file:`requirements.txt`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:319
#: ../../content/administration/on_premise/source.rst:341
#: ../../content/administration/on_premise/source.rst:360
msgid "It can be preferable not to mix Python module packages between different instances of Odoo or with the system. However, it is possible to use `virtualenv <https://pypi.org/project/virtualenv/>`_ to create isolated Python environments."
msgstr ""
#: ../../content/administration/on_premise/source.rst:323
msgid "Navigate to the path of the Odoo Community installation (:file:`CommunityPath`) and run **pip** on the requirements file to install the requirements for the current user."
msgstr ""
#: ../../content/administration/on_premise/source.rst:333
msgid "Before installing the dependencies, download and install the `Build Tools for Visual Studio <https://visualstudio.microsoft.com/downloads/>`_. Select **C++ build tools** in the **Workloads** tab and install them when prompted."
msgstr ""
#: ../../content/administration/on_premise/source.rst:337
#: ../../content/administration/on_premise/source.rst:356
msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo Community directory."
msgstr ""
#: ../../content/administration/on_premise/source.rst:345
msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file in a terminal **with Administrator privileges**:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:364
msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:374
msgid "Non-Python dependencies must be installed with a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:377
msgid "Download and install the **Command Line Tools**:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:383
msgid "Use the package manager to install non-Python dependencies."
msgstr ""
#: ../../content/administration/on_premise/source.rst:386
msgid "For languages using a **right-to-left interface** (such as Arabic or Hebrew), the `rtlcss` package is required."
msgstr ""
#: ../../content/administration/on_premise/source.rst:393
msgid "Download and install **nodejs** and **npm** with a package manager."
msgstr ""
#: ../../content/administration/on_premise/source.rst:394
#: ../../content/administration/on_premise/source.rst:403
#: ../../content/administration/on_premise/source.rst:416
msgid "Install `rtlcss`:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:402
msgid "Download and install `nodejs <https://nodejs.org/en/download>`_."
msgstr ""
#: ../../content/administration/on_premise/source.rst:409
msgid "Edit the system environment's variable `PATH` to add the folder where `rtlcss.cmd` is located (typically: :file:`C:\\\\Users\\\\<user>\\\\AppData\\\\Roaming\\\\npm\\\\`)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:414
msgid "Download and install **nodejs** with a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
msgstr ""
#: ../../content/administration/on_premise/source.rst:431
msgid "Running Odoo"
msgstr ""
#: ../../content/administration/on_premise/source.rst:433
msgid "Once all dependencies are set up, Odoo can be launched by running `odoo-bin`, the command-line interface of the server. It is located at the root of the Odoo Community directory."
msgstr ""
#: ../../content/administration/on_premise/source.rst:436
msgid "To configure the server, either specify :ref:`command-line arguments <reference/cmdline/server>` or a :ref:`configuration file <reference/cmdline/config>`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:440
msgid "For the Enterprise edition, add the path to the `enterprise` add-ons to the `addons-path` argument. Note that it must come before the other paths in `addons-path` for add-ons to be loaded correctly."
msgstr ""
#: ../../content/administration/on_premise/source.rst:444
msgid "Common necessary configurations are:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:446
msgid "PostgreSQL user and password."
msgstr ""
#: ../../content/administration/on_premise/source.rst:447
msgid "Custom addon paths beyond the defaults to load custom modules."
msgstr ""
#: ../../content/administration/on_premise/source.rst:449
msgid "A typical way to run the server would be:"
msgstr ""
#: ../../content/administration/on_premise/source.rst:460
#: ../../content/administration/on_premise/source.rst:481
msgid "Where `CommunityPath` is the path of the Odoo Community installation, and `mydb` is the name of the PostgreSQL database."
msgstr ""
#: ../../content/administration/on_premise/source.rst:470
msgid "Where `CommunityPath` is the path of the Odoo Community installation, `dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, and `mydb` is the name of the PostgreSQL database."
msgstr ""
#: ../../content/administration/on_premise/source.rst:484
msgid "After the server has started (the INFO log `odoo.modules.loading: Modules loaded.` is printed), open http://localhost:8069 in a web browser and log into the Odoo database with the base administrator account: use `admin` as the email and, again, `admin` as the password."
msgstr ""
#: ../../content/administration/on_premise/source.rst:489
msgid "From there, create and manage new :doc:`users <../../applications/general/users>`."
msgstr ""
#: ../../content/administration/on_premise/source.rst:490
msgid "The user account used to log into Odoo's web interface differs from the :option:`--db_user <odoo-bin -r>` CLI argument."
msgstr ""
#: ../../content/administration/on_premise/source.rst:494
msgid ":doc:`The list of CLI arguments for odoo-bin </developer/reference/cli>`"
msgstr ""
#: ../../content/administration/on_premise/update.rst:6
msgid "Bugfix updates"
msgstr ""
#: ../../content/administration/on_premise/update.rst:9
msgid "Introduction"
msgstr ""
#: ../../content/administration/on_premise/update.rst:11
msgid "In order to benefit from the latest improvements, security fixes, bug corrections and performance boosts, you may need to update your Odoo installation from time to time."
msgstr ""
#: ../../content/administration/on_premise/update.rst:14
msgid "This guide only applies when are using Odoo on your own hosting infrastructure. If you are using one of the Odoo Cloud solutions, updates are automatically performed for you."
msgstr ""
#: ../../content/administration/on_premise/update.rst:17
msgid "The terminology surrounding software updates is often confusing, so here are some preliminary definitions:"
msgstr ""
#: ../../content/administration/on_premise/update.rst:25
msgid "Updating (an Odoo installation)"
msgstr ""
#: ../../content/administration/on_premise/update.rst:21
msgid "Refers to the process of obtaining the latest revision of the source code for your current Odoo Edition. For example, updating your Odoo Enterprise 13.0 to the latest revision. This does not directly cause any change to the contents of your Odoo database, and can be undone by reinstalling the previous revision of the source code."
msgstr ""
#: ../../content/administration/on_premise/update.rst:35
msgid "Upgrading (an Odoo database)"
msgstr ""
#: ../../content/administration/on_premise/update.rst:28
msgid "Refers to a complex data processing operation where the structure and contents of your database is permanently altered to make it compatible with a new release of Odoo. This operation is irreversible and typically accomplished via Odoo's `database upgrade service <https://upgrade.odoo.com>`_, when you decide to switch to a newer release of Odoo. Historically, this process has also been known as a \"migration\" because it involves moving data around inside the database, even though the database may end up at the same physical location after the upgrade."
msgstr ""
#: ../../content/administration/on_premise/update.rst:37
msgid "This page describes the typical steps needed to *update* an Odoo installation to the latest version. If you'd like more information about upgrading a database, please visit the `Odoo Upgrade page <https://upgrade.odoo.com>`_ instead."
msgstr ""
#: ../../content/administration/on_premise/update.rst:43
msgid "In a nutshell"
msgstr ""
#: ../../content/administration/on_premise/update.rst:45
msgid "Updating Odoo is accomplished by simply reinstalling the latest version of your Odoo Edition on top of your current installation. This will preserve your data without any alteration, as long as you do not uninstall PostgreSQL (the database engine that comes with Odoo)."
msgstr ""
#: ../../content/administration/on_premise/update.rst:49
msgid "The main reference for updating is logically our :doc:`installation guide <../on_premise>`, which explains the common installation methods."
msgstr ""
#: ../../content/administration/on_premise/update.rst:52
msgid "Updating is also most appropriately accomplished by the person who deployed Odoo initially, because the procedure is very similar."
msgstr ""
#: ../../content/administration/on_premise/update.rst:55
msgid "We always recommend to download a complete new up-to-date Odoo version, rather than manually applying patches, such as the security patches that come with Security Advisories. The patches are mainly provided for installations that are heavily customized, or for technical personnel who prefer to apply minimal changes temporarily while testing a complete update."
msgstr ""
#: ../../content/administration/on_premise/update.rst:64
msgid "Step 1: Download an updated Odoo version"
msgstr ""
#: ../../content/administration/on_premise/update.rst:66
msgid "The central download page is https://www.odoo.com/page/download. If you see a \"Buy\" link for the Odoo Enterprise download, make sure you are logged into Odoo.com with the same login that is linked to your Odoo Enterprise subscription."
msgstr ""
#: ../../content/administration/on_premise/update.rst:70
msgid "Alternatively, you can use the unique download link that was included with your Odoo Enterprise purchase confirmation email."
msgstr ""
#: ../../content/administration/on_premise/update.rst:73
msgid "Downloading an updated version is not necessary if you installed via Github (see below)"
msgstr ""
#: ../../content/administration/on_premise/update.rst:77
msgid "Step 2: Make a backup of your database"
msgstr ""
#: ../../content/administration/on_premise/update.rst:79
msgid "The update procedure is quite safe and should not alter you data. However it's always best to take a full database backup before performing any change on your installation, and to store it somewhere safe, on a different computer."
msgstr ""
#: ../../content/administration/on_premise/update.rst:83
msgid "If you have not disabled the database manager screen (see :ref:`here <security>` why you should), you can use it (link at bottom of your database selection screen) to download a backup of your database(s). If you disabled it, use the same procedure than for your usual backups."
msgstr ""
#: ../../content/administration/on_premise/update.rst:89
msgid "Step 3: Install the updated version"
msgstr ""
#: ../../content/administration/on_premise/update.rst:91
msgid "Choose the method that matches your current installation:"
msgstr ""
#: ../../content/administration/on_premise/update.rst:95
msgid "Packaged Installers"
msgstr ""
#: ../../content/administration/on_premise/update.rst:97
msgid "If you installed Odoo with an installation package downloaded on our website (the recommended method), updating is very simple. All you have to do is download the installation package corresponding to your system (see step #1) and install it on your server. They are updated daily and include the latest security fixes. Usually, you can simply double-click the package to install it on top of the current installation. After installing the package, be sure to restart the Odoo service or reboot your server, and you're all set."
msgstr ""
#: ../../content/administration/on_premise/update.rst:106
msgid "Source Install (Tarball)"
msgstr ""
#: ../../content/administration/on_premise/update.rst:108
msgid "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) After downloading the package, extract it to a temporary location on your server."
msgstr ""
#: ../../content/administration/on_premise/update.rst:113
msgid "You will get a folder labeled with the version of the source code, for example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" and the actual source code folder named \"odoo\" (for Odoo 10 and later) or \"openerp\" for older versions. You can ignore the odoo.egg-info folder. Locate the folder where your current installation is deployed, and replace it with the newer \"odoo\" or \"openerp\" folder that was in the archive you just extracted."
msgstr ""
#: ../../content/administration/on_premise/update.rst:119
msgid "Be sure to match the folder layout, for example the new \"addons\" folder included in the source code should end up exactly at the same path it was before. Next, watch out for any specific configuration files that you may have manually copied or modified in the old folder, and copy them over to the new folder. Finally, restart the Odoo service or reboot the machine, and you are all set."
msgstr ""
#: ../../content/administration/on_premise/update.rst:126
msgid "Source Install (Github)"
msgstr ""
#: ../../content/administration/on_premise/update.rst:128
msgid "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 repository), and run the following commands::"
msgstr ""
#: ../../content/administration/on_premise/update.rst:136
msgid "The last command may encounter source code conflicts if you had edited the Odoo source code locally. The error message will give you the list of files with conflicts, and you will need to resolve the conflicts manually, by editing them and deciding which part of the code to keep."
msgstr ""
#: ../../content/administration/on_premise/update.rst:140
msgid "Alternatively, if you prefer to simply discard the conflicting changes and restore the official version, you can use the following command::"
msgstr ""
#: ../../content/administration/on_premise/update.rst:145
msgid "Finally, restart the Odoo service or reboot the machine, and you should be done."
msgstr ""
#: ../../content/administration/on_premise/update.rst:149
msgid "Docker"
msgstr ""
#: ../../content/administration/on_premise/update.rst:151
msgid "Please refer to our `Docker image documentation <https://hub.docker.com/_/odoo/>`_ for specific update instructions."
msgstr ""
#: ../../content/administration/supported_versions.rst:7
msgid "Supported versions"
msgstr ""
#: ../../content/administration/supported_versions.rst:9
msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo."
msgstr ""
#: ../../content/administration/supported_versions.rst:12
msgid "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."
msgstr ""
#: ../../content/administration/supported_versions.rst:16
msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <upgrade>` them regularly."
msgstr ""
#: ../../content/administration/supported_versions.rst:17
msgid "Online versions are *not* released for Odoo.sh and On-Premise installations."
msgstr ""
#: ../../content/administration/supported_versions.rst:18
msgid "Online versions are listed below as *SaaS*."
msgstr ""
#: ../../content/administration/supported_versions.rst:20
msgid "This matrix shows the support status of every version."
msgstr ""
#: ../../content/administration/supported_versions.rst:22
msgid "**Major releases are in bold type.**"
msgstr ""
#: ../../content/administration/supported_versions.rst:31
msgid "On-Premise"
msgstr ""
#: ../../content/administration/supported_versions.rst:32
msgid "Release date"
msgstr ""
#: ../../content/administration/supported_versions.rst:33
msgid "End of support"
msgstr ""
#: ../../content/administration/supported_versions.rst:34
msgid "**Odoo 19.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:38
#: ../../content/administration/supported_versions.rst:75
msgid "September 2025"
msgstr ""
#: ../../content/administration/supported_versions.rst:39
msgid "September 2028 (planned)"
msgstr ""
#: ../../content/administration/supported_versions.rst:40
msgid "Odoo SaaS 18.4"
msgstr ""
#: ../../content/administration/supported_versions.rst:41
#: ../../content/administration/supported_versions.rst:47
#: ../../content/administration/supported_versions.rst:53
#: ../../content/administration/supported_versions.rst:71
#: ../../content/administration/supported_versions.rst:72
#: ../../content/administration/supported_versions.rst:73
#: ../../content/administration/supported_versions.rst:77
#: ../../content/administration/supported_versions.rst:78
#: ../../content/administration/supported_versions.rst:79
#: ../../content/administration/supported_versions.rst:83
#: ../../content/administration/supported_versions.rst:84
#: ../../content/administration/supported_versions.rst:85
msgid "|red|"
msgstr ""
#: ../../content/administration/supported_versions.rst:42
#: ../../content/administration/supported_versions.rst:43
#: ../../content/administration/supported_versions.rst:48
#: ../../content/administration/supported_versions.rst:49
#: ../../content/administration/supported_versions.rst:54
#: ../../content/administration/supported_versions.rst:55
msgid "N/A"
msgstr ""
#: ../../content/administration/supported_versions.rst:44
msgid "July 2025"
msgstr ""
#: ../../content/administration/supported_versions.rst:46
msgid "Odoo SaaS 18.3"
msgstr ""
#: ../../content/administration/supported_versions.rst:50
msgid "May 2025"
msgstr ""
#: ../../content/administration/supported_versions.rst:52
msgid "Odoo SaaS 18.2"
msgstr ""
#: ../../content/administration/supported_versions.rst:56
msgid "March 2025"
msgstr ""
#: ../../content/administration/supported_versions.rst:58
msgid "**Odoo 18.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:62
#: ../../content/administration/supported_versions.rst:81
msgid "October 2024"
msgstr ""
#: ../../content/administration/supported_versions.rst:63
msgid "September 2027 (planned)"
msgstr ""
#: ../../content/administration/supported_versions.rst:64
msgid "**Odoo 17.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:68
msgid "November 2023"
msgstr ""
#: ../../content/administration/supported_versions.rst:69
msgid "September 2026 (planned)"
msgstr ""
#: ../../content/administration/supported_versions.rst:70
msgid "**Odoo 16.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:74
msgid "October 2022"
msgstr ""
#: ../../content/administration/supported_versions.rst:76
msgid "**Odoo 15.0**"
msgstr ""
#: ../../content/administration/supported_versions.rst:80
msgid "October 2021"
msgstr ""
#: ../../content/administration/supported_versions.rst:82
msgid "Older versions"
msgstr ""
#: ../../content/administration/supported_versions.rst:86
msgid "Before 2021"
msgstr ""
#: ../../content/administration/supported_versions.rst:87
msgid "Before 2024"
msgstr ""
#: ../../content/administration/supported_versions.rst:89
msgid "Legend"
msgstr ""
#: ../../content/administration/supported_versions.rst:91
msgid "|green| Supported version"
msgstr ""
#: ../../content/administration/supported_versions.rst:93
msgid "|red| End-of-support"
msgstr ""
#: ../../content/administration/supported_versions.rst:95
msgid "N/A Never released for this platform"
msgstr ""
#: ../../content/administration/supported_versions.rst:98
msgid "Even though we don't support older versions, you can always `upgrade from any version <https://upgrade.odoo.com/>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:5
msgid "An upgrade involves moving a database from an older version to a newer supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are crucial as each version offers new features, bug fixes, and security patches. Using a :doc:`supported version <supported_versions>` is strongly recommended. Each major version is supported for three years."
msgstr ""
#: ../../content/administration/upgrade.rst:10
msgid "Depending on the hosting type and Odoo version used, a database upgrade can be **mandatory**."
msgstr ""
#: ../../content/administration/upgrade.rst:16
msgid "If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade is mandatory every two years."
msgstr ""
#: ../../content/administration/upgrade.rst:18
msgid "If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade is mandatory a few weeks after the next version is released. Minor versions are usually released every two months."
msgstr ""
#: ../../content/administration/upgrade.rst:24
msgid "After the initial three years of support, you will have another two years to complete the upgrade. You will be notified when an upgrade is required."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "The \"unsupported version\" popup on Odoo.sh."
msgstr ""
#: ../../content/administration/upgrade.rst:32
msgid "You can stay on the same version indefinitely, even if it is not recommended. Note that the smaller the version gap, the easier the upgrade should be."
msgstr ""
#: ../../content/administration/upgrade.rst:37
msgid "You will receive a notification in your database a few weeks before a mandatory upgrade will be automatically carried out. You are in control of the process as long as the deadline is not reached."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "The upgrade message prompt on the top right of the database"
msgstr ""
#: ../../content/administration/upgrade.rst:44
msgid "Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every database that should be upgraded. If the test is successful and lasts less than 20 minutes, you can directly trigger the upgrade from the database. If the test fails, you can test an upgrade using the `database manager <https://www.odoo.com/my/databases>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:49
msgid "When you are invited to upgrade, it is strongly recommended to :ref:`request an upgraded test database <upgrade-request-test>` first and spend time :ref:`testing <upgrade-testing>` it."
msgstr ""
#: ../../content/administration/upgrade.rst:52
msgid "An automatic upgrade to the next version will be triggered if no action is taken before the specified due date."
msgstr ""
#: ../../content/administration/upgrade.rst:55
msgid "An upgrade does not cover:"
msgstr ""
#: ../../content/administration/upgrade.rst:57
msgid "Downgrading to a previous version of Odoo"
msgstr ""
#: ../../content/administration/upgrade.rst:58
msgid ":doc:`Switching editions <on_premise/community_to_enterprise>` (e.g., from Community to Enterprise)"
msgstr ""
#: ../../content/administration/upgrade.rst:60
msgid ":ref:`Changing hosting type <hosting/change-solution>` (e.g., from on-premise to Odoo Online)"
msgstr ""
#: ../../content/administration/upgrade.rst:61
msgid "Migrating from another ERP to Odoo"
msgstr ""
#: ../../content/administration/upgrade.rst:64
msgid "If your database contains custom modules, it cannot be upgraded until a version of your custom modules is available for the target version of Odoo. For customers maintaining their own custom modules, we recommend to parallelize the process by :ref:`requesting an upgraded database <upgrade-request-test>` while also :doc:`upgrading the source code of your custom modules </developer/howtos/upgrade_custom_db>`."
msgstr ""
#: ../../content/administration/upgrade.rst:73
msgid "Upgrading in a nutshell"
msgstr ""
#: ../../content/administration/upgrade.rst:75
msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database <upgrade-request-test>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:77
msgid "If applicable, upgrade the source code of your custom module to be compatible with the new version of Odoo (see :doc:`/developer/howtos/upgrade_custom_db`)."
msgstr ""
#: ../../content/administration/upgrade.rst:79
msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database <upgrade-testing>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:81
msgid "Report any issue encountered during the testing to Odoo by going to the `Support page and selecting \"An issue related to my future upgrade (I am testing an upgrade)\" <https://www.odoo.com/help?stage=migration>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:84
msgid "Once all issues are resolved and you are confident that the upgraded database can be used as your main database without any issues, plan the upgrade of your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:86
msgid "Request the upgrade for the production database, rendering it unavailable for the time it takes to complete the process (see :ref:`upgrading the production database <upgrade-production>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:88
msgid "Report any issue encountered during the upgrade to Odoo by going to the `Support page and selecting \"An issue related to my upgrade (production)\" <https://www.odoo.com/help?stage=post_upgrade>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:95
msgid "Obtaining an upgraded test database"
msgstr ""
#: ../../content/administration/upgrade.rst:97
msgid "The `Upgrade page <https://upgrade.odoo.com>`_ is the main platform for requesting an upgraded database. However, depending on the hosting type, you can upgrade from the command line (on-premise), the Odoo Online `database manager <https://www.odoo.com/my/databases>`_, or your `Odoo.sh project <https://www.odoo.sh/project>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:103
msgid "The Upgrade platform follows the same `Privacy Policy <https://www.odoo.com/privacy>`_ as the other Odoo.com services. Visit the `General Data Protection Regulation page <https://www.odoo.com/gdpr>`_ to learn more about how Odoo handles your data and privacy."
msgstr ""
#: ../../content/administration/upgrade.rst:111
msgid "To upgrade an Odoo Online database:"
msgstr ""
#: ../../content/administration/upgrade.rst:113
msgid "Open the `database manager <https://www.odoo.com/my/databases>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:114
msgid "Select the database and click :icon:`fa-gears` :guilabel:`Manage`."
msgstr ""
#: ../../content/administration/upgrade.rst:115
msgid "Click :guilabel:`Upgrade` in the :guilabel:`Database` section."
msgstr ""
#: ../../content/administration/upgrade.rst:116
msgid "In the popup:"
msgstr ""
#: ../../content/administration/upgrade.rst:118
msgid "Select the **version** of Odoo you want to upgrade to, usually the latest version."
msgstr ""
#: ../../content/administration/upgrade.rst:119
msgid "Enter the :guilabel:`Email to notify`, which will receive a link to the upgraded database."
msgstr ""
#: ../../content/administration/upgrade.rst:121
msgid "Select the :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request."
msgstr ""
#: ../../content/administration/upgrade.rst:123
msgid "Click :guilabel:`Upgrade`."
msgstr ""
#: ../../content/administration/upgrade.rst:125
msgid "In the database manager, the :guilabel:`Connect` button will be replaced by an unclickable :guilabel:`Upgrading...` button until completion. Once the process is successful, an email containing a link to the upgraded test database is sent to the address provided. The test database can also be accessed from the database manager by clicking the :icon:`fa-caret-down` (:guilabel:`caret down`) button before the database name to display the test database, then clicking :guilabel:`Connect`."
msgstr ""
#: ../../content/administration/upgrade.rst:134
msgid "Odoo.sh is integrated with the upgrade platform to simplify the upgrade process."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "Odoo.sh project and tabs"
msgstr ""
#: ../../content/administration/upgrade.rst:139
msgid "The **latest production daily automatic backup** is then sent to the Upgrade platform."
msgstr ""
#: ../../content/administration/upgrade.rst:141
msgid "Once the upgrade platform is done upgrading the backup and uploading it on the branch, it is put in a **special mode**: each time a **commit is pushed** on the branch, a **restore operation** of the upgraded backup and an **update of all the custom modules** occur. This allows you to test your custom modules on a pristine copy of the upgraded database. The log file of the upgrade process can be found in your newly upgraded staging build by going to :file:`~/logs/upgrade.log`."
msgstr ""
#: ../../content/administration/upgrade.rst:149
msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. If there are none, the \"update on commit\" mode is skipped, the upgraded database is built as soon as it is transferred from the upgrade platform, and the upgrade mode is exited."
msgstr ""
#: ../../content/administration/upgrade.rst:154
msgid "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information."
msgstr ""
#: ../../content/administration/upgrade.rst:158
msgid "The standard upgrade process can be initiated by entering the following command line on the machine where the database is hosted:"
msgstr ""
#: ../../content/administration/upgrade.rst:166
msgid "This command has some requirements on the environment it runs in:"
msgstr ""
#: ../../content/administration/upgrade.rst:168
msgid "Some external commands that must be provided by the operating system, normally found in any Linux distribution (including WSL). An error will be displayed if one or several of them are missing."
msgstr ""
#: ../../content/administration/upgrade.rst:171
msgid "The system user that executes the command needs to be configured with access to the database. Please refer to the PostgreSQL documentation of the `client environment <https://www.postgresql.org/docs/current/libpq-envars.html>`_ or the `client password file <https://www.postgresql.org/docs/current/libpq-pgpass.html>`_ for this requirement."
msgstr ""
#: ../../content/administration/upgrade.rst:175
msgid "The script needs to be able to reach one or multiple servers of the upgrade platform both on TCP port 443 and to any random TCP port in the range between 32768 and 60999. This can be in conflict with your restrictive firewall and may need an exception added to the firewall configuration."
msgstr ""
#: ../../content/administration/upgrade.rst:180
msgid "The following command can be used to display the general help and the main commands:"
msgstr ""
#: ../../content/administration/upgrade.rst:186
msgid "An upgraded test database can also be requested via the `Upgrade page <https://upgrade.odoo.com>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:190
msgid "In databases where custom modules are installed, their source code must be up-to-date with the target version of Odoo before the upgrade can be performed. Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information."
msgstr ""
#: ../../content/administration/upgrade.rst:195
msgid "For security reasons, only the person who submitted the upgrade request can download it."
msgstr ""
#: ../../content/administration/upgrade.rst:196
msgid "For storage reasons, the database's copy is submitted without a filestore to the upgrade server. Therefore, the upgraded database does not contain the production filestore."
msgstr ""
#: ../../content/administration/upgrade.rst:198
msgid "Before restoring the upgraded database, its filestore must be merged with the production filestore to be able to perform tests in the same conditions as it would be in the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:201
msgid "The upgraded database contains:"
msgstr ""
#: ../../content/administration/upgrade.rst:203
msgid "A `dump.sql` file containing the upgraded database"
msgstr ""
#: ../../content/administration/upgrade.rst:204
msgid "A `filestore` folder containing files extracted from in-database records into attachments (if there are any) and new standard Odoo files from the targeted Odoo version (e.g., new images, icons, payment provider's logos, etc.). This is the folder that should be merged with the production filestore in order to get the full upgraded filestore."
msgstr ""
#: ../../content/administration/upgrade.rst:211
msgid "You can request multiple test databases if you wish to test an upgrade more than once."
msgstr ""
#: ../../content/administration/upgrade.rst:214
msgid "When an upgrade request is completed, an upgrade report is attached to the successful upgrade email, and it becomes available in the Discuss app for users who are part of the \"Administration / Settings\" group. This report provides important information about the changes introduced by the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:222
msgid "Testing the new version of the database"
msgstr ""
#: ../../content/administration/upgrade.rst:224
msgid "It is essential to test the upgraded test database to ensure that you are not stuck in your day-to-day activities by a change in views, behavior, or an error message once the upgrade goes live."
msgstr ""
#: ../../content/administration/upgrade.rst:229
msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:"
msgstr ""
#: ../../content/administration/upgrade.rst:232
msgid "Scheduled actions are disabled."
msgstr ""
#: ../../content/administration/upgrade.rst:233
msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one."
msgstr ""
#: ../../content/administration/upgrade.rst:234
msgid "Payment providers and delivery carriers are reset to the test environment."
msgstr ""
#: ../../content/administration/upgrade.rst:235
msgid "Bank synchronization is disabled. Should you want to test the synchronization, contact your bank synchronization provider to get sandbox credentials."
msgstr ""
#: ../../content/administration/upgrade.rst:238
msgid "Testing as many of your business flows as possible is strongly recommended to ensure they are working correctly and to get more familiar with the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:241
msgid "Basic test checklist"
msgstr ""
#: ../../content/administration/upgrade.rst:243
msgid "Are there views that are deactivated in your test database but active in your production database?"
msgstr ""
#: ../../content/administration/upgrade.rst:245
msgid "Are your usual views still displayed correctly?"
msgstr ""
#: ../../content/administration/upgrade.rst:246
msgid "Are your reports (invoice, sales order, etc.) correctly generated?"
msgstr ""
#: ../../content/administration/upgrade.rst:247
msgid "Are your website pages working correctly?"
msgstr ""
#: ../../content/administration/upgrade.rst:248
msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:250
msgid "Are there any issues with your mail templates?"
msgstr ""
#: ../../content/administration/upgrade.rst:251
msgid "Are there any issues with saved translations?"
msgstr ""
#: ../../content/administration/upgrade.rst:252
msgid "Are your search filters still present?"
msgstr ""
#: ../../content/administration/upgrade.rst:253
msgid "Can you export your data?"
msgstr ""
#: ../../content/administration/upgrade.rst:257
msgid "Checking a random product in your product catalog and comparing its test and production data to verify everything is the same (product category, selling price, cost price, vendor, accounts, routes, etc.)."
msgstr ""
#: ../../content/administration/upgrade.rst:260
msgid "Buying this product (Purchase app)."
msgstr ""
#: ../../content/administration/upgrade.rst:261
msgid "Confirming the reception of this product (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:262
msgid "Checking if the route to receive this product is the same in your production database (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:264
msgid "Selling this product (Sales app) to a random customer."
msgstr ""
#: ../../content/administration/upgrade.rst:265
msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data."
msgstr ""
#: ../../content/administration/upgrade.rst:267
msgid "Shipping this product (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:268
msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:270
msgid "Validating a customer invoice (Invoicing or Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:271
msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:273
msgid "Checking your reports' results (Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:274
msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:275
msgid "Making an online order (Website apps) from the product selection in your shop until the checkout process and checking if everything behaves as in your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:278
msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo."
msgstr ""
#: ../../content/administration/upgrade.rst:280
msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo by going to the `Support page and selecting \"An issue related to my future upgrade (I am testing an upgrade)\" <https://www.odoo.com/help?stage=migration>`_. In any case, it is essential to report any problem encountered during the testing to fix it before upgrading your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:286
msgid "You might encounter significant differences with standard views, features, fields, and models during testing. Those changes cannot be reverted on a case-by-case basis. However, if a change introduced by a new version breaks a customization, it is the responsibility of the maintainer of your custom module to make it compatible with the new version of Odoo."
msgstr ""
#: ../../content/administration/upgrade.rst:292
msgid "Do not forget to test:"
msgstr ""
#: ../../content/administration/upgrade.rst:294
msgid "Integrations with external software (EDI, APIs, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:295
msgid "Workflows between different apps (online sales with eCommerce, converting a lead all the way to a sales order, delivery of products, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:297
msgid "Data exports"
msgstr ""
#: ../../content/administration/upgrade.rst:298
msgid "Automated actions"
msgstr ""
#: ../../content/administration/upgrade.rst:299
msgid "Server actions in the action menu on form views, as well as by selecting multiple records on list views"
msgstr ""
#: ../../content/administration/upgrade.rst:305
msgid "Upgrading the production database"
msgstr ""
#: ../../content/administration/upgrade.rst:307
msgid "Once the :ref:`tests <upgrade-testing>` are completed and you are confident that the upgraded database can be used as your main database without any issues, it is time to plan the go-live day."
msgstr ""
#: ../../content/administration/upgrade.rst:310
msgid "Your production database will be unavailable during its upgrade. Therefore, we recommend planning the upgrade at a time when the use of the database is minimal."
msgstr ""
#: ../../content/administration/upgrade.rst:313
msgid "As the standard upgrade scripts and your database are constantly evolving, it is also recommended to frequently request another upgraded test database to ensure that the upgrade process is still successful, especially if it takes a long time to finish. **Fully rehearsing the upgrade process the day before upgrading the production database is also recommended.**"
msgstr ""
#: ../../content/administration/upgrade.rst:319
msgid "Going into production without first testing may lead to:"
msgstr ""
#: ../../content/administration/upgrade.rst:321
msgid "Users failing to adjust to the changes and new features"
msgstr ""
#: ../../content/administration/upgrade.rst:322
msgid "Business interruptions (e.g., no longer having the possibility to validate an action)"
msgstr ""
#: ../../content/administration/upgrade.rst:323
msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)"
msgstr ""
#: ../../content/administration/upgrade.rst:325
msgid "The process of upgrading a production database is similar to upgrading a test database, but with a few exceptions."
msgstr ""
#: ../../content/administration/upgrade.rst:332
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade-request-test>`, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`."
msgstr ""
#: ../../content/administration/upgrade.rst:337
msgid "Once the upgrade is requested, the database will be unavailable until the upgrade is finished. Once the process is completed, it is impossible to revert to the previous version."
msgstr ""
#: ../../content/administration/upgrade.rst:343
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade-request-test>` on the :guilabel:`Production` branch."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "View from the upgrade tab"
msgstr ""
#: ../../content/administration/upgrade.rst:349
msgid "The process is **triggered as soon as a new commit is made** on the branch. This allows the upgrade process to be synchronized with the deployment of the custom modules' upgraded source code. If there are no custom modules, the upgrade process is triggered immediately."
msgstr ""
#: ../../content/administration/upgrade.rst:355
msgid "The database is unavailable throughout the process. If anything goes wrong, the platform automatically reverts the upgrade, as it would be for a regular update. In case of success, a backup of the database before the upgrade is created."
msgstr ""
#: ../../content/administration/upgrade.rst:359
msgid "The update of your custom modules must be successful to complete the entire upgrade process. Make sure the status of your staging upgrade is :guilabel:`successful` before trying it in production. More information on how to upgrade your custom modules can be found on :doc:`/developer/howtos/upgrade_custom_db`."
msgstr ""
#: ../../content/administration/upgrade.rst:366
msgid "The command to upgrade a database to production is similar to the one of upgrading a test database except for the argument `test`, which must be replaced by `production`:"
msgstr ""
#: ../../content/administration/upgrade.rst:373
msgid "An upgraded production database can also be requested via the `Upgrade page <https://upgrade.odoo.com>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:376
msgid "Once the database is uploaded, any modification to your production database will **not** be present on your upgraded database. This is why we recommend not using it during the upgrade process."
msgstr ""
#: ../../content/administration/upgrade.rst:381
msgid "When requesting an upgraded database for production purposes, the copy is submitted without a filestore. Therefore, the upgraded database filestore must be merged with the production filestore before deploying the new version."
msgstr ""
#: ../../content/administration/upgrade.rst:385
msgid "In case of an issue with your production database, you can request the assistance of Odoo by going to the `Support page and selecting \"An issue related to my upgrade (production)\" <https://www.odoo.com/help?stage=post_upgrade>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:392
msgid "Service-level agreement (SLA)"
msgstr ""
#: ../../content/administration/upgrade.rst:394
msgid "With Odoo Enterprise, upgrading a database to the most recent version of Odoo is **free**, including any support required to rectify potential discrepancies in the upgraded database."
msgstr ""
#: ../../content/administration/upgrade.rst:397
msgid "Information about the upgrade services included in the Enterprise Licence is available in the :ref:`Odoo Enterprise Subscription Agreement <upgrade>`. However, this section clarifies what upgrade services you can expect."
msgstr ""
#: ../../content/administration/upgrade.rst:404
msgid "Upgrade services covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:406
msgid "Databases hosted on Odoo's cloud platforms (Odoo Online and Odoo.sh) or self-hosted (On-Premise) can benefit from upgrade services at all times for:"
msgstr ""
#: ../../content/administration/upgrade.rst:409
msgid "the upgrade of all **standard applications**;"
msgstr ""
#: ../../content/administration/upgrade.rst:410
msgid "the upgrade of all **customizations created with the Studio app**, as long as Studio is still installed and the respective subscription is still active; and"
msgstr ""
#: ../../content/administration/upgrade.rst:412
msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**."
msgstr ""
#: ../../content/administration/upgrade.rst:415
msgid "Upgrade services are limited to the technical conversion and adaptation of a database (standard modules and data) to make it compatible with the version targeted by the upgrade."
msgstr ""
#: ../../content/administration/upgrade.rst:421
msgid "Upgrade services not covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:423
msgid "The following upgrade-related services are **not** included:"
msgstr ""
#: ../../content/administration/upgrade.rst:425
msgid "the **cleaning** of pre-existing data and configurations while upgrading;"
msgstr ""
#: ../../content/administration/upgrade.rst:426
msgid "the upgrade of **additional modules not covered by a maintenance contract** that are created in-house or by third parties, including Odoo partners; and"
msgstr ""
#: ../../content/administration/upgrade.rst:428
msgid "**training** on using the upgraded version's features and workflows."
msgstr ""
#: ../../content/administration/upgrade.rst:431
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
msgstr ""
#: ../../content/administration/upgrade.rst:432
msgid ":doc:`Supported Odoo versions <supported_versions>`"
msgstr ""
Reference in New Issue View Git Blame Copy Permalink