NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
72ae0f23a0
documentation/locale/sources/administration.pot
Martin Trigaux (mat) f4d1c04ee7 [I18N] *: export 16.0 translations 
closes 

X-original-commit: aecf49d6c8
Signed-off-by: Martin Trigaux (mat) <mat@odoo.com>
2024-01-21 09:07:20 +00:00

6581 lines
325 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 17.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-01-19 15:28+0000\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 "Install and Maintain"
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/maintain/supported_versions>`"
msgstr ""
#: ../../content/administration/install.rst:5
msgid "Install"
msgstr ""
#: ../../content/administration/install.rst:7
msgid "Depending on the intended use case, there are multiple ways to install Odoo - or not install it at all."
msgstr ""
#: ../../content/administration/install.rst:10
msgid ":doc:`Online <install/online>` is the easiest way to use Odoo in production or to try it."
msgstr ""
#: ../../content/administration/install.rst:12
msgid ":doc:`Packaged installers <install/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/install.rst:16
msgid ":doc:`Source install <install/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/install.rst:20
msgid "A `Docker <https://hub.docker.com/_/odoo/>`_ base image is available for development or deployment."
msgstr ""
#: ../../content/administration/install.rst:26
msgid "Editions"
msgstr ""
#: ../../content/administration/install.rst:28
msgid "There are two different editions."
msgstr ""
#: ../../content/administration/install.rst:30
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/install.rst:34
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/install.rst:39
msgid ":doc:`Switch from Community to Enterprise <maintain/enterprise>` at any time (except for the source install)."
msgstr ""
#: ../../content/administration/install/cdn.rst:3
msgid "Set up a content delivery network (CDN)"
msgstr ""
#: ../../content/administration/install/cdn.rst:8
msgid "Deploying with KeyCDN"
msgstr ""
#: ../../content/administration/install/cdn.rst:10
msgid "A :abbr:`CDN (Content Delivery Network)` or *content distribution network*, is a geographically distributed network of servers that provides high speed internet content. The :abbr:`CDN (Content Delivery Network)` provides quick, high-quality content delivery for content-heavy websites."
msgstr ""
#: ../../content/administration/install/cdn.rst:14
msgid "This document will guide you through the setup of a KeyCDN_ account with an Odoo powered website."
msgstr ""
#: ../../content/administration/install/cdn.rst:17
msgid "Create a pull zone in the KeyCDN dashboard"
msgstr ""
#: ../../content/administration/install/cdn.rst:19
msgid "On the KeyCDN dashboard, start by navigating to the :menuselection:`Zones` menu item on the left. On the form, give a value to the :guilabel:`Zone Name`, which will appear as part of the :abbr:`CDN (Content Delivery Network)`'s :abbr:`URL (Uniform Resource Locator)`. Then, set the :guilabel:`Zone Status` to :guilabel:`active` to engage the zone. For the :guilabel:`Zone Type` set the value to :guilabel:`Pull`, and then, finally, under the :guilabel:`Pull Settings`, enter the :guilabel:`Origin URL`— this address should be the full Odoo database :abbr:`URL (Uniform Resource Locator)`."
msgstr ""
#: ../../content/administration/install/cdn.rst:28
msgid "Use ``https://yourdatabase.odoo.com`` and replace the *yourdatabase* subdomain prefix with the actual name of the database. A custom :abbr:`URL (Uniform Resource Locator)` can be used, as well, in place of the Odoo subdomain that was provided to the database."
msgstr ""
#: ../../content/administration/install/cdn.rst:-1
msgid "KeyCDN's Zone configuration page."
msgstr ""
#: ../../content/administration/install/cdn.rst:36
msgid "Under the :guilabel:`General Settings` heading below the zone form, click the :guilabel:`Show all settings` button to expand the zone options. This should be the last option on the page. After expanding the :guilabel:`General Settings` ensure that the :guilabel:`CORS` option is :guilabel:`enabled`."
msgstr ""
#: ../../content/administration/install/cdn.rst:41
msgid "Next, scroll to the bottom of the zone configuration page and :guilabel:`Save` the changes. KeyCDN will indicate that the new zone will be deployed. This can take about 10 minutes."
msgstr ""
#: ../../content/administration/install/cdn.rst:-1
msgid "KeyCDN deploying the new Zone."
msgstr ""
#: ../../content/administration/install/cdn.rst:49
msgid "A new :guilabel:`Zone URL` has been generated for your Zone, in this example it is ``pulltest-xxxxx.kxcdn.com``. This value will differ for each database."
msgstr ""
#: ../../content/administration/install/cdn.rst:52
msgid "Copy this :guilabel:`Zone URL` to a text editor for later, as it will be used in the next steps."
msgstr ""
#: ../../content/administration/install/cdn.rst:55
msgid "Configure the Odoo instance with the new zone"
msgstr ""
#: ../../content/administration/install/cdn.rst:57
msgid "In the Odoo :guilabel:`Website` app, go to the :menuselection:`Settings` and then activate the :guilabel:`Content Delivery Network (CDN)` setting and copy/paste the :guilabel:`Zone URL` value from the earlier step into the :guilabel:`CDN Base URL` field. This field is only visible and configurable when :doc:`Developer Mode <../../applications/general/developer_mode>` is activated."
msgstr ""
#: ../../content/administration/install/cdn.rst:63
msgid "Ensure that there are two *forward slashes* (`//`) before the :guilabel:`CDN Base URL` and one forward slash (`/`) after the :guilabel:`CDN Base URL`."
msgstr ""
#: ../../content/administration/install/cdn.rst:66
msgid ":guilabel:`Save` the settings when complete."
msgstr ""
#: ../../content/administration/install/cdn.rst:-1
msgid "Activate the CDN setting in Odoo."
msgstr ""
#: ../../content/administration/install/cdn.rst:72
msgid "Now the website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions."
msgstr ""
#: ../../content/administration/install/cdn.rst:75
msgid "In the HTML of the Odoo website, the :abbr:`CDN (content delivery network)` integration is evidenced as working properly by checking the :abbr:`URL (Uniform Resource Locators)` of images. The *CDN Base URL* value can be seen by using your web browser's :guilabel:`Inspect` feature on the Odoo website. Look for it's record by searching within the :guilabel:`Network` tab inside of devtools."
msgstr ""
#: ../../content/administration/install/cdn.rst:-1
msgid "The CDN Base URL can be seen using the inspect function on the Odoo website."
msgstr ""
#: ../../content/administration/install/cdn.rst:85
msgid "Prevent security issues by activating cross-origin resource sharing (CORS)"
msgstr ""
#: ../../content/administration/install/cdn.rst:87
msgid "A security restriction in some browsers (such as Mozilla Firefox and Google Chrome) prevents a remotely linked CSS file to fetch relative resources on this same external server."
msgstr ""
#: ../../content/administration/install/cdn.rst:90
msgid "If the :abbr:`CORS (Cross-Origin Resource Sharing)` option isn't enabled in the :guilabel:`CDN Zone`, the more obvious resulting problem on a standard Odoo website will be the lack of *Font Awesome* icons because the font file declared in the *Font Awesome* CSS won't be loaded from the remote server."
msgstr ""
#: ../../content/administration/install/cdn.rst:95
msgid "When these cross-origin resource issues occur, a security error message similar to the output below will appear in the web browser's developer console:"
msgstr ""
#: ../../content/administration/install/cdn.rst:98
msgid "``Font from origin 'http://pulltest-xxxxx.kxcdn.com' has been blocked from loading /shop:1 by Cross-Origin Resource Sharing policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://yourdatabase.odoo.com' is therefore not allowed access.``"
msgstr ""
#: ../../content/administration/install/cdn.rst:-1
msgid "Error message populated in the browser console."
msgstr ""
#: ../../content/administration/install/cdn.rst:106
msgid "Enabling the :abbr:`CORS (Cross-Origin Resource Sharing)` option in the :abbr:`CDN (Content Delivery Network)` settings fixes this issue."
msgstr ""
#: ../../content/administration/install/deploy.rst:3
msgid "System configuration"
msgstr ""
#: ../../content/administration/install/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 <../install>`, and is not generally necessary for a development systems that is not exposed on the internet."
msgstr ""
#: ../../content/administration/install/deploy.rst:10
msgid "If you are setting up a public server, be sure to check our :ref:`security` recommendations!"
msgstr ""
#: ../../content/administration/install/deploy.rst:15
msgid "dbfilter"
msgstr ""
#: ../../content/administration/install/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/install/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/install/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/install/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/install/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/install/deploy.rst:42
msgid "Configuration samples"
msgstr ""
#: ../../content/administration/install/deploy.rst:44
msgid "Show only databases with names beginning with 'mycompany'"
msgstr ""
#: ../../content/administration/install/deploy.rst:46
#: ../../content/administration/install/deploy.rst:58
#: ../../content/administration/install/deploy.rst:153
#: ../../content/administration/install/deploy.rst:280
msgid "in :ref:`the configuration file <reference/cmdline/config_file>` set:"
msgstr ""
#: ../../content/administration/install/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/install/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/install/deploy.rst:76
#: ../../content/administration/install/source.rst:193
msgid "PostgreSQL"
msgstr ""
#: ../../content/administration/install/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/install/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/install/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/install/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/install/deploy.rst:95
#: ../../content/administration/install/deploy.rst:145
#: ../../content/administration/install/deploy.rst:235
#: ../../content/administration/install/deploy.rst:275
msgid "Configuration sample"
msgstr ""
#: ../../content/administration/install/deploy.rst:97
msgid "Allow tcp connection on localhost"
msgstr ""
#: ../../content/administration/install/deploy.rst:98
msgid "Allow tcp connection from 192.168.1.x network"
msgstr ""
#: ../../content/administration/install/deploy.rst:100
msgid "in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/pg_hba.conf`` set:"
msgstr ""
#: ../../content/administration/install/deploy.rst:108
msgid "in ``/etc/postgresql/<YOUR POSTGRESQL VERSION>/main/postgresql.conf`` set:"
msgstr ""
#: ../../content/administration/install/deploy.rst:119
msgid "Configuring Odoo"
msgstr ""
#: ../../content/administration/install/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/install/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/install/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/install/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/install/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/install/deploy.rst:142
msgid "the PostgreSQL user *must not* be a superuser"
msgstr ""
#: ../../content/administration/install/deploy.rst:147
msgid "connect to a PostgreSQL server on 192.168.1.2"
msgstr ""
#: ../../content/administration/install/deploy.rst:148
msgid "port 5432"
msgstr ""
#: ../../content/administration/install/deploy.rst:149
msgid "using an 'odoo' user account,"
msgstr ""
#: ../../content/administration/install/deploy.rst:150
msgid "with 'pwd' as a password"
msgstr ""
#: ../../content/administration/install/deploy.rst:151
msgid "filtering only db with a name beginning with 'mycompany'"
msgstr ""
#: ../../content/administration/install/deploy.rst:168
msgid "SSL Between Odoo and PostgreSQL"
msgstr ""
#: ../../content/administration/install/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/install/deploy.rst:175
msgid "`PostgreSQL Doc <https://www.postgresql.org/docs/12/static/libpq-ssl.html>`_"
msgstr ""
#: ../../content/administration/install/deploy.rst:180
msgid "Builtin server"
msgstr ""
#: ../../content/administration/install/deploy.rst:182
msgid "Odoo includes built-in HTTP, cron, and live-chat servers, using either multi-threading or multi-processing."
msgstr ""
#: ../../content/administration/install/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/install/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/install/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/install/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/install/deploy.rst:205
msgid "Because it is highly customized for Linux servers, the multi-processing server is not available on Windows."
msgstr ""
#: ../../content/administration/install/deploy.rst:209
msgid "Worker number calculation"
msgstr ""
#: ../../content/administration/install/deploy.rst:211
msgid "Rule of thumb : (#CPU * 2) + 1"
msgstr ""
#: ../../content/administration/install/deploy.rst:212
msgid "Cron workers need CPU"
msgstr ""
#: ../../content/administration/install/deploy.rst:213
msgid "1 worker ~= 6 concurrent users"
msgstr ""
#: ../../content/administration/install/deploy.rst:216
msgid "memory size calculation"
msgstr ""
#: ../../content/administration/install/deploy.rst:218
msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones"
msgstr ""
#: ../../content/administration/install/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/install/deploy.rst:220
msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM"
msgstr ""
#: ../../content/administration/install/deploy.rst:222
msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )"
msgstr ""
#: ../../content/administration/install/deploy.rst:225
#: ../../content/administration/install/deploy.rst:412
msgid "LiveChat"
msgstr ""
#: ../../content/administration/install/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/install/deploy.rst:237
msgid "Server with 4 CPU, 8 Thread"
msgstr ""
#: ../../content/administration/install/deploy.rst:238
msgid "60 concurrent users"
msgstr ""
#: ../../content/administration/install/deploy.rst:240
msgid "60 users / 6 = 10 <- theoretical number of worker needed"
msgstr ""
#: ../../content/administration/install/deploy.rst:241
msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker"
msgstr ""
#: ../../content/administration/install/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/install/deploy.rst:243
msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo"
msgstr ""
#: ../../content/administration/install/deploy.rst:245
msgid "in :ref:`the configuration file <reference/cmdline/config_file>`:"
msgstr ""
#: ../../content/administration/install/deploy.rst:261
msgid "HTTPS"
msgstr ""
#: ../../content/administration/install/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/install/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/install/deploy.rst:269
msgid "Set up the SSL termination proxy (`Nginx termination example`_)"
msgstr ""
#: ../../content/administration/install/deploy.rst:270
msgid "Set up the proxying itself (`Nginx proxying example`_)"
msgstr ""
#: ../../content/administration/install/deploy.rst:271
msgid "Your SSL termination proxy should also automatically redirect non-secure connections to the secure port"
msgstr ""
#: ../../content/administration/install/deploy.rst:277
msgid "Redirect http requests to https"
msgstr ""
#: ../../content/administration/install/deploy.rst:278
msgid "Proxy requests to odoo"
msgstr ""
#: ../../content/administration/install/deploy.rst:286
msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:"
msgstr ""
#: ../../content/administration/install/deploy.rst:361
msgid "HTTPS Hardening"
msgstr ""
#: ../../content/administration/install/deploy.rst:363
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/install/deploy.rst:369
msgid "Force HTTPS connections during a year for every visitor in NGINX with the line:"
msgstr ""
#: ../../content/administration/install/deploy.rst:375
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/install/deploy.rst:386
msgid "Odoo as a WSGI Application"
msgstr ""
#: ../../content/administration/install/deploy.rst:388
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/install/deploy.rst:394
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/install/deploy.rst:399
msgid "Cron Workers"
msgstr ""
#: ../../content/administration/install/deploy.rst:401
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/install/deploy.rst:406
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/install/deploy.rst:414
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/install/deploy.rst:420
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/install/deploy.rst:429
msgid "Serving static files and attachments"
msgstr ""
#: ../../content/administration/install/deploy.rst:431
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/install/deploy.rst:436
msgid "Serving static files"
msgstr ""
#: ../../content/administration/install/deploy.rst:438
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/install/deploy.rst:442
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/install/deploy.rst:447
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/install/deploy.rst:474
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/install/deploy.rst:481
msgid "Debian package"
msgstr ""
#: ../../content/administration/install/deploy.rst:483
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/install/deploy.rst:487
#: ../../content/administration/install/deploy.rst:501
msgid "The ``root`` and ``try_files`` should be:"
msgstr ""
#: ../../content/administration/install/deploy.rst:494
msgid "Git sources"
msgstr ""
#: ../../content/administration/install/deploy.rst:496
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/install/deploy.rst:509
msgid "Serving attachments"
msgstr ""
#: ../../content/administration/install/deploy.rst:511
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/install/deploy.rst:516
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/install/deploy.rst:526
msgid "The X-Sendfile extension for apache (and compatible web servers) does not require any supplementary configuration."
msgstr ""
#: ../../content/administration/install/deploy.rst:528
msgid "The X-Accel extension for NGINX **does** require the following additionnal configuration:"
msgstr ""
#: ../../content/administration/install/deploy.rst:537
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/install/deploy.rst:546
msgid "Security"
msgstr ""
#: ../../content/administration/install/deploy.rst:548
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/install/deploy.rst:552
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/install/deploy.rst:558
msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:"
msgstr ""
#: ../../content/administration/install/deploy.rst:561
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/install/deploy.rst:564
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/install/deploy.rst:569
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/install/deploy.rst:573
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:`db_filter`. 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/install/deploy.rst:580
msgid "Once your ``db_name`` and ``db_filter`` 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/install/deploy.rst:586
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/install/deploy.rst:591
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/install/deploy.rst:595
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/install/deploy.rst:598
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/install/deploy.rst:605
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/install/deploy.rst:611
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/install/deploy.rst:615
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/install/deploy.rst:619
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/install/deploy.rst:623
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/install/deploy.rst:634
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/install/deploy.rst:645
msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques."
msgstr ""
#: ../../content/administration/install/deploy.rst:648
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/install/deploy.rst:651
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/install/deploy.rst:659
msgid "Blocking Brute Force Attacks"
msgstr ""
#: ../../content/administration/install/deploy.rst:661
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/install/deploy.rst:665
msgid "The log entries will have the following form."
msgstr ""
#: ../../content/administration/install/deploy.rst:667
msgid "Failed login::"
msgstr ""
#: ../../content/administration/install/deploy.rst:671
msgid "Successful login::"
msgstr ""
#: ../../content/administration/install/deploy.rst:676
msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`."
msgstr ""
#: ../../content/administration/install/deploy.rst:678
msgid "For example, the following fail2ban filter definition should match a failed login::"
msgstr ""
#: ../../content/administration/install/deploy.rst:685
msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)."
msgstr ""
#: ../../content/administration/install/deploy.rst:687
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/install/deploy.rst:701
msgid "Database Manager Security"
msgstr ""
#: ../../content/administration/install/deploy.rst:703
msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing."
msgstr ""
#: ../../content/administration/install/deploy.rst:705
msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)."
msgstr ""
#: ../../content/administration/install/deploy.rst:708
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/install/deploy.rst:714
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/install/deploy.rst:720
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/install/deploy.rst:723
msgid "Be sure to setup an appropriate ``db_name`` parameter (and optionally, ``db_filter`` 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/install/deploy.rst:728
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/install/deploy.rst:732
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/install/deploy.rst:736
msgid "It should be stored securely, and should be generated randomly e.g."
msgstr ""
#: ../../content/administration/install/deploy.rst:742
msgid "which will generate a 32 characters pseudorandom printable string."
msgstr ""
#: ../../content/administration/install/deploy.rst:745
msgid "Supported Browsers"
msgstr ""
#: ../../content/administration/install/deploy.rst:747
msgid "Odoo supports all the major desktop and mobile browsers available on the market, as long as they are supported by their publishers."
msgstr ""
#: ../../content/administration/install/deploy.rst:750
msgid "Here are the supported browsers:"
msgstr ""
#: ../../content/administration/install/deploy.rst:752
msgid "Google Chrome"
msgstr ""
#: ../../content/administration/install/deploy.rst:753
msgid "Mozilla Firefox"
msgstr ""
#: ../../content/administration/install/deploy.rst:754
msgid "Microsoft Edge"
msgstr ""
#: ../../content/administration/install/deploy.rst:755
msgid "Apple Safari"
msgstr ""
#: ../../content/administration/install/deploy.rst:757
msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report."
msgstr ""
#: ../../content/administration/install/deploy.rst:762
msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped."
msgstr ""
#: ../../content/administration/install/deploy.rst:765
msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software."
msgstr ""
#: ../../content/administration/install/deploy.rst:768
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/install/deploy.rst:772
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/install/email_gateway.rst:3
msgid "Email gateway"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:5
msgid "The Odoo mail gateway allows you to inject directly all the received emails in Odoo."
msgstr ""
#: ../../content/administration/install/email_gateway.rst:7
msgid "Its principle is straightforward: your SMTP server executes the \"mailgate\" script for every new incoming email."
msgstr ""
#: ../../content/administration/install/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/install/email_gateway.rst:14
msgid "Prerequisites"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:16
msgid "Administrator access to the Odoo database."
msgstr ""
#: ../../content/administration/install/email_gateway.rst:17
msgid "Your own mail server such as Postfix or Exim."
msgstr ""
#: ../../content/administration/install/email_gateway.rst:18
msgid "Technical knowledge on how to configure an email server."
msgstr ""
#: ../../content/administration/install/email_gateway.rst:21
msgid "For Postfix"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:23
msgid "In you alias config (:file:`/etc/aliases`):"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:30
#: ../../content/administration/install/email_gateway.rst:45
msgid "Resources"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:32
msgid "`Postfix <http://www.postfix.org/documentation.html>`_"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:33
msgid "`Postfix aliases <http://www.postfix.org/aliases.5.html>`_"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:34
msgid "`Postfix virtual <http://www.postfix.org/virtual.8.html>`_"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:38
msgid "For Exim"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:47
msgid "`Exim <https://www.exim.org/docs.html>`_"
msgstr ""
#: ../../content/administration/install/email_gateway.rst:50
msgid "If you don't have access/manage your email server, use :ref:`inbound messages <email_communication/inbound_messages>`."
msgstr ""
#: ../../content/administration/install/geo_ip.rst:3
msgid "Geo IP"
msgstr ""
#: ../../content/administration/install/geo_ip.rst:6
msgid "This documentation only applies to On-premise databases."
msgstr ""
#: ../../content/administration/install/geo_ip.rst:9
msgid "Installation"
msgstr ""
#: ../../content/administration/install/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/install/geo_ip.rst:15
msgid "Move the files to the folder :file:`/usr/share/GeoIP/`."
msgstr ""
#: ../../content/administration/install/geo_ip.rst:22
msgid "Restart the server"
msgstr ""
#: ../../content/administration/install/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/install/geo_ip.rst:36
msgid ":doc:`CLI documentation </developer/reference/cli>`."
msgstr ""
#: ../../content/administration/install/geo_ip.rst:39
msgid "Test GeoIP geolocation in your Odoo website"
msgstr ""
#: ../../content/administration/install/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/install/geo_ip.rst:44
msgid "Go to your website. Open the web page that you want to test ``GeoIP``."
msgstr ""
#: ../../content/administration/install/geo_ip.rst:45
msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`."
msgstr ""
#: ../../content/administration/install/geo_ip.rst:46
msgid "Add the following piece of XML in the page :"
msgstr ""
#: ../../content/administration/install/geo_ip.rst:52
msgid "Save and refresh the page."
msgstr ""
#: ../../content/administration/install/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/install/geo_ip.rst:56
msgid "In case you read \"**geoip failure**\" instead then the geolocalization failed. The common causes are:"
msgstr ""
#: ../../content/administration/install/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/install/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/install/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/install/online.rst:3
msgid "Online"
msgstr ""
#: ../../content/administration/install/online.rst:5
msgid "Online instances are accessed using any web browser and do not require a local installation."
msgstr ""
#: ../../content/administration/install/online.rst:8
msgid "Demo"
msgstr ""
#: ../../content/administration/install/online.rst:10
msgid "To quickly try out Odoo, shared `demo <https://demo.odoo.com>`_ instances are available. No registration is required, but each instance only lives for a few hours."
msgstr ""
#: ../../content/administration/install/online.rst:14
#: ../../content/administration/maintain/domain_names.rst:166
#: ../../content/administration/maintain/domain_names.rst:236
#: ../../content/administration/maintain/supported_versions.rst:29
#: ../../content/administration/upgrade.rst:90
#: ../../content/administration/upgrade.rst:307
msgid "Odoo Online"
msgstr ""
#: ../../content/administration/install/online.rst:16
msgid "`Odoo Online <https://www.odoo.com/trial>`_ provides private instances which are fully managed and hosted by Odoo. It can be used for long-term production or to test Odoo thoroughly, including customizations that don't require code."
msgstr ""
#: ../../content/administration/install/online.rst:21
msgid "Odoo Online is incompatible with custom modules or the Odoo App Store."
msgstr ""
#: ../../content/administration/install/packages.rst:3
msgid "Packaged installers"
msgstr ""
#: ../../content/administration/install/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/install/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/install/packages.rst:13
msgid "Nightly packages may be difficult to keep up to date."
msgstr ""
#: ../../content/administration/install/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/install/packages.rst:19
msgid "It is required to be logged in as a paying customer or partner to download the Enterprise packages."
msgstr ""
#: ../../content/administration/install/packages.rst:25
#: ../../content/administration/install/source.rst:52
#: ../../content/administration/install/source.rst:129
#: ../../content/administration/install/source.rst:152
#: ../../content/administration/install/source.rst:174
#: ../../content/administration/install/source.rst:199
#: ../../content/administration/install/source.rst:228
#: ../../content/administration/install/source.rst:271
#: ../../content/administration/install/source.rst:384
#: ../../content/administration/install/source.rst:446
msgid "Linux"
msgstr ""
#: ../../content/administration/install/packages.rst:28
#: ../../content/administration/install/source.rst:116
msgid "Prepare"
msgstr ""
#: ../../content/administration/install/packages.rst:30
msgid "Odoo needs a `PostgreSQL <https://www.postgresql.org/>`_ server to run properly."
msgstr ""
#: ../../content/administration/install/packages.rst:34
#: ../../content/administration/install/packages.rst:70
#: ../../content/administration/install/packages.rst:100
#: ../../content/administration/install/source.rst:278
msgid "Debian/Ubuntu"
msgstr ""
#: ../../content/administration/install/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/install/packages.rst:44
#: ../../content/administration/install/packages.rst:80
#: ../../content/administration/install/packages.rst:132
msgid "Fedora"
msgstr ""
#: ../../content/administration/install/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/install/packages.rst:57
#: ../../content/administration/install/source.rst:416
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/install/packages.rst:63
msgid "Repository"
msgstr ""
#: ../../content/administration/install/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/install/packages.rst:78
msgid "Use the usual `apt-get upgrade` command to keep the installation up-to-date."
msgstr ""
#: ../../content/administration/install/packages.rst:90
msgid "Currently, there is no nightly repository for the Enterprise edition."
msgstr ""
#: ../../content/administration/install/packages.rst:93
msgid "Distribution package"
msgstr ""
#: ../../content/administration/install/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/install/packages.rst:103
msgid "Odoo 17 'deb' package currently supports `Debian Buster <https://www.debian.org/releases/buster/>`_ and `Ubuntu 18.04 <https://releases.ubuntu.com/18.04>`_ or above."
msgstr ""
#: ../../content/administration/install/packages.rst:107
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/install/packages.rst:117
msgid "The `python3-xlwt` Debian package, needed to export into the XLS format, does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it manually with the following:"
msgstr ""
#: ../../content/administration/install/packages.rst:124
msgid "The `num2words` Python package - needed to render textual amounts - does not exist in Debian Buster nor Ubuntu 18.04, which could cause problems with the `l10n_mx_edi` module. If needed, install it manually with the following:"
msgstr ""
#: ../../content/administration/install/packages.rst:135
msgid "Odoo 17 'rpm' package supports Fedora 36."
msgstr ""
#: ../../content/administration/install/packages.rst:137
msgid "Once downloaded, the package can be installed using the 'dnf' package manager:"
msgstr ""
#: ../../content/administration/install/packages.rst:148
#: ../../content/administration/install/source.rst:70
#: ../../content/administration/install/source.rst:133
#: ../../content/administration/install/source.rst:158
#: ../../content/administration/install/source.rst:180
#: ../../content/administration/install/source.rst:208
#: ../../content/administration/install/source.rst:239
#: ../../content/administration/install/source.rst:324
#: ../../content/administration/install/source.rst:393
#: ../../content/administration/install/source.rst:456
msgid "Windows"
msgstr ""
#: ../../content/administration/install/packages.rst:151
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/install/packages.rst:155
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/install/packages.rst:158
msgid "Execute the downloaded file."
msgstr ""
#: ../../content/administration/install/packages.rst:161
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/install/packages.rst:164
msgid "Accept the `UAC <https://en.wikipedia.org/wiki/User_Account_Control>`_ prompt."
msgstr ""
#: ../../content/administration/install/packages.rst:165
msgid "Go through the installation steps."
msgstr ""
#: ../../content/administration/install/packages.rst:167
msgid "Odoo launches automatically at the end of the installation."
msgstr ""
#: ../../content/administration/install/source.rst:3
msgid "Source"
msgstr ""
#: ../../content/administration/install/source.rst:5
msgid "The source 'installation' is not about installing Odoo but running it directly from the source instead."
msgstr ""
#: ../../content/administration/install/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/install/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/install/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/install/source.rst:19
msgid "Fetch the sources"
msgstr ""
#: ../../content/administration/install/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/install/source.rst:24
msgid "Archive"
msgstr ""
#: ../../content/administration/install/source.rst:26
msgid "Community edition:"
msgstr ""
#: ../../content/administration/install/source.rst:28
#: ../../content/administration/install/source.rst:34
msgid "`Odoo download page <https://www.odoo.com/page/download>`_"
msgstr ""
#: ../../content/administration/install/source.rst:29
msgid "`GitHub Community repository <https://github.com/odoo/odoo>`_"
msgstr ""
#: ../../content/administration/install/source.rst:30
msgid "`Nightly server <https://nightly.odoo.com>`_"
msgstr ""
#: ../../content/administration/install/source.rst:32
msgid "Enterprise edition:"
msgstr ""
#: ../../content/administration/install/source.rst:35
msgid "`GitHub Enterprise repository <https://github.com/odoo/enterprise>`_"
msgstr ""
#: ../../content/administration/install/source.rst:40
msgid "Git"
msgstr ""
#: ../../content/administration/install/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/install/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/getting_started>`."
msgstr ""
#: ../../content/administration/install/source.rst:56
#: ../../content/administration/install/source.rst:74
#: ../../content/administration/install/source.rst:92
msgid "Clone with HTTPS"
msgstr ""
#: ../../content/administration/install/source.rst:63
#: ../../content/administration/install/source.rst:81
#: ../../content/administration/install/source.rst:99
msgid "Clone with SSH"
msgstr ""
#: ../../content/administration/install/source.rst:88
#: ../../content/administration/install/source.rst:141
#: ../../content/administration/install/source.rst:164
#: ../../content/administration/install/source.rst:186
#: ../../content/administration/install/source.rst:213
#: ../../content/administration/install/source.rst:253
#: ../../content/administration/install/source.rst:347
#: ../../content/administration/install/source.rst:405
#: ../../content/administration/install/source.rst:467
msgid "Mac OS"
msgstr ""
#: ../../content/administration/install/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/install/source.rst:119
msgid "Python"
msgstr ""
#: ../../content/administration/install/source.rst:121
msgid "Odoo requires **Python 3.10** or later to run."
msgstr ""
#: ../../content/administration/install/source.rst:123
msgid "Minimum requirement updated from Python 3.7 to Python 3.10."
msgstr ""
#: ../../content/administration/install/source.rst:131
msgid "Use a package manager to download and install Python 3 if needed."
msgstr ""
#: ../../content/administration/install/source.rst:135
msgid "`Download the latest version of Python 3 <https://www.python.org/downloads/windows/>`_ and install it."
msgstr ""
#: ../../content/administration/install/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/install/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/install/source.rst:147
msgid "If Python 3 is already installed, make sure that the version is 3.7 or above, as previous versions are not compatible with Odoo."
msgstr ""
#: ../../content/administration/install/source.rst:170
msgid "Verify that `pip <https://pip.pypa.io>`_ is also installed for this version."
msgstr ""
#: ../../content/administration/install/source.rst:195
msgid "Odoo uses PostgreSQL as its database management system."
msgstr ""
#: ../../content/administration/install/source.rst:201
msgid "Use a package manager to download and install PostgreSQL (supported versions: 12.0 or above). It can be achieved by executing the following:"
msgstr ""
#: ../../content/administration/install/source.rst:210
msgid "`Download PostgreSQL <https://www.postgresql.org/download/windows>`_ (supported versions: 12.0 or above) and install it."
msgstr ""
#: ../../content/administration/install/source.rst:215
msgid "Use `Postgres.app <https://postgresapp.com>`_ to download and install PostgreSQL (supported version: 12.0 or above)."
msgstr ""
#: ../../content/administration/install/source.rst:219
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/install/source.rst:223
msgid "By default, the only user is `postgres`. As Odoo forbids connecting as `postgres`, create a new PostgreSQL user."
msgstr ""
#: ../../content/administration/install/source.rst:236
#: ../../content/administration/install/source.rst:261
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/install/source.rst:241
msgid "Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program Files\\\\PostgreSQL\\\\<version>\\\\bin`) to the `PATH`."
msgstr ""
#: ../../content/administration/install/source.rst:243
msgid "Create a postgres user with a password using the pg admin gui:"
msgstr ""
#: ../../content/administration/install/source.rst:245
msgid "Open **pgAdmin**."
msgstr ""
#: ../../content/administration/install/source.rst:246
msgid "Double-click the server to create a connection."
msgstr ""
#: ../../content/administration/install/source.rst:247
msgid "Select :menuselection:`Object --> Create --> Login/Group Role`."
msgstr ""
#: ../../content/administration/install/source.rst:248
msgid "Enter the username in the **Role Name** field (e.g., `odoo`)."
msgstr ""
#: ../../content/administration/install/source.rst:249
msgid "Open the **Definition** tab, enter a password (e.g., `odoo`), and click **Save**."
msgstr ""
#: ../../content/administration/install/source.rst:250
msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to `Yes`."
msgstr ""
#: ../../content/administration/install/source.rst:267
msgid "Dependencies"
msgstr ""
#: ../../content/administration/install/source.rst:273
msgid "Using **distribution packages** is the preferred way of installing dependencies. Alternatively, install the Python dependencies with **pip**."
msgstr ""
#: ../../content/administration/install/source.rst:280
msgid "For Debian-based systems, the packages are listed in the `debian/control <https://github.com/odoo/odoo/blob/17.0/debian/control>`_ file of the Odoo sources."
msgstr ""
#: ../../content/administration/install/source.rst:283
msgid "On Debian/Ubuntu, the following commands should install the required packages:"
msgstr ""
#: ../../content/administration/install/source.rst:290
msgid "Install with pip"
msgstr ""
#: ../../content/administration/install/source.rst:292
msgid "As some of the Python packages need a compilation step, they require system libraries to be installed."
msgstr ""
#: ../../content/administration/install/source.rst:295
msgid "On Debian/Ubuntu, the following command should install these required libraries:"
msgstr ""
#: ../../content/administration/install/source.rst:301
msgid "Odoo dependencies are listed in the :file:`requirements.txt` file located at the root of the Odoo Community directory."
msgstr ""
#: ../../content/administration/install/source.rst:305
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/install/source.rst:312
#: ../../content/administration/install/source.rst:334
#: ../../content/administration/install/source.rst:353
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/install/source.rst:316
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/install/source.rst:326
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/install/source.rst:330
#: ../../content/administration/install/source.rst:349
msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo Community directory."
msgstr ""
#: ../../content/administration/install/source.rst:338
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/install/source.rst:357
msgid "Navigate to the path of the Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:"
msgstr ""
#: ../../content/administration/install/source.rst:367
msgid "Non-Python dependencies must be installed with a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
msgstr ""
#: ../../content/administration/install/source.rst:370
msgid "Download and install the **Command Line Tools**:"
msgstr ""
#: ../../content/administration/install/source.rst:376
msgid "Use the package manager to install non-Python dependencies."
msgstr ""
#: ../../content/administration/install/source.rst:379
msgid "For languages using a **right-to-left interface** (such as Arabic or Hebrew), the `rtlcss` package is required."
msgstr ""
#: ../../content/administration/install/source.rst:386
msgid "Download and install **nodejs** and **npm** with a package manager."
msgstr ""
#: ../../content/administration/install/source.rst:387
#: ../../content/administration/install/source.rst:396
#: ../../content/administration/install/source.rst:409
msgid "Install `rtlcss`:"
msgstr ""
#: ../../content/administration/install/source.rst:395
msgid "Download and install `nodejs <https://nodejs.org/en/download>`_."
msgstr ""
#: ../../content/administration/install/source.rst:402
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/install/source.rst:407
msgid "Download and install **nodejs** with a package manager (`Homebrew <https://brew.sh/>`_, `MacPorts <https://www.macports.org>`_)."
msgstr ""
#: ../../content/administration/install/source.rst:424
msgid "Running Odoo"
msgstr ""
#: ../../content/administration/install/source.rst:426
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/install/source.rst:429
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/install/source.rst:433
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/install/source.rst:437
msgid "Common necessary configurations are:"
msgstr ""
#: ../../content/administration/install/source.rst:439
msgid "PostgreSQL user and password."
msgstr ""
#: ../../content/administration/install/source.rst:440
msgid "Custom addon paths beyond the defaults to load custom modules."
msgstr ""
#: ../../content/administration/install/source.rst:442
msgid "A typical way to run the server would be:"
msgstr ""
#: ../../content/administration/install/source.rst:453
#: ../../content/administration/install/source.rst:474
msgid "Where `CommunityPath` is the path of the Odoo Community installation, and `mydb` is the name of the PostgreSQL database."
msgstr ""
#: ../../content/administration/install/source.rst:463
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/install/source.rst:477
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/install/source.rst:482
msgid "From there, create and manage new :doc:`users <../../applications/general/users/manage_users>`."
msgstr ""
#: ../../content/administration/install/source.rst:483
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/install/source.rst:487
msgid ":doc:`The list of CLI arguments for odoo-bin </developer/reference/cli>`"
msgstr ""
#: ../../content/administration/maintain.rst:5
msgid "Maintain"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:3
msgid "Connect Microsoft Outlook 365 to Odoo using Azure OAuth"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:5
msgid "Odoo is compatible with Microsoft's Azure OAuth for Microsoft 365. In order to send and receive secure emails from a custom domain, all that is required is to configure a few settings on the Azure platform and on the back end of the Odoo database. This configuration works with either a personal email address or an address created by a custom domain."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:11
msgid "`Microsoft Learn: Register an application with the Microsoft identity platform <https://learn.microsoft.com/azure/active-directory/develop/quickstart-register-app>`_"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:15
msgid ":doc:`/applications/general/auth/azure`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:16
msgid ":doc:`/applications/productivity/calendar/outlook`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:19
msgid "Setup in Microsoft Azure Portal"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:22
msgid "Create a new application"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:24
msgid "To get started, go to `Microsoft's Azure Portal <https://portal.azure.com/>`_. Log in with the :guilabel:`Microsoft Outlook Office 365` account if there is one, otherwise log in with the personal :guilabel:`Microsoft account`. A user with administrative access to the Azure Settings will need to connect and perform the following configuration. Next, navigate to the section labeled :guilabel:`Manage Microsoft Entra ID` (formally *Azure Active Directory*)."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:30
msgid "Now, click on :guilabel:`Add (+)`, located in the top menu, and then select :guilabel:`App registration`. On the :guilabel:`Register an application` screen, rename the :guilabel:`Name` to `Odoo` or something recognizable. Under the :guilabel:`Supported account types` section select :guilabel:`Accounts in any organizational directory (Any Microsoft Entra ID directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:36
msgid "Under the :guilabel:`Redirect URL` section, select :guilabel:`Web` as the platform, and then input `https://<odoo base url>/microsoft_outlook/confirm` in the :guilabel:`URL` field. The Odoo base URL is the canonical domain at which your Odoo instance can be reached in the URL field."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:41
msgid "*mydatabase.odoo.com*, where *mydatabase* is the actual prefix of the database's subdomain, assuming it's hosted on Odoo.com"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:44
msgid "After the URL has been added to the field, :guilabel:`Register` the application so it is created."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:47
msgid "API permissions"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:49
msgid "The :guilabel:`API permissions` should be set next. Odoo will need specific API permissions to be able to read (IMAP) and send (SMTP) emails in the Microsoft 365 setup. First, click the :guilabel:`API permissions` link, located in the left menu bar. Next, click on the :guilabel:`(+) Add a Permission` button and select :guilabel:`Microsoft Graph` under :guilabel:`Commonly Used Microsoft APIs`. After, select the :guilabel:`Delegated Permissions` option."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:55
msgid "In the search bar, search for the following :guilabel:`Deregulated permissions` and click :guilabel:`Add permissions` for each one:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:58
msgid ":guilabel:`SMTP.Send`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:59
msgid ":guilabel:`IMAP.AccessAsUser.All`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:62
msgid "The :guilabel:`User.Read` permission will be added by default."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "API permissions needed for Odoo integration are listed under the Microsoft Graph."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:69
msgid "Assign users and groups"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:71
msgid "After adding the API permissions, navigate back to the :guilabel:`Overview` of the :guilabel:`Application` in the top of the left sidebar menu."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:74
msgid "Now, add users to this application. Under the :guilabel:`Essentials` overview table, click on the link labeled :guilabel:`Managed Application in Local Directory`, or the last option on the bottom right-hand side of the table."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Add users/groups by clicking the Managed application in local directory link for the\n"
"created application."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:83
msgid "In the left sidebar menu, select :guilabel:`Users and Groups`. Next, click on :guilabel:`(+) Add User/Group`. Depending on the account, either a :guilabel:`Group` and a :guilabel:`User` can be added, or only :guilabel:`Users`. Personal accounts will only allow for :guilabel:`Users` to be added."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:88
msgid "Under :guilabel:`Users` or :guilabel:`Groups`, click on :guilabel:`None Selected` and add the users or group of users that will be sending emails from the :guilabel:`Microsoft account` in Odoo. :guilabel:`Add` the users/groups, click :guilabel:`Select`, and then :guilabel:`Assign` them to the application."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:94
msgid "Create credentials"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:96
msgid "Now that the Microsoft Azure app is set up, credentials need to be created for the Odoo setup. These include the :guilabel:`Client ID` and :guilabel:`Client Secret`. To start, the :guilabel:`Client ID` can be copied from the :guilabel:`Overview` page of the app. The :guilabel:`Client ID` or :guilabel:`Application ID` is located under the :guilabel:`Display Name` in the :guilabel:`Essentials` overview of the app."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Application/Client ID located in the Overview of the app."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:106
msgid "Next, the :guilabel:`Client Secret Value` needs to be retrieved. To get this value, click on :guilabel:`Certificates & Secrets` in the left sidebar menu. Then, a :guilabel:`Client Secret` needs to be produced. In order to do this, click on the :guilabel:`(+) New Client Secret` button."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:110
msgid "A window on the right will populate with a button labeled :guilabel:`Add a client secret`. Under :guilabel:`Description`, type in `Odoo Fetchmail` or something recognizable, and then set the :guilabel:`expiration date`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:115
msgid "A new :guilabel:`Client Secret` will need to be produced and configured if the first one expires. In this event, there could be an interruption of service, so the expiration date should be noted and set to the furthest possible date."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:119
msgid "Next, click on :guilabel:`Add` when these two values are entered. A :guilabel:`Client Secret Value` and :guilabel:`Secret ID` will be created. It is important to copy the :guilabel:`Value` or :guilabel:`Client Secret Value` into a notepad as it will become encrypted after leaving this page. The :guilabel:`Secret ID` is not needed."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Client Secret Value or Value in the app's credentials."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:128
msgid "After these steps, the following items should be ready to be set up in Odoo:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:130
msgid "A client ID (:guilabel:`Client ID` or :guilabel:`Application ID`)"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:131
msgid "A client secret (:guilabel:`Value` or :guilabel:`Client Secret Value`)"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:133
msgid "This completes the setup on the :guilabel:`Microsoft Azure Portal` side."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:136
#: ../../content/administration/maintain/google_oauth.rst:111
msgid "Setup in Odoo"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:139
msgid "Enter Microsoft Outlook credentials"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:141
msgid "First, open the Odoo database and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Outlook`. After that, install the module called :guilabel:`Microsoft Outlook`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:145
msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` is checked. This populates a new option for :guilabel:`Outlook Credentials`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:149
msgid ":guilabel:`Save` the progress."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:151
msgid "Then, copy and paste the :guilabel:`Client ID` (Application ID) and :guilabel:`Client Secret (Client Secret Value)` into the respective fields and :guilabel:`Save` the settings."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Outlook Credentials in Odoo General Settings."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:159
#: ../../content/administration/maintain/google_oauth.rst:127
msgid "Configure outgoing email server"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:161
msgid "On the :guilabel:`General Settings` page, under the :guilabel:`Custom Email Servers` setting, click the :guilabel:`Outgoing Email Servers` link to configure the Microsoft account."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:164
msgid "Then, create a new email server and check the box for :guilabel:`Outlook`. Next, fill in the :guilabel:`Name` (it can be anything) and the Microsoft Outlook email :guilabel:`Username`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:167
msgid "If the :guilabel:`From Filter` field is empty, enter either a :ref:`domain or email address <email_communication/default>`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:170
msgid "Then, click on :guilabel:`Connect your Outlook account`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:172
msgid "A new window from Microsoft opens to complete the :guilabel:`authorization process`. Select the appropriate email address that is being configured in Odoo."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Permission page to grant access between newly created app and Odoo."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:179
msgid "Then, allow Odoo to access the Microsoft account by clicking on :guilabel:`Yes`. After this, the page will navigate back to the newly configured :guilabel:`Outgoing Mail Server` in Odoo. The configuration automatically loads the :guilabel:`token` in Odoo, and a tag stating :guilabel:`Outlook Token Valid` appears in green."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Valid Outlook Token indicator."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:188
msgid "Finally, click :guilabel:`Test Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Microsoft Outlook using OAuth authentication."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:194
msgid "Configuration with a single outgoing mail server"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:196
msgid "Configuring a single outgoing server is the simplest configuration available for Microsoft Azure and it doesn't require extensive access rights for the users in the database."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:199
msgid "A generic email address would be used to send emails for all users within the database. For example it could be structured with a `notifications` alias (`notifications@example.com`) or `contact` alias (`contact@example.com`). This address must be set as the :guilabel:`FROM Filtering` on the server. This address must also match the `{mail.default.from}@{mail.catchall.domain}` key combination in the system parameters."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:206
#: ../../content/administration/maintain/azure_oauth.rst:247
msgid "For more information on the from filter visit: :ref:`email_communication/default`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:209
#: ../../content/administration/maintain/azure_oauth.rst:254
msgid "The :guilabel:`System Parameters` can be accessed by activating :ref:`developer-mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:212
msgid "When using this configuration, every email that is sent from the database will use the address of the configured `notification` mailbox. However it should be noted that the name of the sender will appear but their email address will change:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:-1
msgid "Name from real sender with static email."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:221
msgid "Single outgoing mail server configuration:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:223
msgid "Outgoing mail server **username** (login) = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:224
msgid "Outgoing mail server :guilabel:`FROM Filtering` = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:225
#: ../../content/administration/maintain/azure_oauth.rst:279
msgid "`mail.catchall.domain` in system parameters = `example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:226
#: ../../content/administration/maintain/azure_oauth.rst:280
msgid "`mail.default.from` in system parameters = `notifications`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:229
msgid "User-specific (multiple user) configuration"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:231
msgid "In addition to a generic email server, individual email servers can be set up for users in a database. These email addresses must be set as the :guilabel:`FROM Filtering` on each individual server for this configuration to work."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:235
msgid "This configuration is the more difficult of the two Microsoft Azure configurations, in that it requires all users configured with email servers to have access rights to settings in order to establish a connection to the email server."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:240
#: ../../content/administration/odoo_sh/getting_started/branches.rst:480
msgid "Setup"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:242
msgid "Each user should have a separate email server set up. The :guilabel:`FROM Filtering` should be set so that only the user's email is sent from that server. In other words, only a user with an email address that matches the set :guilabel:`FROM Filtering` is able to use this server."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:249
msgid "A :ref:`fallback server <azure_oauth/notifications>` must be setup to allow for the sending of :guilabel:`notifications`. The :guilabel:`FROM Filtering` for this server should have the value of the `{mail.default.from}@{mail.catchall.domain}`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:258
msgid "The configuration for this transactional email server can work alongside an outgoing mass-mailing email server. The :guilabel:`FROM Filtering` for the mass-mailing email server can remain empty, but it's require to be added in the settings of the *Email Marketing* application."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:263
msgid "For more information on setting the mass-mailing email server visit :ref:`email_communication/mass_mails`."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:267
msgid "Multiple user outgoing mail server configuration:"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:270
msgid "User #1 mailbox"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:270
msgid "Outgoing mail server #1 **username** (login) = `john@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:271
msgid "Outgoing mail server #1 :guilabel:`FROM Filtering` = `john@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:273
msgid "User #2 mailbox"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:273
msgid "Outgoing mail server #2 **username** (login) = `jane@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:274
msgid "Outgoing mail server #2 :guilabel:`FROM Filtering` = `jane@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:276
msgid "Notifications mailbox"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:276
msgid "Outgoing mail server #3 **username** (login) = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:277
msgid "Outgoing mail server #3 :guilabel:`FROM Filtering` = `notifications@example.com`"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:279
msgid "System Parameters"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:283
msgid "Configure incoming email server"
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:285
msgid "The incoming account should be configured in a similar way to the outgoing email account. Navigate to the :guilabel:`Incoming Mail Servers` in the :guilabel:`Technical Menu` and :guilabel:`Create` a new configuration. Check or Select the button next to :guilabel:`Outlook Oauth Authentication` and enter the :guilabel:`Microsoft Outlook username`. Click on :guilabel:`Connect your Outlook account`. Odoo will state: :guilabel:`Outlook Token Valid` Now :guilabel:`Test and Confirm` the account. The account should be ready to receive email to the Odoo database."
msgstr ""
#: ../../content/administration/maintain/azure_oauth.rst:293
msgid ":doc:`../../applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:3
#: ../../content/administration/maintain/odoo_online.rst:70
msgid "Domain names"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:5
msgid "A **domain name** works as an address for your website. It makes the Internet much more accessible as it allows users to type a meaningful web address, such as ``www.odoo.com``, rather than its server's IP address with a series of numbers."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:9
msgid "You can use a custom domain name to access your Odoo database and websites:"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:11
msgid "By :ref:`registering a free domain name with Odoo <domain-name/odoo-register>` (for Odoo Online databases)"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:13
msgid "By :ref:`configuring a custom domain that you already own <domain-name/existing>`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:16
msgid "Odoo Online and Odoo.sh databases, including their websites, use by default a subdomain of ``odoo.com`` for both the URL and the emails (e.g., ``https://example.odoo.com``)."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:20
msgid "Odoo offers a :ref:`free custom domain name <domain-name/odoo-register>` to all Odoo Online databases for one year. Visitors can then access your website with an address such as ``www.example.com`` rather than the default ``example.odoo.com``."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:25
msgid "`Odoo Tutorials: Register a Free Domain Name <https://www.odoo.com/slides/slide/register-a-free-domain-name-1663>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:27
msgid "`Odoo Quick Tips: Get a free domain name! <https://www.youtube.com/watch?v=eAfgeNOHLP4>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:32
msgid "About domain names"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:34
msgid "Having a **good domain name** is as important to your branding as the name of your business or organization as it is the first thing your visitors will notice. We recommend you keep them *simple, short, easy to remember and spell*."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:38
msgid "A **subdomain** is a domain that is a part of another domain. It often refers to the additional part that comes before the main domain name. Traditionally, most websites use the ``www.`` subdomain, but any string of letters can be used as well. You can use subdomains to direct your visitors to other websites than your main website or to specific pages (e.g., ``experience.odoo.com`` points to a specific page.)"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:44
msgid "All domain names are referenced in the **Domain Name System**, or **DNS**, which works as a giant directory for the Internet. There are many DNS servers, so any modification to the DNS can take up to 72 hours to propagate worldwide on all servers."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:51
msgid "Indexing of domain names by search engines"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:53
msgid "Search engines, such as Google and Bing, rely on web crawlers (:dfn:`robots that explore and analyze the web`) to index all websites and their related domain names. These crawlers discover new URLs thanks to links on known web pages. As a result, search engines should index domain names automatically after a while, as long as their URLs are mentioned elsewhere on the Internet."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:58
msgid "Improving the appearance and positioning of web pages on search engines is a practice named \"Search Engine Optimization\" (SEO)."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:62
msgid "Adding relevant content, optimizing metadata, and building high-quality backlinks can all help improve a website's search engine visibility."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:65
msgid "Some search engines provide tools for web admins, such as `Google Search Console <https://search.google.com/search-console>`_ and `Bing Webmaster Tools <https://www.bing.com/webmasters>`_, to help you analyze and improve your page ranking. To use these services, you must prove that you are the owner of your domain name. One way to verify the ownership of your domain name is by adding a DNS record. You can do this for :ref:`domain names registered with Odoo <domain-name/odoo-manage>` and for domain names managed by other providers."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:74
msgid ":doc:`/applications/websites/website/pages/seo`"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:75
msgid "`Google Search Console Help - Verify your site ownership <https://support.google.com/webmasters/answer/9008080>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:76
msgid "`Bing Webmaster Tools - Add and Verify site <https://www.bing.com/webmasters/help/add-and-verify-site-12184f8b>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:81
msgid "Register a free domain name with Odoo"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:83
msgid "You can register a domain name for your Odoo Online database directly from Odoo Website or your database manager."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:87
msgid "Your domain name is **free for one year** if you register it with Odoo!"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:88
msgid "The domain name is registered with `Gandi <https://www.gandi.net/>`_, the domain name registrar."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:90
msgid "You are the owner of the domain name and can use it for other purposes."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:91
msgid "Odoo manages payment and technical support for you."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:92
msgid "This offer doesn't include any mailbox. However, you can :ref:`configure your MX records <domain-name/odoo-manage>` to use your own email server or solution such as Google Workspace."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:95
msgid "To do so, go to :menuselection:`Website --> Domain Name`. Alternatively, open your `database manager <https://www.odoo.com/my/databases>`_, click on the :guilabel:`settings` button next to your database, then on :guilabel:`Domain names`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:-1
msgid "Clicking on Domain Names from an Odoo website"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:103
msgid "Search for the domain name of your choice to check its availability, then select the one you want to register for your website."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:-1
msgid "The search of the domain name example.com shows which associated domains are available."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:110
msgid "Next, fill in the form with your information to become the domain name owner."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:112
msgid "Your domain name is directly linked to your database, but you still have to :ref:`map your domain name with your website <domain-name/website-map>`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:116
msgid "Free domain names are also available for free Odoo Online databases (if you installed one app only, for example). In this case, Odoo reviews your request and your website to avoid abuse. This process can take several days due to the success of the offer."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:119
msgid "This is not available for Odoo.sh databases yet."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:124
msgid "Manage your domain name registered with Odoo"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:126
msgid "To manage the DNS records of your domain name registered with Odoo or to visualize the contacts associated with it, open your `database manager <https://www.odoo.com/my/databases>`_, click on the :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on :guilabel:`Contacts` or :guilabel:`DNS`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:-1
msgid "Management of the domain names linked to an Odoo database"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:136
msgid "Please `submit a support ticket <https://www.odoo.com/help>`_ if you need further assistance to manage your domain name."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:142
msgid "Configure your existing domain name"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:144
msgid "If you already own a domain name, you can use it to point to your website."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:146
msgid "To avoid any issue with the :ref:`SSL certificate validation <domain-name/ssl>`, we highly recommend that you proceed with the following actions in this order:"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:149
msgid ":ref:`Add a CNAME record <domain-name/cname>` on your domain name's DNS zone."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:150
msgid ":ref:`Map your domain name with your Odoo database <domain-name/db-map>`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:151
msgid ":ref:`Map your domain name with your Odoo website <domain-name/website-map>`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:156
msgid "Add a CNAME record"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:158
msgid "A **CNAME record** is a type of DNS record that points to the domain of another website rather than directly to an IP address."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:161
msgid "You need a CNAME record that points to your Odoo database. The requirements are detailed in your database manager."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:168
msgid "The target address is the current address of your database, as defined at its creation (e.g., ``example.odoo.com``)"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:171
#: ../../content/administration/maintain/domain_names.rst:250
#: ../../content/administration/maintain/supported_versions.rst:30
#: ../../content/administration/odoo_sh.rst:5
#: ../../content/administration/upgrade.rst:120
#: ../../content/administration/upgrade.rst:318
msgid "Odoo.sh"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:173
msgid "Your project's main address is defined in :menuselection:`Settings --> Project Name`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:175
msgid "If you want to target a specific branch (production, staging or development), go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, and click on :guilabel:`How to set up my domain?`. A message indicates which address your CNAME record should target."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:180
#: ../../content/administration/maintain/domain_names.rst:222
msgid "Open your domain name's manager dashboard."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:181
msgid "Open the **DNS zone** management page for the domain name you want to configure."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:182
msgid "Create a **CNAME record** pointing to the address of your database."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:184
msgid "While Odoo suggests creating a CNAME record for your ``www.`` subdomain (``www.example.com``), you can of course use any domain name of your choice, with any subdomain (e.g., ``anything.example.com``)."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:189
msgid "You own the domain name ``example.com``, and you have an Odoo Online database at the address ``example.odoo.com``. You want to access your Odoo database primarily with the domain ``www.example.com`` but also with the :ref:`naked domain <domain-name/naked-domain>` ``example.com``."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:194
msgid "To do so, you create a CNAME record for the ``www`` subdomain, with ``example.odoo.com`` as the target. The DNS zone manager generates the following rule and adds it to your DNS zone: ``www IN CNAME example.odoo.com.``"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:198
msgid "You also create a redirection from ``example.com`` to ``wwww.example.com``."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:200
msgid "Your new DNS records are propagated to all DNS servers."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:203
msgid "Here are some specific guidelines to create a CNAME record:"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:205
msgid "`GoDaddy <https://www.godaddy.com/help/add-a-cname-record-19236>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:206
msgid "`Namecheap <https://www.namecheap.com/support/knowledgebase/article.aspx/9646/2237/how-to-create-a-cname-record-for-your-domain>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:207
msgid "`OVH <https://docs.ovh.com/us/en/domains/web_hosting_how_to_edit_my_dns_zone/#add-a-new-dns-record>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:208
msgid "`CloudFlare <https://support.cloudflare.com/hc/en-us/articles/360019093151>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:209
msgid "`Google Domains <https://support.google.com/domains/answer/3290350?hl=en>`_"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:214
msgid "Naked domain"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:216
msgid "A **naked domain** is a domain name that doesn't have any subdomain at the beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:219
msgid "You may want your naked domain to redirect to your website as some visitors may not type the full domain name to access your website."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:223
msgid "Create a **redirection** from the naked domain (``example.com``) to your main domain name (``www.example.com``)."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:227
msgid "Depending on your domain name registrar, this redirection may be already pre-configured."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:232
msgid "Map your domain name with your Odoo database"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:238
msgid "Open your `database manager <https://www.odoo.com/my/databases>`_, click on the :guilabel:`settings` button next to your database, on :guilabel:`Domain names`, and then on :guilabel:`Use my own domain` at the bottom of the right column."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:242
msgid "Type the domain name you want to add to this database, then click on :guilabel:`Verify` to check if the CNAME record is correctly configured. Once done, click on :guilabel:`I confirm, it's done`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:0
msgid "Verification of the CNAME records of a domain name before mapping it with a database"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:252
msgid "Go to :menuselection:`Branches --> select your branch --> Settings --> Custom domains`, type the domain name you want to add to this database, then click on :guilabel:`Add domain`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:0
msgid "Mapping a domain name with an Odoo.sh branch"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:260
msgid ":ref:`Odoo.sh branches: settings tab <odoosh-gettingstarted-branches-tabs-settings>`"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:263
msgid "Make sure to :ref:`add a CNAME record <domain-name/cname>` to your domain name's DNS **before** mapping your domain name with your Odoo database."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:266
msgid "Failing to do so may impede the validation of the :ref:`SSL certificate <domain-name/ssl>` and would result in a *certificate name mismatch* error. This is often displayed by web browsers as a warning such as *\"Your connection is not private\"*."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:270
msgid "If this is the case and you have added the domain name to your database's settings less than five days ago, wait 24 hours as the validation may still happen. Otherwise, please `submit a support ticket <https://www.odoo.com/help>`_ including screenshots of your CNAME records."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:277
msgid "SSL encryption (HTTPS protocol)"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:279
msgid "**SSL encryption** is an encryption-based Internet security protocol. It allows your visitors to navigate your website through a secure connection, which appears as an ``https://`` protocol at the beginning of your web address, rather than a non-secure ``http://`` protocol."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:283
msgid "Odoo generates a separate SSL certificate for each domain :ref:`mapped in the database manager <domain-name/db-map>`, using integration with `Let's Encrypt Certificate Authority and ACME protocol <https://letsencrypt.org/how-it-works/>`_."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:288
msgid "The certificate generation may take up to 24h."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:289
msgid "Several attempts to validate your certificate are made during the five days following the moment you add your domain name in your database's settings."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:291
msgid "If you already use another service, you can keep using it or simply change for Odoo."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:296
msgid "Web base URL of a database"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:299
msgid "If you have Odoo Website, you can disregard this part and directly :ref:`map your domain name with your website <domain-name/website-map>`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:302
msgid "The **web base URL** of a database, or **root URL** affects your main website address and all the links sent to your customers (e.g., quotations, portal links, etc.)."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:305
msgid "To configure it, access your Odoo database with your custom address, then log in as an administrator of your database (any user in the *Settings* group) from the login screen."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:309
msgid "Connecting to your database with the original Odoo subdomain address (e.g., ``example.odoo.com`` also updates the web base URL of your database. See below to prevent these automatic updates."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:312
msgid "Alternatively, you can do it manually. To do so, activate the :ref:`developer mode <developer-mode>`, then go to :menuselection:`Settings --> Technical --> System Parameters`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:315
msgid "Find the key called ``web.base.url`` (or create it if it does not exist) and enter the full address of your website as value, such as ``https://www.example.com``."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:319
msgid "The URL must include the protocol ``https://`` (or ``http://``) and must not end with a slash (``/``)."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:322
msgid "To prevent the automatic update of the web base URL when an administrator logs in the database, you can create the following System Parameter:"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:325
msgid "key: ``web.base.url.freeze``"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:326
msgid "value: ``True``"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:331
msgid "Map your domain name with your website"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:333
msgid "Mapping your domain name to your website isn't the same as mapping it with your database:"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:335
msgid "It defines your domain name as the main one for your website, helping search engines to index your website properly."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:337
msgid "It defines your domain name as the base URL for your database, including the portal links sent by email to your customers."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:339
msgid "If you have multiple websites, it maps your domain name with the appropriate website."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:341
msgid "Go to :menuselection:`Website --> Configuration --> Settings --> Website Info`. If you have multiple websites, select the one you want to configure."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:344
msgid "In the :guilabel:`Domain` field, fill in the web address of your website (e.g., ``https://www.example.com``) and click on :guilabel:`Save`."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:-1
msgid "Configuring https://www.example.com as the Domain of the website"
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:352
msgid "Mapping your domain name with your Odoo website prevents Google from indexing both your custom domain name ``www.example.com`` and your original odoo database address ``example.odoo.com``."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:355
msgid "If both addresses are already indexed, it may take some time before Google removes the indexation of the second address. You may also try using the `Google Search Console <https://search.google.com/search-console>`_ to fix this."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:360
msgid "If you have multiple websites and companies on your database, make sure that you select the right :guilabel:`Company` in the website settings, next to the :guilabel:`Domain` settings. Doing so indicates Odoo which URL to use as the :ref:`base URL <domain-name/web-base-url>` according to the company in use."
msgstr ""
#: ../../content/administration/maintain/domain_names.rst:366
msgid ":doc:`/applications/general/email_communication/email_servers`"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:6
msgid "Switch from Community to Enterprise"
msgstr ""
#: ../../content/administration/maintain/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/maintain/enterprise.rst:12
#: ../../content/administration/maintain/enterprise.rst:31
#: ../../content/administration/maintain/enterprise.rst:63
#: ../../content/administration/maintain/enterprise.rst:80
msgid "Backup your community database"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:17
#: ../../content/administration/maintain/enterprise.rst:62
msgid "Shutdown your server"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:19
msgid "Install the web_enterprise module"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:21
msgid "Restart your server"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:23
msgid "Enter your Odoo Enterprise Subscription code"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:29
msgid "On Linux, using an installer"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:33
msgid "Stop the odoo service"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:39
msgid "Install the enterprise .deb (it should install over the community package)"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:45
msgid "Update your database to the enterprise packages using"
msgstr ""
#: ../../content/administration/maintain/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/maintain/enterprise.rst:57
msgid "On Linux, using the source code"
msgstr ""
#: ../../content/administration/maintain/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/maintain/enterprise.rst:64
msgid "Update the ``--addons-path`` parameter of your launch command (see :doc:`../install/source`)"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:65
msgid "Install the web_enterprise module by using"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:71
msgid "Depending on the size of your database, this may take some time."
msgstr ""
#: ../../content/administration/maintain/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/maintain/enterprise.rst:78
msgid "On Windows"
msgstr ""
#: ../../content/administration/maintain/enterprise.rst:82
msgid "Uninstall Odoo Community (using the Uninstall executable in the installation folder) - PostgreSQL will remain installed"
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/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/maintain/google_oauth.rst:3
msgid "Connect Gmail to Odoo using Google OAuth"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:5
msgid "Odoo is compatible with Google's OAuth for Gmail. In order to send secure emails from a custom domain, all that is required is to configure a few settings on Google's *Workspace* platform, as well as on the back end of the Odoo database. This configuration works by using either a personal email address or an address created by a custom domain."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:11
msgid "For more information, visit `Google's documentation <https://support.google.com/cloud/answer/6158849>`_ on setting up OAuth."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:15
msgid ":doc:`/applications/general/auth/google`"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:16
msgid ":doc:`/applications/productivity/calendar/google`"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:19
msgid "Setup in Google"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:22
msgid "Create a new project"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:24
msgid "To get started, go to the `Google API Console <https://console.developers.google.com>`_. Log in with your *Google Workspace* account if you have one, otherwise log in with your personal Gmail account (this should match the email address you want to configure in Odoo)."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:28
msgid "After that, click on :guilabel:`Create Project`, located on the far right of the :guilabel:`OAuth consent screen`. If a project has already been created in this account, then the :guilabel:`New Project` option will be located on the top right under the :guilabel:`Select a project` drop-down menu."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:33
msgid "On the :menuselection:`New Project` screen, rename the :guilabel:`Project name` to `Odoo` and browse for the :guilabel:`Location`. Set the :guilabel:`Location` as the *Google Workspace organization*. If you are using a personal Gmail account, then leave the :guilabel:`Location` as :guilabel:`No Organization`."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:-1
msgid "Project Name and Location for Google OAuth."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:42
msgid "Click on :guilabel:`Create` to finish this step."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:45
msgid "OAuth consent screen"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:47
msgid "If the page doesn't redirect to the :menuselection:`User Type` options, click on :guilabel:`OAuth consent screen` in the left menu."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:50
msgid "Under :guilabel:`User Type` options, select the appropriate :guilabel:`User Type`, and then click on :guilabel:`Create` again, which will finally navigate to the :menuselection:`Edit app registration` page."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:55
msgid "*Personal* Gmail Accounts are only allowed to be **External** User Type, which means Google may require an approval, or for *Scopes* to be added on. However, using a *Google WorkSpace* account allows for **Internal** User Type to be used."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:59
msgid "Note, as well, that while the API connection is in the *External* testing mode, then no approval is necessary from Google. User limits in this testing mode is set to 100 users."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:63
msgid "Edit app registration"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:65
msgid "Next we will configure the app registration of the project."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:67
msgid "On the :guilabel:`OAuth consent screen` step, under the :guilabel:`App information` section, enter `Odoo` in the :guilabel:`App name` field. Select the organization's email address under the :guilabel:`User support` email field."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:71
msgid "Next, under :menuselection:`App Domain --> Authorized domains`, click on :guilabel:`Add Domain` and enter `odoo.com`."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:74
msgid "After that, under the :guilabel:`Developer contact information` section, enter the organization's email address. Google uses this email address to notify the organization about any changes to your project."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:78
msgid "Next, click on the :guilabel:`Save and Continue` button. Then, skip the :menuselection:`Scopes` page by scrolling to the bottom and clicking on :guilabel:`Save and Continue`."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:81
msgid "If continuing in testing mode (External), add the email addresses being configured under the :guilabel:`Test users` step, by clicking on :guilabel:`Add Users`, and then the :guilabel:`Save and Continue` button. A summary of the app registration appears."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:85
msgid "Finally, scroll to the bottom and click on :guilabel:`Back to Dashboard` to finish setting up the project."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:89
msgid "Create Credentials"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:91
msgid "Now that the project is set up, credentials should be created, which includes the *Client ID* and *Client Secret*. First, click on :guilabel:`Credentials` in the left sidebar menu."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:94
msgid "Then, click on :guilabel:`Create Credentials` in the top menu and select :guilabel:`OAuth client ID` from the dropdown menu."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:97
msgid "Under :guilabel:`Application Type`, select :guilabel:`Web Application` from the dropdown menu."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:98
msgid "In the :guilabel:`Name` field, enter `Odoo`."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:99
msgid "Under the :guilabel:`Authorized redirect URIs` label, click the button :guilabel:`ADD URI`, and then input `https://yourdbname.odoo.com/google_gmail/confirm` in the :guilabel:`URIs 1` field. Be sure to replace the *yourdbname* part of the URL with the actual Odoo database name."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:102
msgid "Next, click on :guilabel:`Create` to generate an OAuth :guilabel:`Client ID` and :guilabel:`Client Secret`. Finally, copy each generated value for later use when configuring in Odoo, and then navigate to the Odoo database."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:-1
msgid "Client ID and Client Secret for Google OAuth."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:114
msgid "Enter Google Credentials"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:116
msgid "First, open Odoo and navigate to the :guilabel:`Apps` module. Then, remove the :guilabel:`Apps` filter from the search bar and type in `Google`. Install the module called :guilabel:`Google Gmail`."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:120
msgid "Next, navigate to :menuselection:`Settings --> General Settings`, and under the :guilabel:`Discuss` section, ensure that the checkbox for :guilabel:`Custom Email Servers` or :guilabel:`External Email Servers` is checked. This populates a new option for :guilabel:`Gmail Credentials` or :guilabel:`Use a Gmail Sever`. Then, copy and paste the respective values into the :guilabel:`Client ID` and :guilabel:`Client Secret` fields and :guilabel:`Save` the settings."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:129
msgid "To configure the external Gmail account, return to the top of the :guilabel:`Custom Email Servers` setting and then click the :guilabel:`Outgoing Email Servers` link."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:-1
msgid "Configure Outgoing Email Servers in Odoo."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:136
msgid "Then, click on :guilabel:`New` or :guilabel:`Create` to create a new email server, and fill in the :guilabel:`Name`, :guilabel:`Description`, and the email :guilabel:`Username` (if required)."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:139
msgid "Next, click on :guilabel:`Gmail OAuth Authentication` or :guilabel:`Gmail` (under the :guilabel:`Authenticate with` or :guilabel:`Connection` section). Finally, click on :guilabel:`Connect your Gmail Account`."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:143
msgid "A new window labeled :guilabel:`Google` opens to complete the authorization process. Select the appropriate email address that is being configured in Odoo."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:146
msgid "If the email address is a personal account, then an extra step pops up, so click :guilabel:`Continue` to allow the verification and connect the Gmail account to Odoo."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:149
msgid "Then, allow Odoo to access the Google account by clicking on :guilabel:`Continue` or :guilabel:`Allow`. After that, the page navigates back to the newly configured outgoing email server in Odoo. The configuration automatically loads the token in Odoo, and a tag stating :guilabel:`Gmail Token Valid` appears in green."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:158
msgid "Finally, :guilabel:`Test the Connection`. A confirmation message should appear. The Odoo database can now send safe, secure emails through Google using OAuth authentication."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:162
msgid "Google OAuth FAQ"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:165
msgid "Production VS Testing Publishing Status"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:167
msgid "Choosing :guilabel:`Production` as the :guilabel:`Publishing Status` (instead of :guilabel:`Testing`) will display the following warning message:"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:-1
msgid "OAuth is Limited to 100 Sensitive Scope Logins."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:174
msgid "To correct this warning, navigate to the `Google API Platform <https://console.cloud.google.com/apis/credentials/consent>`_. If the :guilabel:`Publishing status` is :guilabel:`In Production`, click :guilabel:`Back to Testing` to correct the issue."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:179
msgid "No Test Users Added"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:181
msgid "If no test users are added to the OAuth consent screen, then a 403 access denied error will populate."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:-1
msgid "403 Access Denied Error."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:188
msgid "To correct this error, return to the :guilabel:`OAuth consent screen` under :guilabel:`APIs & Services` and add test user(s) to the app. Add the email that you are configuring in Odoo."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:192
msgid "Gmail Module not updated"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:194
msgid "If the *Google Gmail* module in Odoo has not been updated to the latest version, then a :guilabel:`Forbidden` error message populates."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:-1
msgid "Forbidden you don't have the permission to access the requested resource."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:201
msgid "To correct this error, go to the :menuselection:`Apps` module and clear out the search terms. Then, search for `Gmail` or `Google` and upgrade the :guilabel:`Google Gmail` module. Finally, click on the three dots on the upper right of the module and select :guilabel:`Upgrade`."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:206
msgid "Application Type"
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:208
msgid "When creating the credentials (OAuth *Client ID* and *Client Secret*), if :guilabel:`Desktop App` is selected for the :guilabel:`Application Type`, an :guilabel:`Authorization Error` appears."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:-1
msgid "Error 400 Redirect URI Mismatch."
msgstr ""
#: ../../content/administration/maintain/google_oauth.rst:215
msgid "To correct this error, delete the credentials already created and create new credentials, selecting :guilabel:`Web Application` for the :guilabel:`Application Type`. Then, under :guilabel:`Authorized redirect URIs`, click :guilabel:`ADD URI` and type: `https://yourdbname.odoo.com/google_gmail/confirm` in the field, being sure to replace *yourdbname* in the URL with the Odoo database name."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:3
msgid "Change hosting solution"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:5
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/maintain/hosting_changes.rst:9
msgid "Transferring an on-premise database"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:12
#: ../../content/administration/maintain/hosting_changes.rst:80
msgid "To Odoo Online"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:15
#: ../../content/administration/maintain/hosting_changes.rst:83
msgid "Odoo Online is *not* compatible with **non-standard apps**."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:16
msgid "The database's current version must be :doc:`supported <supported_versions>`."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:18
msgid "Create a :ref:`duplicate <duplicate_premise>` of the database."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:19
msgid "In this duplicate, uninstall all **non-standard apps**."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:20
msgid "Use the database manager to grab a *dump with filestore*."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:21
msgid "`Submit a support ticket <https://www.odoo.com/help>`_ including the following:"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:23
#: ../../content/administration/maintain/hosting_changes.rst:88
msgid "your **subscription number**,"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:24
msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`), and"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:25
msgid "the **dump** as an attachment or as a link to the file (required for 60 MB+ files)."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:27
#: ../../content/administration/maintain/hosting_changes.rst:95
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/maintain/hosting_changes.rst:31
#: ../../content/administration/maintain/hosting_changes.rst:99
msgid "If you have time constraints, `submit a support ticket <https://www.odoo.com/help>`_ as soon as possible to schedule the transfer."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:35
#: ../../content/administration/maintain/hosting_changes.rst:67
msgid "To Odoo.sh"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:37
#: ../../content/administration/maintain/hosting_changes.rst:73
msgid "Follow the instructions found in :ref:`the Import your database section <odoo_sh_import_your_database>` of the Odoo.sh *Create your project* documentation."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:41
msgid "Transferring an Odoo Online database"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:44
msgid "Odoo Online's :ref:`intermediary versions <supported_versions>` cannot be hosted on-premise as that type of hosting does not support those versions. 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/maintain/hosting_changes.rst:50
msgid "Transferring an online database running on Odoo 16.3 would require first upgrading it to Odoo 17.0."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:54
msgid "Click the gear icon (:guilabel:`⚙`) 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/maintain/hosting_changes.rst:58
#: ../../content/administration/maintain/hosting_changes.rst:108
msgid "To on-premise"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:60
#: ../../content/administration/maintain/hosting_changes.rst:69
msgid "Sign in to `the Odoo Online database manager <https://www.odoo.com/my/databases/>`_ and click the gear icon (:guilabel:`⚙`) next to the database name to :guilabel:`Download` a backup. If the download fails due to the file being too large, `contact Odoo support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:64
#: ../../content/administration/maintain/hosting_changes.rst:111
msgid "Restore the database from the database manager on your local server using the backup."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:77
msgid "Transferring an Odoo.sh database"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:85
msgid "Uninstall all **non-standard apps** in a staging build before doing it in the production build."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:86
msgid "`Create a support ticket <https://www.odoo.com/help>`_ including the following:"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:89
msgid "the **URL** you want to use for the database (e.g., `company.odoo.com`),"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:90
msgid "which **branch** should be migrated,"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:91
msgid "in which **region** you want the database to be hosted (Americas, Europe, or Asia),"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:92
msgid "which user(s) will be the **administrator(s)**, and"
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:93
msgid "**when** (and in which timezone) you want the database to be up and running."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:101
msgid "Select the **region** closest to most of your users to reduce latency."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:102
msgid "Future **administrator(s)** must have an Odoo.com account."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:103
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/maintain/hosting_changes.rst:105
msgid "Databases are **not reachable** during their migration."
msgstr ""
#: ../../content/administration/maintain/hosting_changes.rst:110
msgid "Download a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:3
msgid "Mailjet API"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:5
msgid "Odoo is compatible with Mailjet's :abbr:`API (Application Programming Interface)` for mass mailing. Set up a dedicated mass mailing server through Mailjet by configuring settings in the Mailjet account and the Odoo database. In some circumstances, settings need to be configured on the custom domain's :abbr:`DNS (Domain Name System)` settings as well."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:11
msgid "Set up in Mailjet"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:14
msgid "Create API credentials"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:16
msgid "To get started, sign in to the `Mailjet Account Information <https://app.mailjet.com/account>`_ page. Next, navigate to the :guilabel:`Senders & Domains` section and click on :guilabel:`SMTP and SEND API Settings`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:-1
msgid "SMTP and Send API Settings link in the Senders & Domains section of Mailjet."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:24
msgid "Then, copy the :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings onto a notepad. They can be found under the :guilabel:`Configuration (SMTP only)` section. The :abbr:`SMTP (Simple Mail Transfer Protocol)` configuration settings include the server address, the security option needed (Use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)`), and the port number. The settings are needed to configure Mailjet in Odoo, which is covered in the :ref:`last section <maintain/mailjet-api/odoo-setup>`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:32
msgid "`Mailjet: How can I configure my SMTP parameters? <https://documentation.mailjet.com/hc/articles/360043229473>`_"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:36
msgid "Odoo blocks `port 25` on Odoo Online and Odoo.sh databases. :ref:`See reference here <email_servers/restriction>`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:-1
msgid "SMTP configuration from Mailjet."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:43
msgid "Next, click on the button labeled :guilabel:`Retrieve your API credentials` to retrieve the Mailjet API credentials."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:46
msgid "Then, click on the eye icon to reveal the :guilabel:`API key`. Copy this key to a notepad, as this serves as the :guilabel:`Username` in the Odoo configuration. Next, click on the :guilabel:`Generate Secret Key` button to generate the :guilabel:`Secret Key`. Copy this key to a notepad, as this serves as the :guilabel:`Password` in the Odoo configuration."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:52
msgid "Add verified sender address(es)"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:54
msgid "The next step is to add a sender address or a domain to the Mailjet account settings so that the email address or domain is approved to send emails using Mailjet's servers. First, navigate to the `Mailjet Account Information <https://app.mailjet.com/account>`_ page. Next, click on the :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:-1
msgid "Add a sender domain or address in the Mailjet interface."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:63
msgid "Determine if a sender's email address or the entire domain needs to be added to the Mailjet settings. It may be easier to configure the domain as a whole if :abbr:`DNS (Domain Name System)` access is available. Jump to the :ref:`Add a domain <maintain/mailjet-api/add-domain>` section for steps on adding the domain."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:69
msgid "Either all email addresses of the Odoo database users who are sending emails using Mailjet's servers need to be configured or the domain(s) of the users' email addresses can be configured."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:72
msgid "By default, the email address originally set up in the Mailjet account is added as a trusted sender. To add another email address, click on the button labeled :guilabel:`Add a sender address`. Then, add the email address that is configured to send from the custom domain."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:76
msgid "At minimum the following email addresses should be set up in the provider and verified in Mailjet:"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:78
msgid "notifications\\@yourdomain.com"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:79
msgid "bounce\\@yourdomain.com"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:80
msgid "catchall\\@yourdomain.com"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:83
msgid "Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use the :guilabel:`mail.catchall.domain` system parameter."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:86
msgid "After that, fill out the :guilabel:`Email Information` form, making sure to select the appropriate email type: transactional email or mass emails. After completing the form, an activation email is sent to the email address and the trusted sender can be activated."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:90
msgid "It is recommended to set up the :abbr:`SPF (Sender Policy Framework)`/:abbr:`DKIM (DomainKeys Identified Mail)`/:abbr:`DMARC (Domain-based Message Authentication, Reporting, and Conformance)` settings on the domain of the sender."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:95
#: ../../content/administration/maintain/mailjet_api.rst:162
msgid "`Mailjet's SPF/DKIM/DMARC documentation <https://documentation.mailjet.com/hc/articles/ 360042412734-Authenticating-Domains-with-SPF-DKIM>`_"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:99
msgid "If the database is not using a custom domain, then in order to verify the sender's address, a temporary alias (of the three email addresses mentioned above) should be set up in Odoo CRM to create a lead. Then, the database is able to receive the verification email and verify the accounts."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:107
msgid "Add a domain"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:109
msgid "By adding an entire domain to the Mailjet account, all the sender addresses related to that domain are automatically validated for sending emails using Mailjet servers. First, navigate to the `Mailjet Account Information <https://app.mailjet.com/account>`_ page. Next, click on :guilabel:`Add a Sender Domain or Address` link under the :guilabel:`Senders & Domains` section. Then, click on :guilabel:`Add domain` to add the custom domain."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:116
msgid "The domain needs to be added to the Mailjet account and then validated through the :abbr:`DNS (Domain Name System)`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:119
msgid "After that, fill out the :guilabel:`Add a new Domain` page on Mailjet and click :guilabel:`Continue`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:122
msgid "After adding the domain, a validation page will populate. Unless the Odoo database is on-premise (in which case, choose :guilabel:`Option 1`), choose :guilabel:`Option 2: Create a DNS Record`. Copy the TXT record information to a notepad and then navigate to the domain's :abbr:`DNS (Domain Name System)` provider to complete validation."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:-1
msgid "The TXT record information to input on the domain's DNS."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:132
msgid "Setup in the domain's DNS"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:134
msgid "After getting the TXT record information from the Mailjet account, add a TXT record to the domain's :abbr:`DNS (Domain Name System)`. This process varies depending on the :abbr:`DNS (Domain Name System)` provider. Consult the provider for specific configuration processes. The TXT record information consists of the :guilabel:`Host` and :guilabel:`Value`. Paste these into the corresponding fields in the TXT record."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:141
msgid "Return to Mailjet account information"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:143
msgid "After adding the TXT record to the domain's :abbr:`DNS (Domain Name System)`, navigate back to the Mailjet account. Then, navigate to :menuselection:`Account Information --> Add a Sender Domain or Address`, click the gear icon next to :guilabel:`Domain`, and select :guilabel:`Validate`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:147
msgid "This action can also be done by going to the `Sender domains & addresses <https://app.mailjet.com/ account/sender>`_ page on the Mailjet account information and clicking on :guilabel:`Manage`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:150
msgid "Next, click :guilabel:`Check Now` to validate the TXT record that was added on the domain. A success screen will appear if the domain is configured correctly."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:-1
msgid "Check DNS record in Mailjet."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:157
msgid "After successfully setting up the domain, there is an option to :guilabel:`Authenticate this domain (SPF/DKIM)`. This button populates :abbr:`SPF (Sender Policy Framework)` & :abbr:`DKIM (DomainKeys Identified Mail) records to input into the :abbr:`DNS (Domain Name System)` provider."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:-1
msgid "Authenticate the domain with SPF/DKIM records in Mailjet."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:172
msgid "Set up in Odoo"
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:174
msgid "To complete the setup, navigate to the Odoo database and go to the :guilabel:`Settings`. With :ref:`developer-mode` turned on, go to the :menuselection:`Technical Menu --> Email --> Outgoing Mail Servers`. Then, create a new outgoing server configuration by clicking on the :guilabel:`Create` button."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:179
msgid "Next, input the `SMTP server` (in-v3.mailjet.com), `port number` (587 or 465), and `Security (SSL/TLS)` that was copied earlier from the Mailjet account. They can also be found `here <https://app.mailjet.com/account/setup>`_. It is recommended to use :abbr:`SSL (Secure Sockets Layer)`/:abbr:`TLS (Transport Layer Security)` even though Mailjet may not require it."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:184
msgid "For the :guilabel:`Username`, input the :guilabel:`API KEY`. For the :guilabel:`Password`, input the :guilabel:`SECRET KEY` that was copied from the Mailjet account to the notepad earlier. These settings can be found on :menuselection:`Mailjet --> Account Settings --> SMTP and SEND API Settings`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:189
msgid "Then, if the Mailjet server is used for mass emailing, set the :guilabel:`Priority` value higher than that of any transactional email server(s). Finally, save the settings and :guilabel:`Test the Connection`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:-1
msgid "Odoo outgoing email server settings."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:198
msgid "In order for the notifications feature to work using Mailjet, there are three settings that need to be set in Odoo."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:201
msgid "The :guilabel:`From Filter` needs to be set on the server configuration. It is recommended to set it as a domain and not a full email address. It should match the domain in the two proceeding steps. More information can be referenced :ref:`here <email_communication/from_filter>`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:205
msgid "The :guilabel:`mail.default.from` system parameter must have the value `notifications\\@yourdomain.com`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:207
msgid "The :guilabel:`mail.default.from_filter` system parameter must have the value `yourdomain.com`. Replace `yourdomain` with the custom domain for the Odoo database. If there isn't one, then use the :guilabel:`mail.catchall.domain` system parameter."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:211
msgid "For more information see :ref:`Using a default email address <email_communication/default>`."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:213
msgid "The :guilabel:`System Parameters` can be accessed by activating :doc:`../../applications/general/developer_mode` in the :menuselection:`Settings --> Technical --> Parameters --> System Parameters` menu."
msgstr ""
#: ../../content/administration/maintain/mailjet_api.rst:217
msgid "Once the setup is complete, the Odoo database is ready to use the Mailjet email server for mass mailing or transactional emails!"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:3
msgid "Odoo Online database management"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:5
msgid "To manage a database, go to the `database manager <https://www.odoo.com/my/databases>`_ and sign in as the database administrator."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:8
msgid "All the main database management options are available by clicking the database name, except the upgrade option, which can be accessed by clicking the **arrow in a circle** icon next to the database name. It is only displayed if an upgrade is available."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:-1
msgid "Accessing the database management options"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:15
msgid ":ref:`odoo_online/upgrade`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:16
msgid ":ref:`odoo_online/duplicate`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:17
msgid ":ref:`odoo_online/rename`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:18
msgid ":ref:`odoo_online/download`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:19
msgid ":ref:`odoo_online/domains`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:20
msgid ":ref:`odoo_online/tags`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:21
msgid ":ref:`odoo_online/delete`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:22
msgid ":ref:`odoo_online/contact-support`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:23
msgid ":ref:`odoo_online/users`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:28
#: ../../content/administration/odoo_sh/getting_started/branches.rst:293
#: ../../content/administration/odoo_sh/getting_started/settings.rst:77
#: ../../content/administration/odoo_sh/getting_started/settings.rst:113
#: ../../content/administration/upgrade.rst:3
msgid "Upgrade"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:30
msgid "Trigger a database upgrade."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:33
msgid "For more information about the upgrade process, check out the :ref:`Odoo Online upgrade documentation <upgrade/request-test-database>`."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:39
msgid "Duplicate"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:41
msgid "Create an exact copy of the database, which can be used to perform testing without compromising daily operations."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:45
msgid "By checking :guilabel:`For testing purposes`, all external actions (emails, payments, delivery orders, etc.) are disabled by default on the duplicated database."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:47
msgid "Duplicated databases expire automatically after 15 days."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:52
msgid "Rename"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:54
msgid "Rename the database and its URL."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:59
msgid "Download"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:61
msgid "Download a ZIP file containing a backup of the database."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:64
msgid "Databases are backed up daily as per the `Odoo Cloud Hosting SLA <https://www.odoo.com/cloud-sla>`_."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:72
msgid "Use a custom :doc:`domain name <domain_names>` to access the database via another URL."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:75
msgid "You can :ref:`register a domain name for free <domain-name/odoo-register>`."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:80
msgid "Tags"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:82
msgid "Add tags to easily identify and sort your databases."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:85
msgid "You can search for tags in the search bar."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:90
#: ../../content/administration/odoo_sh/getting_started/branches.rst:550
msgid "Delete"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:92
msgid "Delete a database instantly."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:95
msgid "Deleting a database means that all data is permanently lost. The deletion is instant and applies to all users. It is recommended to create a backup of the database before deleting it."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:98
msgid "Carefully read the warning message and only proceed if the implications of deleting a database are fully understood."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:-1
msgid "The warning message displayed before deleting a database"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:105
msgid "Only an administrator can delete a database."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:106
msgid "The database name is immediately made available to anyone."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:107
msgid "Deleting a database if it has expired or is linked to a subscription is impossible. In that case, contact `Odoo Support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:113
msgid "Contact us"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:115
msgid "Access the `Odoo.com support page <https://www.odoo.com/help>`_ with the database's details already pre-filled."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:121
msgid "Invite / remove users"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:123
msgid "To invite users, fill out the new user's email address and click :guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:-1
msgid "Inviting a user on a database"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:129
msgid "To remove users, select them and click :guilabel:`Remove`."
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:132
msgid ":doc:`/applications/general/users/manage_users`"
msgstr ""
#: ../../content/administration/maintain/odoo_online.rst:133
msgid ":doc:`/applications/general/users/odoo_account`"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:3
msgid "On-premise database management"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:6
msgid "Register a database"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:8
msgid "To register your database, you just need to enter your Subscription Code in the banner in the App Switcher. Make sure you do not add extra spaces before or after your subscription code. If the registration is successful, it will turn green and will provide you with the Expiration Date of your freshly-registered database. You can check this Expiration Date in the About menu (Odoo 9) or in the Settings Dashboard (Odoo 10)."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:16
msgid "Registration Error Message"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:18
msgid "If you are unable to register your database, you will likely encounter this message:"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:-1
msgid "Something went wrong while registering your database, you can try again or contact Odoo\n"
"Help"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:27
#: ../../content/administration/maintain/on_premise.rst:100
#: ../../content/administration/maintain/on_premise.rst:127
msgid "Solutions"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:29
msgid "Do you have a valid Enterprise subscription?"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:31
msgid "Check if your subscription details get the tag \"In Progress\" on your `Odoo Account <https://accounts.odoo.com/my/subscription>`__ or with your Account Manager"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:35
msgid "Have you already linked a database with your subscription reference?"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:37
msgid "You can link only one database per subscription. (Need a test or a development database? `Find a partner <https://www.odoo.com/partners>`__)"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:41
msgid "You can unlink the old database yourself on your `Odoo Contract <https://accounts.odoo.com/my/subscription>`__ with the button \"Unlink database\""
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:47
msgid "A confirmation message will appear; make sure this is the correct database as it will be deactivated shortly:"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:53
msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:55
#: ../../content/administration/maintain/on_premise.rst:159
msgid "From July 2016 onward, Odoo 9 now automatically change the uuid of a duplicated database; a manual operation is no longer required."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:58
msgid "If it's not the case, you may have multiple databases sharing the same UUID. Please check on your `Odoo Contract <https://accounts.odoo.com/my/subscription>`__, a short message will appear specifying which database is problematic:"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:66
msgid "In this case, you need to change the UUID on your test databases to solve this issue. You will find more information about this in :ref:`this section <duplicate_premise>`."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:69
msgid "For your information, we identify database with UUID. Therefore, each database should have a distinct UUID to ensure that registration and invoicing proceed effortlessly for your and for us."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:73
msgid "Check your network and firewall settings"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:75
msgid "The Update notification must be able to reach Odoo's subscription validation servers. In other words, make sure that the Odoo server is able to open outgoing connections towards:"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:79
msgid "services.odoo.com on port 443 (or 80)"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:80
msgid "services.openerp.com on port 443 (or 80) for older deployments"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:82
msgid "Once you activated your database, you must keep these ports open, as the Update notification runs once a week."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:86
msgid "Error message due to too many users"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:88
msgid "If you have more users in your local database than provisionned in your Odoo Enterprise subscription, you may encounter this message:"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:-1
msgid "This database will expire in X days, you have more users than your subscription allows"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:96
msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:102
msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:104
msgid "**Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_ and **Reject** the upsell quotation."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:107
msgid "Once your database has the correct number of users, the expiration message will disappear automatically after a few days, when the next verification occurs. We understand that it can be a bit frightening to see the countdown, so you can :ref:`force an Update Notification <force_ping>` to make the message disappear right away."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:114
msgid "Database expired error message"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:116
msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:-1
msgid "This database has expired."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:123
msgid "This **blocking** message appears after a non-blocking message that lasts 30 days. If you fail to take action before the end of the countdown, the database is expired."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:131
msgid "Renew your subscription: follow the link and renew your subscription - note that"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:130
msgid "if you wish to pay by Wire Transfer, your subscription will effectively be renewed only when the payment arrives, which can take a few days. Credit card payments are processed immediately."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:133
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:135
msgid "None of those solutions worked for you? Please contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:143
msgid "Duplicate a database"
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:145
msgid "You can duplicate your database by accessing the database manager on your server (<odoo-server>/web/database/manager). In this page, you can easily duplicate your database (among other things)."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:152
msgid "When you duplicate a local database, it is **strongly** advised to change the duplicated database's uuid (Unniversally Unique Identifier), since this uuid is how your database identifies itself with our servers. Having two databases with the same uuid could result in invoicing problems or registration problems down the line."
msgstr ""
#: ../../content/administration/maintain/on_premise.rst:162
msgid "The database uuid is currently accessible from the menu :menuselection:`Settings --> Technical --> System Parameters`, we advise you to use a `uuid generator <https://www.uuidtools.com>`_ or to use the unix command ``uuidgen`` to generate a new uuid. You can then simply replace it like any other record by clicking on it and using the edit button."
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:7
msgid "Supported versions"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:9
msgid "Odoo provides support and bug fixing **for the 3 last major versions** of Odoo."
msgstr ""
#: ../../content/administration/maintain/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/maintain/supported_versions.rst:16
msgid "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` them regularly."
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:17
msgid "Online versions are *not* released for Odoo.sh and On-Premise installations."
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:18
msgid "Online versions are listed below as *SaaS*."
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:20
msgid "This matrix shows the support status of every version."
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:22
msgid "**Major releases are in bold type.**"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:31
msgid "On-Premise"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:32
msgid "Release date"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:33
msgid "End of support"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:34
msgid "**Odoo 17.0**"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:35
#: ../../content/administration/maintain/supported_versions.rst:36
#: ../../content/administration/maintain/supported_versions.rst:37
#: ../../content/administration/maintain/supported_versions.rst:41
#: ../../content/administration/maintain/supported_versions.rst:65
#: ../../content/administration/maintain/supported_versions.rst:66
#: ../../content/administration/maintain/supported_versions.rst:67
#: ../../content/administration/maintain/supported_versions.rst:83
#: ../../content/administration/maintain/supported_versions.rst:84
#: ../../content/administration/maintain/supported_versions.rst:85
#: ../../content/administration/odoo_sh/getting_started/settings.rst:58
#: ../../content/administration/odoo_sh/getting_started/settings.rst:59
#: ../../content/administration/odoo_sh/getting_started/settings.rst:62
#: ../../content/administration/odoo_sh/getting_started/settings.rst:63
#: ../../content/administration/odoo_sh/getting_started/settings.rst:66
#: ../../content/administration/odoo_sh/getting_started/settings.rst:67
#: ../../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:78
#: ../../content/administration/odoo_sh/getting_started/settings.rst:79
#: ../../content/administration/odoo_sh/getting_started/settings.rst:82
#: ../../content/administration/odoo_sh/getting_started/settings.rst:83
#: ../../content/administration/odoo_sh/getting_started/settings.rst:86
#: ../../content/administration/odoo_sh/getting_started/settings.rst:87
#: ../../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:99
#: ../../content/administration/odoo_sh/getting_started/settings.rst:103
#: ../../content/administration/odoo_sh/getting_started/settings.rst:107
#: ../../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:119
#: ../../content/administration/odoo_sh/getting_started/settings.rst:122
#: ../../content/administration/odoo_sh/getting_started/settings.rst:123
#: ../../content/administration/odoo_sh/getting_started/settings.rst:127
msgid "|green|"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:38
#: ../../content/administration/maintain/supported_versions.rst:93
msgid "November 2023"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:39
msgid "November 2026 (planned)"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:40
msgid "Odoo saas~16.4"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:42
#: ../../content/administration/maintain/supported_versions.rst:43
#: ../../content/administration/maintain/supported_versions.rst:48
#: ../../content/administration/maintain/supported_versions.rst:49
#: ../../content/administration/maintain/supported_versions.rst:54
#: ../../content/administration/maintain/supported_versions.rst:55
#: ../../content/administration/maintain/supported_versions.rst:60
#: ../../content/administration/maintain/supported_versions.rst:61
#: ../../content/administration/maintain/supported_versions.rst:72
#: ../../content/administration/maintain/supported_versions.rst:73
#: ../../content/administration/maintain/supported_versions.rst:78
#: ../../content/administration/maintain/supported_versions.rst:79
msgid "N/A"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:44
msgid "August 2023"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:46
msgid "Odoo saas~16.3"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:47
#: ../../content/administration/maintain/supported_versions.rst:53
#: ../../content/administration/maintain/supported_versions.rst:59
#: ../../content/administration/maintain/supported_versions.rst:71
#: ../../content/administration/maintain/supported_versions.rst:77
#: ../../content/administration/maintain/supported_versions.rst:89
#: ../../content/administration/maintain/supported_versions.rst:90
#: ../../content/administration/maintain/supported_versions.rst:91
#: ../../content/administration/maintain/supported_versions.rst:95
#: ../../content/administration/maintain/supported_versions.rst:96
#: ../../content/administration/maintain/supported_versions.rst:97
#: ../../content/administration/maintain/supported_versions.rst:101
#: ../../content/administration/maintain/supported_versions.rst:102
#: ../../content/administration/maintain/supported_versions.rst:103
msgid "|red|"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:50
msgid "June 2023"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:52
msgid "Odoo saas~16.2"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:56
msgid "March 2023"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:58
msgid "Odoo saas~16.1"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:62
msgid "February 2023"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:64
msgid "**Odoo 16.0**"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:68
#: ../../content/administration/maintain/supported_versions.rst:99
msgid "October 2022"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:69
msgid "November 2025 (planned)"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:70
msgid "Odoo saas~15.2"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:74
msgid "March 2022"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:75
msgid "January 2023"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:76
msgid "Odoo saas~15.1"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:80
msgid "February 2022"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:81
msgid "July 2022"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:82
msgid "**Odoo 15.0**"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:86
msgid "October 2021"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:87
msgid "November 2024 (planned)"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:88
msgid "**Odoo 14.0**"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:92
msgid "October 2020"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:94
msgid "**Odoo 13.0**"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:98
msgid "October 2019"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:100
msgid "Older versions"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:104
msgid "Before 2019"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:105
msgid "Before 2022"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:107
msgid "Legend"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:109
msgid "|green| Supported version"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:111
msgid "|red| End-of-support"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:113
msgid "N/A Never released for this platform"
msgstr ""
#: ../../content/administration/maintain/supported_versions.rst:116
msgid "Even though we don't support older versions, you can always `upgrade from any version <https://upgrade.odoo.com/>`_."
msgstr ""
#: ../../content/administration/maintain/update.rst:6
msgid "Bugfix updates"
msgstr ""
#: ../../content/administration/maintain/update.rst:9
msgid "Introduction"
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/update.rst:17
msgid "The terminology surrounding software updates is often confusing, so here are some preliminary definitions:"
msgstr ""
#: ../../content/administration/maintain/update.rst:25
msgid "Updating (an Odoo installation)"
msgstr ""
#: ../../content/administration/maintain/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/maintain/update.rst:35
msgid "Upgrading (an Odoo database)"
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/update.rst:43
msgid "In a nutshell"
msgstr ""
#: ../../content/administration/maintain/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/maintain/update.rst:49
msgid "The main reference for updating is logically our :doc:`installation guide <../install>`, which explains the common installation methods."
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/update.rst:64
msgid "Step 1: Download an updated Odoo version"
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/update.rst:73
msgid "Downloading an updated version is not necessary if you installed via Github (see below)"
msgstr ""
#: ../../content/administration/maintain/update.rst:77
msgid "Step 2: Make a backup of your database"
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/update.rst:89
msgid "Step 3: Install the updated version"
msgstr ""
#: ../../content/administration/maintain/update.rst:91
msgid "Choose the method that matches your current installation:"
msgstr ""
#: ../../content/administration/maintain/update.rst:95
msgid "Packaged Installers"
msgstr ""
#: ../../content/administration/maintain/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/maintain/update.rst:106
msgid "Source Install (Tarball)"
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/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/maintain/update.rst:126
msgid "Source Install (Github)"
msgstr ""
#: ../../content/administration/maintain/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/maintain/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/maintain/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/maintain/update.rst:145
msgid "Finally, restart the Odoo service or reboot the machine, and you should be done."
msgstr ""
#: ../../content/administration/maintain/update.rst:149
msgid "Docker"
msgstr ""
#: ../../content/administration/maintain/update.rst:151
msgid "Please refer to our `Docker image documentation <https://hub.docker.com/_/odoo/>`_ for specific update instructions."
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/getting_started/branches.rst:6
#: ../../content/administration/odoo_sh/getting_started/builds.rst:9
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6
#: ../../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
#: ../../content/administration/odoo_sh/overview.rst:5
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/17.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 "``--without-demo=all`` prevents demo data to be loaded for all modules"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:167
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:169
msgid "More options are available and detailed in the :doc:`CLI documentation </developer/reference/cli>`."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:172
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:181
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:186
msgid "Debugging in Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:188
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:190
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:192
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:195
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:197
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:199
msgid "To do so, you have two options:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:201
msgid "temporary (only in the current build):"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:207
msgid "or"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:213
msgid "permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` file."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:216
msgid "Then edit the code where you want to trigger the debugger and add this:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:224
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:226
msgid "Save the file and then run the Odoo Shell:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:232
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/submodules.rst:6
#: ../../content/administration/odoo_sh/getting_started/settings.rst:170
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/getting_started/first_module.rst:360
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498
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/getting_started.rst:5
msgid "Get started"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:3
msgid "Branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:8
msgid "The branches view gives you an overview of the different branches your repository has."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:16
#: ../../content/administration/odoo_sh/getting_started/builds.rst:41
msgid "Stages"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:18
msgid "Odoo.sh offers three different stages for your branches: production, staging and development."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:20
msgid "You can change the stage of a branch by drag and dropping it into the stage section title."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:28
#: ../../content/administration/odoo_sh/getting_started/builds.rst:44
msgid "Production"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:30
msgid "This is the branch holding the code on which your production database runs. There can be only one production branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:33
msgid "When you push a new commit in this branch, your production server is updated with the code of the new revision and is then restarted."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:36
msgid "If your changes require the update of a module, such as a change in a form view, and you want it to be performed automatically, increase the version number of the module in its manifest (*__manifest__.py*). The platform will then take care to perform the update during which the instance will be held temporarily unavailable for maintenance reason."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:43
msgid "This method is equivalent to perform an upgrade of the module through the Apps menu, or through the :code:`-u` switch of :doc:`the command line </developer/reference/cli>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:47
msgid "In the case the changes in the commit prevent the server to restart, or if the modules update fails, the server is automatically reverted to the previous successful code revision and the database is roll-backed as it was before the update. You still have access to the log of the failed update, so you can troubleshoot it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:53
msgid "The demo data is not loaded, as it is not meant to be used in a production database. The unit tests are not performed, as it would increase the unavailability time of the production database during the updates."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:57
msgid "Partners using trial projects should be aware their production branch, along with all the staging branches, will automatically be set back to the development stage after 30 days."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:61
#: ../../content/administration/odoo_sh/getting_started/builds.rst:63
msgid "Staging"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:63
msgid "Staging branches are meant to test your new features using the production data without compromising the actual production database with test records. They will create databases that are neutralized duplicates of the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:67
msgid "The neutralization includes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:69
msgid "Disabling scheduled actions. If you want to test them, you can trigger their action 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 up resources."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:72
msgid "Disabling outgoing emails by intercepting them with a mailcatcher. An :ref:`interface to view <odoosh-gettingstarted-branches-tabs-mails>` the emails sent by your database is provided. That way, you do not have to worry about sending test emails to your contacts."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:75
msgid "Setting payment providers and shipping providers in test mode."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:76
msgid "Disabling IAP services"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:78
msgid "The latest database will be kept alive indefinitely, older ones from the same branch may get garbage collected to make room for new ones. It will be valid for 3 months, after which you will be expected to rebuild the branch. If you make configuration or view changes in these databases, make sure to document them or write them directly in the modules of the branch, using XML data files overriding the default configuration or views."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:83
msgid "The unit tests are not performed as, in Odoo, they currently rely on the demo data, which is not loaded in the production database. In the future, if Odoo supports to run the unit tests without the demo data, Odoo.sh will then consider running the tests on staging databases."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:88
#: ../../content/administration/odoo_sh/getting_started/builds.rst:81
#: ../../content/administration/odoo_sh/getting_started/settings.rst:56
msgid "Development"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:90
msgid "Development branches create new databases using the demo data to run the unit tests. The installed modules are the ones included in your branches. You can change this list of modules to install in your :ref:`project Settings <odoosh-gettingstarted-settings-modules-installation>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:94
msgid "When you push a new commit in one of these branches, a new server is started, with a database created from scratch and the new revision of the branch. The demo data is loaded, and the unit tests are performed by default. This verifies your changes do not break any of the features tested by them. If you wish, you can disable the tests or allow specific tests to be run with custom tags in the :ref:`branch's settings <odoosh-gettingstarted-branches-tabs-settings>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:101
msgid "Similar to staging branches, the emails are not sent but are intercepted by a mailcatcher and scheduled actions are not triggered as long as the database is not in use."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:104
msgid "The databases created for development branches are meant to live around 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:110
msgid "Merging your branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:112
msgid "You can merge your branches easily by drag and dropping them into each other."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:117
msgid "When you want to test the changes of your development branches with the production data, you can either:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:120
msgid "merge the development branch into your staging branch, by drag and dropping it onto the desired staging branch,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:121
msgid "drag and dropping the development branch on the staging section title, to make it become a staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:123
msgid "When your latest changes are ready for production, you can drag and drop your staging branch onto your production branch to merge and deploy in production your newest features."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:127
msgid "If you are bold enough, you can merge your development branches into your production branch as well. It just means you skip the validation of your changes with the production data through a staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:131
msgid "You can merge your development branches into each other, and your staging branches into each other."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:133
msgid "Of course, you can also use :code:`git merge` directly on your workstation to merge your branches. Odoo.sh will be notified when new revisions have been pushed in your branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:136
msgid "Merging a staging branch in the production branch only merges the source code: Any configuration changes you made in the staging databases are not passed to the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:139
msgid "If you test configuration changes in staging branches, and want them to be applied in the production, you have to either:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:141
msgid "write the configuration changes in XML data files overriding the default configuration or views in your branches, and then increase the version of your module in its manifest (*__manifest__.py*) to trigger the update of the module when you merge your staging branch in your production branch. This is the best practice for a better scalability of your developments as you will use the Git versioning features for all your configuration changes, and therefore have a traceability for your changes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:147
msgid "pass them manually from your staging to your production database, by copy/pasting them."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:152
msgid "Tabs"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:155
#: ../../content/administration/odoo_sh/getting_started/settings.rst:57
#: ../../content/administration/odoo_sh/getting_started/settings.rst:85
msgid "History"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:157
msgid "An overview of your branch history:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:159
msgid "The messages of the commits and their authors,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:160
msgid "The various events linked to the platform, such as stage changes, database imports, backup restores."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:165
msgid "For each event, a status is displayed in the top right-hand corner. It can provide information about the ongoing operation on the database (installation, update, backup import, ...), or its result (tests feedback, successful backup import, ...). When an operation is successful, you can access the database thanks to the *connect* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:173
#: ../../content/administration/odoo_sh/getting_started/settings.rst:73
#: ../../content/administration/odoo_sh/getting_started/settings.rst:101
msgid "Mails"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:175
msgid "This tab contains the mail catcher. It displays an overview of the emails sent by your database. The mail catcher is available for your development and staging branches as the emails of your production database are really sent instead of being intercepted."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:184
msgid "Shell"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:186
msgid "A shell access to your container. You can perform basic linux commands (:code:`ls`, :code:`top`) and open a shell on your database by typing :code:`psql`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:192
#: ../../content/administration/odoo_sh/getting_started/branches.rst:208
msgid "You can open multiple tabs and drag-and-drop them to arrange the layout as you wish, for instance side by side."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:196
msgid "Long running shell instances are not guaranteed. Idle shells can be disconnected at anytime in order to free up resources."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:200
msgid "Editor"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:202
msgid "An online integrated development environment (IDE) to edit the source code. You can also open terminals, Python consoles and even Odoo Shell consoles."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:212
#: ../../content/administration/odoo_sh/getting_started/settings.rst:105
msgid "Monitoring"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:214
msgid "This link contains various monitoring metrics of the current build."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:219
msgid "You can zoom, change the time range or select a specific metric on each graph. On the graphs, annotations help you relate to changes on the build (database import, git push, etc...)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:225
#: ../../content/administration/odoo_sh/getting_started/settings.rst:65
#: ../../content/administration/odoo_sh/getting_started/settings.rst:93
msgid "Logs"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:227
msgid "A viewer to have a look to your server logs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:232
msgid "Different logs are available:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:234
msgid "install.log: The logs of the database installation. In a development branch, the logs of the tests are included."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:235
msgid "pip.log: The logs of the Python dependencies installation."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:236
msgid "odoo.log: The logs of the running server."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:237
msgid "update.log: The logs of the database updates."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:238
msgid "pg_long_queries.log: The logs of psql queries that take an unusual amount of time."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:240
msgid "If new lines are added in the logs, they will be displayed automatically. If you scroll to the bottom, the browser will scroll automatically each time a new line is added."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:243
msgid "You can pause the logs fetching by clicking on the according button in the upper right corner of the view. The fetching is automatically stopped after 5 minutes. You can restart it using the play button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:249
#: ../../content/administration/odoo_sh/getting_started/settings.rst:109
msgid "Backups"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:251
msgid "A list of the backups available for download and restore, the ability to perform a manual backup and to import a database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:257
msgid "Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 weekly and 3 monthly backups. Each backup includes the database dump, the filestore (attachments, binary fields), logs and sessions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:260
msgid "Staging and development databases are not backed up. You nevertheless have the possibility to restore a backup of the production database in your staging branches, for testing purposes, or to manually recover data that has been deleted by accident from the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:264
msgid "The list contains the backups kept on the server your production database is hosted on. This server only keeps one month of backups: 7 daily and 4 weekly backups."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:267
msgid "Dedicated backup servers keep the same backups, as well as 3 additional monthly backups. To restore or download one of these monthly backups, please `contact us <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:270
msgid "If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list), as either the container will be changed by the installation of new pip packages, either the database itself will be changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially break things."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:276
msgid "If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course, as an extra precaution, you can make a backup manually before making big changes in your production sources in case something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups to 5 per day."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:282
msgid "The *import database* feature accepts database archives in the format provided by:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:284
msgid "the standard Odoo databases manager, (available for on-premise Odoo servers under :code:`/web/database/manager`)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:286
msgid "the Odoo online databases manager,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:287
msgid "the Odoo.sh backup download button of this *Backups* tab,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:288
msgid "the Odoo.sh dump download button in the :ref:`Builds view <odoosh-gettingstarted-builds>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:295
msgid "Available for production and staging branches for valid projects."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:298
msgid ":doc:`Upgrade documentation <../../upgrade>`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:303
#: ../../content/administration/odoo_sh/getting_started/settings.rst:3
#: ../../content/administration/odoo_sh/getting_started/settings.rst:81
#: ../../content/administration/odoo_sh/getting_started/settings.rst:117
#: ../../content/administration/odoo_sh/getting_started/settings.rst:124
msgid "Settings"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:305
msgid "Here you can find a couple of settings that only apply to the currently selected branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:310
msgid "**Behaviour upon new commit**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:312
msgid "For development and staging branches, you can change the branch's behavior upon receiving a new commit. By default, a development branch will create a new build and a staging branch will update the previous build (see the :ref:`Production Stage <stage_production>`). This is especially useful should the feature you're working on require a particular setup or configuration, to avoid having to manually set it up again on every commit. If you choose new build for a staging branch, it will make a fresh copy from the production build every time a commit is pushed. A branch that is put back from staging to development will automatically be set to 'Do nothing'."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:320
msgid "**Modules installation**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:322
msgid "Choose the modules to install automatically for your development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:327
msgid "*Install only my modules* will install the modules of the branch only. This is the default option. The :ref:`submodules <odoosh-advanced-submodules>` are excluded."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:329
msgid "*Full installation (all modules)* will install the modules of the branch, the modules included in the submodules and all standard modules of Odoo. When running the full installation, the test suite is disabled."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:331
msgid "*Install a list of modules* will install the modules specified in the input just below this option. The names are the technical name of the modules, and they must be comma-separated."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:334
msgid "If the tests are enabled, the standard Odoo modules suite can take up to 1 hour. This setting applies to development builds only. Staging builds duplicate the production build and the production build only installs base."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:339
msgid "**Test suite**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:341
msgid "For development branches, you can choose to enable or disable the test suite. It's enabled by default. When the test suite is enabled, you can restrict them by specifying test tags :ref:`test tags <developer/reference/testing/selection>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:345
msgid "**Odoo Version**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:347
msgid "For development branches only, you can change the version of Odoo, should you want to test upgraded code or develop features while your production database is in the process of being upgraded to a newer version."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:350
msgid "In addition, for each version you have two options regarding the code update."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:352
msgid "You can choose to benefit from the latest bug, security and performance fixes automatically. The sources of your Odoo server will be updated weekly. This is the 'Latest' option."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:354
msgid "You can choose to pin the Odoo sources to a specific revision by selecting them from a list of dates. Revisions will expire after 3 months. You will be notified by mail when the expiration date approaches and if you don't take action afterwards, you will automatically be set to the latest revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:359
msgid "**Custom domains**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:361
msgid "Here you can configure additional domains for the selected branch. It's possible to add other *<name>.odoo.com* domains or your own custom domains. For the latter you have to:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:364
msgid "own or purchase the domain name,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:365
msgid "add the domain name in this list,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:366
msgid "in your registrar's domain name manager, configure the domain name with a ``CNAME`` record set to your production database domain name."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:369
msgid "For instance, to associate *www.mycompany.com* to your database *mycompany.odoo.com*:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:371
msgid "in Odoo.sh, add *www.mycompany.com* in the custom domains of your project settings,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:372
msgid "in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), configure *www.mycompany.com* with a ``CNAME`` record with as value *mycompany.odoo.com*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:375
msgid "Bare domains (e.g. *mycompany.com*) are not accepted:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:377
msgid "they can only be configured using ``A`` records,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:378
msgid "``A`` records only accept IP addresses as value,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:379
msgid "the IP address of your database can change, following an upgrade, a hardware failure or your wish to host your database in another country or continent."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:382
msgid "Therefore, bare domains could suddenly no longer work because of this change of IP address."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:384
msgid "In addition, if you would like both *mycompany.com* and *www.mycompany.com* to work with your database, having the first redirecting to the second is amongst the `SEO best practices <https://support.google.com/webmasters/answer/7451184?hl=en>`_ (See *Provide one version of a URL to reach a document*) in order to have one dominant URL. You can therefore just configure *mycompany.com* to redirect to *www.mycompany.com*. Most domain managers have the feature to configure this redirection. This is commonly called a web redirection."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:391
msgid "**HTTPS/SSL**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:393
msgid "If the redirection is correctly set up, the platform will automatically generate an SSL certificate with `Let's Encrypt <https://letsencrypt.org/about/>`_ within the hour and your domain will be accessible through HTTPS."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:397
msgid "While it is currently not possible to configure your own SSL certificates on the Odoo.sh platform we are considering the feature if there is enough demand."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:401
msgid "**SPF and DKIM compliance**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:403
msgid "In case the domain of your users email addresses use SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize Odoo as a sending host in your domain name settings to increase the deliverability of your outgoing emails. The configuration steps are explained in the documentation about :ref:`SPF <email_communication/spf_compliant>` and :ref:`DKIM <email_communication/dkim_compliant>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:410
msgid "Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host can lead to the delivery of your emails as spam in your contacts inbox."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:414
msgid "Shell commands"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:416
msgid "In the top right-hand corner of the view, different shell commands are available."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:421
msgid "Each command can be copied in the clipboard to be used in a terminal, and some of them can be used directly from Odoo.sh by clicking the *run* button in such case a popup will prompt the user in order to define eventual placeholders such as ``<URL>``, ``<PATH>``, ..."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:427
msgid "Clone"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:429
msgid "Download the Git repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:435
msgid "Clones the repository *odoo/odoo*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:437
msgid ":code:`--recurse-submodules`: Downloads the submodules of your repository. Submodules included in the submodules are downloaded as well."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:438
msgid ":code:`--branch`: checks out a specific branch of the repository, in this case *master*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:440
msgid "The *run* button is not available for this command, as it is meant to be used on your machines."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:443
msgid "Fork"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:445
msgid "Create a new branch based on the current branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:451
msgid "Creates a new branch called *feature-1* based on the branch *master*, and then checkouts it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:457
msgid "Uploads the new branch *feature-1* on your remote repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:460
msgid "Merge"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:462
msgid "Merge the current branch in another branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:468
msgid "Merges the branch *staging-1* in the current branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:474
#: ../../content/administration/odoo_sh/getting_started/branches.rst:547
msgid "Uploads the changes you just added in the *master* branch on your remote repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:477
msgid "SSH"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:482
msgid "In order to use SSH, you have to set up your profile SSH public key (if it is not already done). To do so, follow these steps:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:485
msgid "`Generate a new SSH key <https://help.github.com/en/github/authenticating-to-github/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:487
msgid "`Copy the SSH key to your clipboard <https://help.github.com/en/github/authenticating-to-github/adding-a-new-ssh-key-to-your-github-account>`_ (only apply the step 1)"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:490
msgid "Paste the copied content to your profile SSH keys and press \"Add\""
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:495
msgid "The key should appear below"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:501
msgid "Connection"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:503
msgid "To connect to your builds using ssh use the following command in a terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:509
msgid "You will find a shortcut for this command into the SSH tab in the upper right corner."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:514
msgid "Provided you have the :ref:`correct access rights <odoosh-gettingstarted-settings-collaborators>` on the project, you'll be granted ssh access to the build."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:518
msgid "Long running ssh connections are not guaranteed. Idle connections will be disconnected in order to free up resources."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:522
msgid "Submodule"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:524
msgid "Add a branch from another repository in your current branch as a *submodule*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:526
msgid "*Submodules* allows you to use modules from other repositories in your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:528
msgid "The submodules feature is detailed in the chapter :ref:`Submodules <odoosh-advanced-submodules>` of this documentation."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:535
msgid "Adds the branch *master* of the repository *<URL>* as a submodule under the path *<PATH>* in your current branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:541
msgid "Commits all your current changes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:552
msgid "Delete a branch from your repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:558
msgid "Deletes the branch in your remote repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:564
msgid "Deletes the branch in your local copy of the repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:6
msgid "Builds"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:11
msgid "In Odoo.sh, a build is considered as a database loaded by an Odoo server (`odoo/odoo <https://github.com/odoo/odoo>`_ & `odoo/enterprise <https://github.com/odoo/enterprise>`_) running on a specific revision of your project repository in a containerized environment. Its purpose is to test the well-behavior of the server, the database and the features with this revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:20
msgid "In this view, a row represents a branch, and a cell of a row represents a build of this branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:22
msgid "Most of the time, builds are created following pushes on your Github repository branches. They can be created as well when you do other operations, such as importing a database on Odoo.sh or asking a rebuild for a branch in your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:26
msgid "A build is considered successful if no errors or warnings come up during its creation. A successful build is highlighted in green."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:29
msgid "A build is considered failed if errors come up during its creation. A failed build is highlighted in red."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:32
msgid "If warnings come up during the creation, but there are no errors, the build is considered almost successful. It is highlighted in yellow to notify the developer warnings were raised."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:35
msgid "Builds do not always create a database from scratch. For instance, when pushing a change on the production branch, the build created just starts the server with your new revision and tries to load the current production database on it. If no errors come up, the build is considered successful, and otherwise failed."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:46
msgid "The first build of a production branch creates a database from scratch. If this build is successful, this database is considered as the production database of your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:49
msgid "From then, pushes on the production branch will create new builds that attempt to load the database using a server running with the new revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:52
msgid "If the build is successful, or has warnings but no errors, the production database will now run with this build, along with the revision associated to this build."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:55
msgid "If the build fails to load or update the database, then the previous successful build is re-used to load the database, and therefore the database will run using a server running with the previous successful revision."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:59
msgid "The build used to run the production database is always the first of the builds list. If a build fails, it is put after the build currently running the production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:65
msgid "Staging builds duplicate the production database, and try to load this duplicate with the revisions of the staging branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:68
msgid "Each time you push a new revision on a staging branch, the build created uses a new copy of the production database. The databases are not re-used between builds of the same branch. This ensures:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:71
msgid "staging builds use databases that are close to what the production looks like, so you do not make your tests with outdated data,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:74
msgid "you can play around as much as you want in the same staging database, and you can then ask for a rebuild when you want to restart with a new copy of the production."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:77
msgid "Nevertheless, this means that if you make configuration changes in staging databases and do not apply them in the production, they will not be passed on the next build of the same staging branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:83
msgid "Development builds create new databases, load the demo data and run the unit tests."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:85
msgid "A build will be considered failed and highlighted in red if tests fail during the installation, as they are meant to raise errors if something wrong occurs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:88
msgid "If all tests pass, and there is no error, the build will be considered successful."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:90
msgid "According to the list of modules to install and test, a development build can take up to 1 hour to be ready. This is due to the large number of tests set in the default Odoo modules suite."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:94
msgid "Features"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:96
msgid "The production branch will always appear first, and then the other branches are ordered by last build created. You can filter out the branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:102
msgid "For each branch, you can access the last build's database using the *Connect* link and jump to the branch code using the *Github* link. For other branches than the production, you can create a new build which will use the latest revision of the branch using the link *rebuild*. This last link is not available when there is already a build in progress for the branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:110
msgid "For each build, you can access the revision changes using the button with the Github icon. You can access the build's database as the administrator using the *Connect* button. Also, you can access the database with another user using the *Connect as* button, in the dropdown menu of the *Connect* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:122
msgid "In the dropdown menu of the build, you can access the same features than in :ref:`the branches view <odoosh-gettingstarted-branches-tabs>`: *Logs*, *Web Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to *Download a dump* of the build's database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:6
msgid "Create your project"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:9
msgid "Deploy your platform"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:11
msgid "Go to `Odoo.sh <https://www.odoo.sh/>`_ and hit the *Deploy your platform* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:17
msgid "Sign in with Github"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:19
msgid "Sign in with your Github account. If you do not have an account yet, hit the *Create an account* link."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:26
msgid "Authorize Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:28
msgid "Grant Odoo.sh the required accesses to your account by clicking the *Authorize* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:33
msgid "Odoo.sh basically needs:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:35
msgid "to know your Github login and email,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:36
msgid "to create a new repository in case you decide to start from scratch,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:37
msgid "to read your existing repositories, including the ones of your organizations, in case you want to start from an existing repository,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:39
msgid "to create a webhook to be notified each time you push changes,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:40
msgid "to commit changes to make your deployment easier, merging branches or adding new `submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ for example."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:44
msgid "Submit your project"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:46
msgid "Choose if you want to start from scratch by creating a new repository, or if you want to use an existing repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:49
msgid "Then, choose a name or select the repository you want to use."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:51
msgid "Choose the Odoo version you want to use. If you plan to import an existing database or an existing set of applications, you might need to choose the according version. If you start from scratch, use the latest version."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:55
msgid "Enter your *subscription code*. This is also called *subscription referral*, *contract number* or *activation code*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:58
msgid "It should be the code of your Enterprise subscription that includes Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:60
msgid "Partners can use their partnership codes to start a trial. Should their clients start a project, they ought to get an Enterprise subscription including Odoo.sh and use its subscription code. The partner will get 50% of the amount back as commission. Contact your sales representative or account manager in order to get it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:65
msgid "When submitting the form, if you are notified your subscription is not valid, it either means:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:67
msgid "it is not an existing subscription,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:68
msgid "it is not a partnership subscription,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:69
msgid "it is an enterprise subscription, but which does not include Odoo.sh,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:70
msgid "it is neither a partnership subscription or an enterprise subscription (e.g. an online subscription)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:73
msgid "In case of doubt with your subscription, please contact the `Odoo support <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:80
msgid "You're done !"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:82
msgid "You can start using Odoo.sh. Your first build is about to be created. You will soon be able to connect to your first database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:91
msgid "Import your database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:93
msgid "You can import your database in your Odoo.sh project as long as it is in a :doc:`supported version </administration/maintain/supported_versions>` of Odoo."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:97
msgid "Push your modules in production"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:99
msgid "If you use community or custom modules, add them in a branch in your Github repository. Databases hosted on the Odoo.com online platform do not have any custom modules. Users of these databases can therefore skip this step."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:103
msgid "You can structure your modules as you wish, Odoo.sh will automatically detect the folders containing Odoo addons. For instance, you can put all your modules folder in the root directory of your repository, or group the modules in folders by categories that you define (accounting, project, ...)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:108
msgid "For community modules available in public Git repositories, you can also consider to add them using :ref:`Submodules <odoosh-advanced-submodules>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:111
msgid "Then, either :ref:`make this branch the production branch <odoosh-gettingstarted-branches-stages>`, or :ref:`merge it into your production branch <odoosh-gettingstarted-branches-mergingbranches>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:115
msgid "Download a backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:118
msgid "On-premise databases"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:120
msgid "Access the URL :file:`/web/database/manager` of your on-premise database and download a backup."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:124
msgid "If you cannot access the database manager, it may have been disabled by your system administrator. See the :ref:`database manager security documentation <db_manager_security>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:127
msgid "You will need the master password of your database server. If you do not have it, contact your system administrator."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:133
msgid "Choose a zip including the filestore as the backup format."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:139
msgid "Odoo Online databases"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:141
msgid "`Access your databases manager <https://accounts.odoo.com/my/databases/manage>`_ and download a backup of your database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:149
msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:152
msgid "Upload the backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:154
msgid "Then, in your Odoo.sh project, in the backups tab of your production branch, import the backup you just downloaded."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:160
msgid "Once the backup imported, you can access the database using the *Connect* button in the history of the branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:167
msgid "Check your outgoing email servers"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:169
msgid "There is a default mail server provided with Odoo.sh. To use it, there must be no enabled outgoing mail server configured in your database in :menuselection:`Settings --> Technical --> Outgoing Mail Servers` (:ref:`Developer mode <developer-mode>` must be activated)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:174
msgid "After the import of your database, all outgoing email servers are disabled so you use the Odoo.sh email server provided by default."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:178
msgid "Port 25 is (and will stay) closed. If you want to connect to an external SMTP server, you should use ports 465 and 587."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:182
msgid "Check your scheduled actions"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:184
msgid "All scheduled actions are disabled after the import."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:186
msgid "This is to prevent your newly imported database to perform actions that could impact your running production, such as sending the mails remaining in the queue, processing mass mailings, or third-party services synchronization (Calendars, files hosting, ...)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:190
msgid "If you plan to make the imported database your production, enable the scheduled actions you need. You can check what is enabled in the database of origin and enable the same actions in the imported database. Scheduled actions are located under :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:196
msgid "Register your subscription"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:198
msgid "Your subscription is unlinked after the import."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:200
msgid "The imported database is considered a duplicate by default and the enterprise subscription is therefore removed, as you can only have one database linked per subscription."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:203
msgid "If you plan to make it your production, unlink your former database from the subscription, and register the newly imported database. Read the :doc:`database registration documentation <../../maintain/on_premise>` for instructions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3
msgid "Your first module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:10
msgid "This tutorial requires :ref:`you created a project on Odoo.sh <odoosh-gettingstarted-create>`, and you know your Github repository's URL."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13
msgid "Basic use of Git and Github is explained."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15
msgid "The below assumptions are made:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:18
msgid "*odoo* is the Github user,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19
msgid "*odoo-addons* is the Github repository,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20
msgid "*feature-1* is the name of a development branch,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21
msgid "*master* is the name of the production branch,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22
msgid "*my_module* is the name of the module."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24
msgid "Replace these by the values of your choice."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27
msgid "Create the development branch"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30
msgid "From Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32
msgid "In the branches view:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34
msgid "hit the :code:`+` button next to the development stage,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35
msgid "choose the branch *master* in the *Fork* selection,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36
msgid "type *feature-1* in the *To* input."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38
msgid "|pic1| |pic2|"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40
msgid "pic1"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43
msgid "pic2"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:56
msgid "From your computer"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58
msgid "Clone your Github repository on your computer:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67
msgid "Create a new branch:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74
msgid "Create the module structure"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77
msgid "Scaffolding the module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:82
msgid "From the Odoo.sh editor, in a terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88
msgid "Or, from your computer, if you have an :doc:`installation of Odoo <../../install/source>`:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:98
msgid "The below structure will be generated:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:125
msgid "Uncomment the content of the files:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127
msgid "*models/models.py*, an example of model with its fields,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129
msgid "*views/views.xml*, a tree and a form view, with the menus opening them,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131
msgid "*demo/demo.xml*, demo records for the above example model,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133
msgid "*controllers/controllers.py*, an example of controller implementing some routes,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135
msgid "*views/templates.xml*, two example qweb views used by the above controller routes,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:146
msgid "Manually"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148
msgid "If you want to create your module structure manually, you can follow the :doc:`/developer/tutorials/getting_started` tutorial to understand the structure of a module and the content of each file."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153
msgid "Push the development branch"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155
msgid "Stage the changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395
msgid "Commit your changes"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167
msgid "Push your changes to your remote repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169
msgid "From an Odoo.sh editor terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:183
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409
msgid "Or, from your computer terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:197
msgid "Test your module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199
msgid "Your branch should appear in your development branches in your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/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/getting_started/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/getting_started/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/getting_started/first_module.rst:223
msgid "Test with the production data"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/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/getting_started/first_module.rst:230
msgid "You can either:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/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/getting_started/first_module.rst:243
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289
msgid "You can also use the :code:`git merge` command to merge your branches."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:251
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297
msgid "Once the database ready, you can access it using the *Connect* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300
msgid "Install your module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/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/getting_started/first_module.rst:266
msgid "Activate the :ref:`developer mode <developer-mode>`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267
msgid "in the apps menu, click the *Update Apps List* button,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268
msgid "in the dialog that appears, click the *Update* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273
msgid "Your module will then appear in the list of available apps."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279
msgid "Deploy in production"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/first_module.rst:284
msgid "Drag and drop your staging branch on the production branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/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/getting_started/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/getting_started/first_module.rst:308
msgid "Add a change"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310
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/getting_started/first_module.rst:315
msgid "From the Odoo.sh editor,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314
msgid "browse to your module folder *~/src/user/my_module*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315
msgid "then, open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321
msgid "Or, from your computer,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318
msgid "use the file browser of your choice to browse to your module folder *~/src/odoo-addons/my_module*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320
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/getting_started/first_module.rst:323
msgid "Then, after the description field"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329
msgid "Add a datetime field"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335
msgid "Then, open the file *views/views.xml*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473
msgid "After"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479
msgid "Add"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349
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/getting_started/first_module.rst:352
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/getting_started/first_module.rst:355
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/getting_started/first_module.rst:358
msgid "Open the module manifest *__manifest__.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504
msgid "with"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372
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/getting_started/first_module.rst:375
msgid "Browse to your Git folder."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377
msgid "Then, from an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389
msgid "Then, stage your changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401
msgid "Push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403
msgid "From an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415
msgid "The platform will then create a new build for the branch *feature-1*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420
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/getting_started/first_module.rst:426
msgid "Use an external Python library"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428
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/getting_started/first_module.rst:432
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/getting_started/first_module.rst:436
msgid "**PostgreSQL extensions** are not supported on Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437
msgid "For more information, consult our `FAQ <https://www.odoo.sh/faq#install_dependencies>`_."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439
msgid "The platform will use this file to automatically install the Python libraries your project needs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441
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/getting_started/first_module.rst:444
msgid "Create a file *requirements.txt* in the root folder of your repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446
msgid "From the Odoo.sh editor, create and open the file ~/src/user/requirements.txt."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448
msgid "Or, from your computer, create and open the file ~/src/odoo-addons/requirements.txt."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456
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/getting_started/first_module.rst:459
msgid "Open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461
msgid "Before"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494
msgid "Adding a Python dependency requires a module version increase for the platform to install it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496
msgid "Edit the module manifest *__manifest__.py*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510
msgid "Stage and commit your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518
msgid "Then, push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520
msgid "In an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526
msgid "In your computer terminal:"
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 <odoosh-gettingstarted-branches-tabs>`, :ref:`the builds dropdown menu <odoosh-gettingstarted-builds-dropdown-menu>` 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 <odoosh-gettingstarted-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 two levels of users:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:38
msgid "Admin: has access to all features of Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:39
msgid "User: does not have access to the project settings nor to the production and staging databases."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:41
msgid "The user group is meant for developers who can make modifications in your code but are not allowed to access the production data. Users of this group cannot connect to the production and staging databases using the *1-click connect* feature, but they can of course use their regular account on these databases if they have one, using their regular credentials."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:46
msgid "In addition, they cannot use the webshell nor have access to the server logs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:54
msgid "User"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:55
msgid "Admin"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:61
#: ../../content/administration/odoo_sh/getting_started/settings.rst:89
msgid "1-click connect"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:69
#: ../../content/administration/odoo_sh/getting_started/settings.rst:97
msgid "Shell/SSH"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:84
msgid "Production & Staging"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:118
msgid "|green|\\*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:120
#: ../../content/administration/odoo_sh/getting_started/status.rst:3
msgid "Status"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:130
msgid "\\* Only in staging branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:145
msgid "Public Access"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:147
msgid "Allow public access to your development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:152
msgid "If activated, this option exposes the Builds page publicly, allowing visitors to connect to your development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:155
msgid "In addition, visitors have access to the logs, shell and mails of your development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:157
msgid "Production and staging builds are excluded, visitors can only see their status."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:162
msgid "Custom domains"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:164
msgid "To configure additional domains please refer to the corresponding branch's :ref:`settings tab <odoosh-gettingstarted-branches-tabs-settings>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:172
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:176
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:183
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:188
msgid "To configure the deploy key for a private repository, proceed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:190
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:192
msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:193
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:196
msgid "copy the public key,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:198
msgid "it should look like *ssh-rsa some...random...characters...here...==*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:200
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:202
msgid "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:203
msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:204
msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:205
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:208
msgid "Storage Size"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:210
msgid "This section shows the storage size used by your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:215
msgid "Storage size is computed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:217
msgid "the size of the PostgreSQL database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:219
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:222
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:225
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:229
msgid "Database Workers"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:231
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:239
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:245
msgid "Staging Branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:247
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:254
msgid "Activation"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:256
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/odoo_sh/overview/introduction.rst:3
msgid "Introduction to Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/overview/introduction.rst:10
msgid "The documentation will help you go live with your Odoo.sh project in no time."
msgstr ""
#: ../../content/administration/upgrade.rst:7
msgid "An upgrade is the process of moving your database from an older version to a newer :doc:`supported version <maintain/supported_versions>` (e.g., Odoo 14.0 to Odoo 16.0). Frequently upgrading is essential as each version comes with new and improved features, bug fixes, and security patches."
msgstr ""
#: ../../content/administration/upgrade.rst:15
msgid "The Rolling Release process allows Odoo Online customers to upgrade their database directly from a message prompt sent to the database administrator as soon as a new version is released. The invitation to upgrade is only sent if no issues are detected during the automatic tests."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "The upgrade message prompt on the top right of the database"
msgstr ""
#: ../../content/administration/upgrade.rst:22
msgid "It is strongly recommended to manually :ref:`test the upgrade first <upgrade/test_your_db>`. Clicking :guilabel:`I want to test first` redirects to `the database manager <https://www.odoo.com/my/databases/>`_, where it is possible to request an upgraded test database and check it for any discrepancies."
msgstr ""
#: ../../content/administration/upgrade.rst:27
msgid "It is **not** recommended to click :guilabel:`Upgrade Now` without testing first, as it immediately triggers the live production database upgrade."
msgstr ""
#: ../../content/administration/upgrade.rst:30
msgid "If the Rolling Release process detects an issue with the upgrade, it will be deactivated until the issue is resolved."
msgstr ""
#: ../../content/administration/upgrade.rst:33
msgid "An upgrade does not cover:"
msgstr ""
#: ../../content/administration/upgrade.rst:35
msgid "Downgrading to a previous version of Odoo"
msgstr ""
#: ../../content/administration/upgrade.rst:36
msgid ":doc:`Switching editions <maintain/enterprise>` (e.g., from Community to Enterprise)"
msgstr ""
#: ../../content/administration/upgrade.rst:37
msgid ":doc:`Changing hosting type </administration/maintain/hosting_changes>` (e.g., from on-premise to Odoo Online)"
msgstr ""
#: ../../content/administration/upgrade.rst:39
msgid "Migrating from another ERP to Odoo"
msgstr ""
#: ../../content/administration/upgrade.rst:42
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-database>` while also :doc:`upgrading the source code of your custom modules </developer/howtos/upgrade_custom_db>`."
msgstr ""
#: ../../content/administration/upgrade.rst:50
msgid "Upgrading in a nutshell"
msgstr ""
#: ../../content/administration/upgrade.rst:52
msgid "Request an upgraded test database (see :ref:`obtaining an upgraded test database <upgrade/request-test-database>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:55
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:58
msgid "Thoroughly test the upgraded database (see :ref:`testing the new version of the database <upgrade/test_your_db>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:61
msgid "Report any issue encountered during the testing to Odoo via the `support page <https://odoo.com/help?stage=migration>`__."
msgstr ""
#: ../../content/administration/upgrade.rst:64
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:67
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/upgrade-prod>`)."
msgstr ""
#: ../../content/administration/upgrade.rst:70
msgid "Report any issue encountered during the upgrade to Odoo via the `support page <https://odoo.com/help?stage=post_upgrade>`__."
msgstr ""
#: ../../content/administration/upgrade.rst:76
msgid "Obtaining an upgraded test database"
msgstr ""
#: ../../content/administration/upgrade.rst:78
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://odoo.com/my/databases>`_, or your `Odoo.sh project <https://odoo.sh/project>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:84
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:92
msgid "Odoo Online databases can be manually upgraded via the `database manager <https://odoo.com/my/databases>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:95
msgid "The database manager displays all databases associated with the user's account. Databases not on the most recent version of Odoo display an arrow in a circle icon next to their name, indicating that they can be upgraded."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "The database manager with an upgrade button next to the name of a database."
msgstr ""
#: ../../content/administration/upgrade.rst:102
msgid "Click the **arrow in a circle** icon to start the upgrade process. In the popup, fill in:"
msgstr ""
#: ../../content/administration/upgrade.rst:104
msgid "The **version** of Odoo you want to upgrade to, usually the latest version"
msgstr ""
#: ../../content/administration/upgrade.rst:105
msgid "The **email** address that should receive the link to the upgraded database"
msgstr ""
#: ../../content/administration/upgrade.rst:106
msgid "The :guilabel:`Purpose` of the upgrade, which is automatically set to :guilabel:`Test` for your first upgrade request"
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "The \"Upgrade your database\" popup."
msgstr ""
#: ../../content/administration/upgrade.rst:112
msgid "The :guilabel:`Upgrade in progress` tag is displayed next to the database name until completion. Once the process succeeds, an email containing a link to the upgraded test database is sent to the address provided. The database can also be accessed from the database manager by clicking the dropdown arrow before the database name."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "Clicking the menu arrow displays the upgraded test database."
msgstr ""
#: ../../content/administration/upgrade.rst:122
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:127
msgid "The **latest production daily automatic backup** is then sent to the `upgrade platform <https://upgrade.odoo.com>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:130
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:138
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:143
msgid "Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more information."
msgstr ""
#: ../../content/administration/upgrade.rst:145
#: ../../content/administration/upgrade.rst:341
msgid "On-premise"
msgstr ""
#: ../../content/administration/upgrade.rst:147
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:154
msgid "The following command can be used to display the general help and the main commands:"
msgstr ""
#: ../../content/administration/upgrade.rst:160
msgid "An upgraded test database can also be requested via the `Upgrade page <https://upgrade.odoo.com/>`_."
msgstr ""
#: ../../content/administration/upgrade.rst:164
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:169
msgid "For security reasons, only the person who submitted the upgrade request can download it."
msgstr ""
#: ../../content/administration/upgrade.rst:170
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:172
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:175
msgid "The upgraded database contains:"
msgstr ""
#: ../../content/administration/upgrade.rst:177
msgid "A `dump.sql` file containing the upgraded database"
msgstr ""
#: ../../content/administration/upgrade.rst:178
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:185
msgid "You can request multiple test databases if you wish to test an upgrade more than once."
msgstr ""
#: ../../content/administration/upgrade.rst:190
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:198
msgid "Testing the new version of the database"
msgstr ""
#: ../../content/administration/upgrade.rst:200
msgid "It is essential to spend some time testing 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:205
msgid "Test databases are neutralized, and some features are disabled to prevent them from impacting the production database:"
msgstr ""
#: ../../content/administration/upgrade.rst:208
msgid "Scheduled actions are disabled."
msgstr ""
#: ../../content/administration/upgrade.rst:209
msgid "Outgoing mail servers are disabled by archiving the existing ones and adding a fake one."
msgstr ""
#: ../../content/administration/upgrade.rst:210
msgid "Payment providers and delivery carriers are reset to the test environment."
msgstr ""
#: ../../content/administration/upgrade.rst:211
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:214
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:217
msgid "Basic test checklist"
msgstr ""
#: ../../content/administration/upgrade.rst:219
msgid "Are there views that are deactivated in your test database but active in your production database?"
msgstr ""
#: ../../content/administration/upgrade.rst:221
msgid "Are your usual views still displayed correctly?"
msgstr ""
#: ../../content/administration/upgrade.rst:222
msgid "Are your reports (invoice, sales order, etc.) correctly generated?"
msgstr ""
#: ../../content/administration/upgrade.rst:223
msgid "Are your website pages working correctly?"
msgstr ""
#: ../../content/administration/upgrade.rst:224
msgid "Are you able to create and modify records? (sales orders, invoices, purchases, users, contacts, companies, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:226
msgid "Are there any issues with your mail templates?"
msgstr ""
#: ../../content/administration/upgrade.rst:227
msgid "Are there any issues with saved translations?"
msgstr ""
#: ../../content/administration/upgrade.rst:228
msgid "Are your search filters still present?"
msgstr ""
#: ../../content/administration/upgrade.rst:229
msgid "Can you export your data?"
msgstr ""
#: ../../content/administration/upgrade.rst:233
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:236
msgid "Buying this product (Purchase app)."
msgstr ""
#: ../../content/administration/upgrade.rst:237
msgid "Confirming the reception of this product (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:238
msgid "Checking if the route to receive this product is the same in your production database (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:240
msgid "Selling this product (Sales app) to a random customer."
msgstr ""
#: ../../content/administration/upgrade.rst:241
msgid "Opening your customer database (Contacts app), selecting a customer (or company), and checking its data."
msgstr ""
#: ../../content/administration/upgrade.rst:243
msgid "Shipping this product (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:244
msgid "Checking if the route to ship this product is the same as in your production database (Inventory app)."
msgstr ""
#: ../../content/administration/upgrade.rst:246
msgid "Validating a customer invoice (Invoicing or Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:247
msgid "Crediting the invoice (issuing a credit note) and checking if it behaves as in your production database."
msgstr ""
#: ../../content/administration/upgrade.rst:249
msgid "Checking your reports' results (Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:250
msgid "Randomly checking your taxes, currencies, bank accounts, and fiscal year (Accounting app)."
msgstr ""
#: ../../content/administration/upgrade.rst:251
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:254
msgid "This list is **not** exhaustive. Extend the example to your other apps based on your use of Odoo."
msgstr ""
#: ../../content/administration/upgrade.rst:256
msgid "If you face an issue while testing your upgraded test database, you can request the assistance of Odoo via the `support page <https://odoo.com/help?stage=migration>`__ by selecting the option related to testing the upgrade. 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:261
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:267
msgid "Do not forget to test:"
msgstr ""
#: ../../content/administration/upgrade.rst:269
msgid "Integrations with external software (EDI, APIs, etc.)"
msgstr ""
#: ../../content/administration/upgrade.rst:270
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:272
msgid "Data exports"
msgstr ""
#: ../../content/administration/upgrade.rst:273
msgid "Automated actions"
msgstr ""
#: ../../content/administration/upgrade.rst:274
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:280
msgid "Upgrading the production database"
msgstr ""
#: ../../content/administration/upgrade.rst:282
msgid "Once the :ref:`tests <upgrade/test_your_db>` 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. It can be planned in coordination with Odoo's upgrade support analysts, reachable via the `support page <https://odoo.com/help>`__."
msgstr ""
#: ../../content/administration/upgrade.rst:287
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:290
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:296
msgid "Going into production without first testing may lead to:"
msgstr ""
#: ../../content/administration/upgrade.rst:298
msgid "Users failing to adjust to the changes and new features"
msgstr ""
#: ../../content/administration/upgrade.rst:299
msgid "Business interruptions (e.g., no longer having the possibility to validate an action)"
msgstr ""
#: ../../content/administration/upgrade.rst:300
msgid "Poor customer experience (e.g., an eCommerce website that does not work correctly)"
msgstr ""
#: ../../content/administration/upgrade.rst:302
msgid "The process of upgrading a production database is similar to upgrading a test database with a few exceptions."
msgstr ""
#: ../../content/administration/upgrade.rst:309
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>`, except for the purpose option, which must be set to :guilabel:`Production` instead of :guilabel:`Test`."
msgstr ""
#: ../../content/administration/upgrade.rst:314
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:320
msgid "The process is similar to :ref:`obtaining an upgraded test database <upgrade/request-test-database>` on the :guilabel:`Production` branch."
msgstr ""
#: ../../content/administration/upgrade.rst:0
msgid "View from the upgrade tab"
msgstr ""
#: ../../content/administration/upgrade.rst:326
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:332
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:336
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:343
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:350
msgid "An upgraded production database can also be requested via the `Upgrade page <https://upgrade.odoo.com/>`_. 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:357
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:361
msgid "In case of an issue with your production database, you can request the assistance of Odoo via the `support page <https://odoo.com/help?stage=post_upgrade>`__ by selecting the option related to the upgrade in production."
msgstr ""
#: ../../content/administration/upgrade.rst:369
msgid "Service-level agreement (SLA)"
msgstr ""
#: ../../content/administration/upgrade.rst:371
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:374
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:379
msgid "Upgrade services covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:381
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:384
msgid "the upgrade of all **standard applications**;"
msgstr ""
#: ../../content/administration/upgrade.rst:385
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:387
msgid "the upgrade of all **developments and customizations covered by a maintenance of customizations subscription**."
msgstr ""
#: ../../content/administration/upgrade.rst:390
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:394
msgid "Upgrade services not covered by the SLA"
msgstr ""
#: ../../content/administration/upgrade.rst:396
msgid "The following upgrade-related services are **not** included:"
msgstr ""
#: ../../content/administration/upgrade.rst:398
msgid "the **cleaning** of pre-existing data and configurations while upgrading;"
msgstr ""
#: ../../content/administration/upgrade.rst:399
msgid "the upgrade of **custom modules created in-house or by third parties**, including Odoo partners;"
msgstr ""
#: ../../content/administration/upgrade.rst:400
msgid "lines of **code added to standard modules**, i.e., customizations created outside the Studio app, code entered manually, and :ref:`automated actions using Python code <studio/automated-actions/action>`; and"
msgstr ""
#: ../../content/administration/upgrade.rst:403
msgid "**training** on using the upgraded version's features and workflows."
msgstr ""
#: ../../content/administration/upgrade.rst:406
msgid ":doc:`Odoo.sh documentation <odoo_sh>`"
msgstr ""
#: ../../content/administration/upgrade.rst:407
msgid ":doc:`Supported Odoo versions <maintain/supported_versions>`"
msgstr ""
Reference in New Issue View Git Blame Copy Permalink