NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
14.0-survey-ksc
documentation/locale/sources/administration.pot

4870 lines
235 KiB
Plaintext
Raw Permalink Normal View History

[I18N] *: export pot files And fetch matching translations
2021-05-18 12:16:30 +07:00
# 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 14.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-05-18 07:12+0200\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:3
msgid "Administration"
msgstr ""
#: ../../content/administration/db_management.rst:3
msgid "Database Management"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:6
msgid "Online Database management"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:8
msgid "To manage your databases, access the `database management page <https://www.odoo.com/my/databases>`__ (you will have to sign in). Then click on the `Manage Your Databases <https://www.odoo.com/my/databases/manage>`__ button."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:16
msgid "Make sure you are connected as the administrator of the database you want to manage - many operations depends on indentifying you remotely to that database."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:20
msgid "Several actions are available:"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:26
msgid ":ref:`Upgrade <upgrade_button>`"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:26
msgid "Upgrade your database to the latest Odoo version to enjoy cutting-edge features"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:30
msgid ":ref:`Duplicate <duplicate_online>`"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:29
msgid "Make an exact copy of your database, if you want to try out new apps or new flows without compromising your daily operations"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:32
msgid ":ref:`Rename <rename_online_database>`"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:33
msgid "Rename your database (and its URL)"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:35
msgid "**Backup**"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:35
msgid "Download an instant backup of your database; note that we back up databases daily according to our Odoo Cloud SLA"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:38
msgid ":ref:`Domains <custom_domain>`"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:38
msgid "Configure custom domains to access your database via another URL"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:40
msgid ":ref:`Delete <delete_online_database>`"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:41
msgid "Delete a database instantly"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:44
msgid "Contact Support"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:43
msgid "Access our `support page <https://www.odoo.com/help>`__ with the correct database already selected"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:49
#: ../../content/administration/db_upgrade.rst:11
msgid "Upgrade"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:51
msgid "Upgrading your database to a newer version of Odoo is a complex operation that require time and caution. It is extremely important that you fully test the process before upgrading your production database."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:55
msgid "Odoo releases new versions regularly (at least once a year), and upgrading your database to enjoy new Odoo features is part of the Odoo Online experience."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:58
msgid "The upgrade process can take some time, especially if you use multiple apps or apps that manage sensitive data (e.g. Accounting, Inventory, etc.). In general, the 'smaller' the database, the quickest the upgrade. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase and Manufacturing."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:64
msgid "Unfortunately, it is impossible to give time estimates for every upgrade request, since Odoo.com will test manually every database upgrade at least once and will need to correct/adapt changes made to the standard Odoo Apps (e.g. through Studio or through a Success Pack) on a case-by-case basis. This can make the process slower, since requests are treated in the order they arrive. This is especially true in the months following the release of a new major version, which can lengthen the upgrade delay significantly."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:72
msgid "The upgrade process is quite simple from your point of view:"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:74
msgid "You request a test upgrade"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:75
msgid "Once all tests have been validated **by you**, you upgrade your actual database"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:77
msgid "The process to request a test or a production (*actual*) upgrade is the same."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:79
msgid "First, make sure to be connected to the database you want to upgrade and access the `database management page <https://www.odoo.com/my/databases>`__."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:82
msgid "You have to have an active session with access to the Settings app in the database you want to upgrade for the button to be visible."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:85
msgid "On the line of the database you want to upgrade, click on the \"Cog\" menu. If an newer version of Odoo is available, you will see an 'Upgrade' button."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:92
msgid "You have the possibility to choose the target version of the upgrade. By default, we select the highest available version available for your database; if you were already in the process of testing an upgrade, we will automatically select the version you were already testing (even if we released a more recent version during your tests)."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:101
msgid "By clicking on the \"Test upgrade\" button, an upgrade request will be generated. Only one request can be made at time for each database; if a request has already been made, you will see an 'Upgrade Queued' note instead and asking another request will not be possible."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:106
msgid "A test upgrade will create a copy of your database, upgrade it and make it available to you automatically once successful. If this is the first test you request for this particular database, a manual testing phase will be done by Odoo.com - this could take time (up to several weeks). Subsequent requests will not go through that manual testing step and will usually be made available in a few hours. Once the test database is available, you should receive an e-mail with the URL of the test database."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:114
msgid "**Testing your database is the most important step of the upgrade process!** Even though we test all upgrades manually, we do not know your work processes. A change in standard worfklows of Odoo in new versions might require you to change internal processes, or some of the customizations you made through Odoo Studio might not work properly. *It is up to you to make sure that everything works as it should!* You can report issues with your test database through our `Support page <https://www.odoo.com/help>`__."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:122
msgid "Make sure to do one last test of your upgrade right before the final upgrade (e.g. the day before) to ensure everything will run smoothly. Downgrading is not possible and post-poning an upgrade is always easier than being prevented to work by an upgrade issue after the fact!"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:127
msgid "Once you are ready and you have validated all your tests, you can click again on the Upgrade button and confirm by clicking on Upgrade (the button with the little rocket!) to switch your production database to the new version. Your database will then be taken offline within the next 10 minutes and will be upgraded automatically; you receive a confirmation e-mail once the process is completed."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:138
msgid "Your database will be taken offline during the upgrade (usually between 30min up to several hours for big databases), so make sure to plan your migration during non-business hours."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:144
msgid "Duplicating a database"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:146
msgid "Database duplication, renaming, custom DNS, etc. is not available for trial databases on our Online platform. Paid Databases and \"One App Free\" database can duplicate without problem."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:151
msgid "In the line of the database you want to duplicate, you will have a few buttons. To duplicate your database, just click **Duplicate**. You will have to give a name to your duplicate, then click **Duplicate Database**."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:158
msgid "If you do not check the \"For testing purposes\" checkbox when duplicating a database, all external communication will remain active:"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:161
msgid "Emails are sent"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:163
msgid "Payments are processed (in the e-commerce or Subscriptions apps, for example)"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:166
msgid "Delivery orders (shipping providers) are sent"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:168
msgid "Etc."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:170
msgid "Make sure to check the checkbox \"For testing purposes\" if you want these behaviours to be disabled."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:173
msgid "After a few seconds, you will be logged in your duplicated database. Notice that the url uses the name you chose for your duplicated database."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:178
msgid "Duplicate databases expire automatically after 15 days."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:186
msgid "Rename a Database"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:188
msgid "To rename your database, make sure you are connected to the database you want to rename, access the `database management page <https://www.odoo.com/my/databases>`__ and click **Rename**. You will have to give a new name to your database, then click **Rename Database**."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:199
msgid "Deleting a Database"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:201
msgid "You can only delete databases of which you are the administrator."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:203
msgid "When you delete your database all the data will be permanently lost. The deletion is instant and for all the Users. We advise you to do an instant backup of your database before deleting it, since the last automated daily backup may be several hours old at that point."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:209
msgid "From the `database management page <https://www.odoo.com/my/databases>`__, on the line of the database you want to delete, click on the \"Delete\" button."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:216
msgid "Read carefully the warning message that will appear and proceed only if you fully understand the implications of deleting a database:"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:222
msgid "After a few seconds, the database will be deleted and the page will reload automatically."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:226
msgid "If you need to re-use this database name, it will be immediately available."
msgstr ""
#: ../../content/administration/db_management/db_online.rst:228
msgid "It is not possible to delete a database if it is expired or linked to a Subscription. In these cases contact `Odoo Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../content/administration/db_management/db_online.rst:232
msgid "If you want to delete your Account, please contact `Odoo Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:6
msgid "On-premises Database management"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:9
msgid "Register a database"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:11
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 Epiration Date in the About menu (Odoo 9) or in the Settings Dashboard (Odoo 10)."
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:19
msgid "Registration Error Message"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:21
msgid "If you are unable to register your database, you will likely encounter this message:"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:30
#: ../../content/administration/db_management/db_premise.rst:109
#: ../../content/administration/db_management/db_premise.rst:137
msgid "Solutions"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:32
msgid "Do you have a valid Enterprise subscription?"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:34
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/db_management/db_premise.rst:38
msgid "Have you already linked a database with your subscription reference?"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:40
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/db_management/db_premise.rst:44
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/db_management/db_premise.rst:51
msgid "A confirmation message will appear; make sure this is the correct database as it will be deactivated shortly:"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:58
msgid "Do you have the updated version of Odoo 9?"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:60
#: ../../content/administration/db_management/db_premise.rst:170
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/db_management/db_premise.rst:63
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/db_management/db_premise.rst:72
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/db_management/db_premise.rst:75
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/db_management/db_premise.rst:79
msgid "Check your network and firewall settings"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:81
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/db_management/db_premise.rst:85
msgid "services.odoo.com on port 443 (or 80)"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:86
msgid "services.openerp.com on port 443 (or 80) for older deployments"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:88
msgid "Once you activated your database, you must keep these ports open, as the Update notification runs once a week."
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:94
msgid "Error message due to too many users"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:96
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/db_management/db_premise.rst:105
msgid "When the message appears you have 30 days before the expiration. The countdown is updated everyday."
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:111
msgid "**Add more users** on your subscription: follow the link and Validate the upsell quotation and pay for the extra users."
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:113
msgid "**Deactivate users** as explained in this `documentation <documentation.html#deactivating-users>`_ and **Reject** the upsell quotation."
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:116
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/db_management/db_premise.rst:123
msgid "Database expired error message"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:125
msgid "If your database reaches its expiration date before your renew your subscription, you will encounter this message:"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:133
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/db_management/db_premise.rst:141
msgid "Renew your subscription: follow the link and renew your subscription - note that"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:140
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/db_management/db_premise.rst:143
msgid "Contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:145
msgid "None of those solutions worked for you? Please contact our `Support <https://www.odoo.com/help>`__"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:154
msgid "Duplicate a database"
msgstr ""
#: ../../content/administration/db_management/db_premise.rst:156
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/db_management/db_premise.rst:164
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/db_management/db_premise.rst:173
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/db_management/hosting_changes.rst:6
msgid "Hosting Changes"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:8
msgid "You may want to move your Odoo database from one hosting solution to another. Depending on the platforms, you have to do it by yourself or contact our support team first."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:12
msgid "From on-premises to Odoo Online"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:14
#: ../../content/administration/db_management/hosting_changes.rst:48
msgid "Odoo Online is not compatible with **non-standard apps**."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:16
msgid "Create a :ref:`duplicate <duplicate_premise>` of your database: in this duplicate, uninstall all the **non-standard apps**."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:17
msgid "Grab a \"dump with filestore\" of your database by using the Database Manager."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:18
#: ../../content/administration/db_management/hosting_changes.rst:51
msgid "**If you have time constraints, contact us earlier to schedule the transfer.**"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:19
#: ../../content/administration/db_management/hosting_changes.rst:52
msgid "`Create a support ticket <https://www.odoo.com/help>`_ and attach the dump (if the file is too large, use any file transfer service and attach the link to your ticket). Also include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com)."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:20
#: ../../content/administration/db_management/hosting_changes.rst:53
msgid "We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:21
#: ../../content/administration/db_management/hosting_changes.rst:54
msgid "It's done!"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:24
msgid "From on-premises to Odoo.sh"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:26
#: ../../content/administration/db_management/hosting_changes.rst:43
msgid "Follow the :ref:`Import your database section of the Odoo.sh documentation <odoo_sh_import_your_database>`."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:27
msgid "...and voilà!"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:30
msgid "From Odoo Online to on-premises"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:32
#: ../../content/administration/db_management/hosting_changes.rst:40
msgid "Log into `your Odoo Online user portal <https://accounts.odoo.com/my/databases/manage>`_ and look for the version number of your database."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:33
msgid "If your database does not run a :ref:`major version <supported_versions>` of Odoo, you cannot host it on-premises yet, you have to upgrade it first to a new major version. (*e.g.: If your database runs Odoo 12.3 which is not a major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:34
#: ../../content/administration/db_management/hosting_changes.rst:42
msgid "Download a backup of your database by clicking on the \"Gear\" icon next to your database name then :menuselection:`Download` (if the download fails due to your backup file being too large, contact `our support <https://www.odoo.com/help>`_)"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:35
#: ../../content/administration/db_management/hosting_changes.rst:60
msgid "Restore it from the database manager on your local server."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:38
msgid "From Odoo Online to Odoo.sh"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:41
msgid "If your database does not run a :ref:`major version <supported_versions>` of Odoo, you cannot host it on Odoo.sh yet, you have to upgrade it first to a new major version. (*e.g.: If your database runs Odoo 12.3 which is not a major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:46
msgid "From Odoo.sh to Odoo Online"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:50
msgid "Uninstall all the **non-standard apps**: test it in a staging build first, then do it in your production build."
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:57
msgid "From Odoo.sh to on-premises"
msgstr ""
#: ../../content/administration/db_management/hosting_changes.rst:59
msgid "Grab a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`."
msgstr ""
#: ../../content/administration/db_upgrade.rst:16
#: ../../content/administration/odoo_sh/advanced/containers.rst:7
#: ../../content/administration/odoo_sh/advanced/submodules.rst:9
#: ../../content/administration/odoo_sh/getting_started/branches.rst:7
#: ../../content/administration/odoo_sh/getting_started/builds.rst:9
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:7
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9
#: ../../content/administration/odoo_sh/getting_started/settings.rst:7
#: ../../content/administration/odoo_sh/getting_started/status.rst:7
#: ../../content/administration/odoo_sh/overview.rst:4
msgid "Overview"
msgstr ""
#: ../../content/administration/db_upgrade.rst:21
msgid "The upgrade process"
msgstr ""
#: ../../content/administration/db_upgrade.rst:23
msgid "This documentation is for our *On-Premise* (self-hosted) and *Odoo.sh* customers. If you are hosted Online, please check our :ref:`instruction page for our Online (SaaS) customers <upgrade_button>`."
msgstr ""
#: ../../content/administration/db_upgrade.rst:29
msgid "Definition"
msgstr ""
#: ../../content/administration/db_upgrade.rst:31
msgid "An upgrade is switching to a newer version of Odoo (e.g., Odoo 13.0 to Odoo 14.0)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:33
msgid "An upgrade does not cover:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:35
msgid "changing :ref:`Editions <db-upgrade/faq/editions-change>` (i.e., Community to Enterprise edition)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:36
msgid "switching :ref:`hosting type <db-upgrade/faq/hosting-types-switch>` (i.e., On-Premise to Online or Odoo.sh)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:38
msgid "migration from another ERP to Odoo"
msgstr ""
#: ../../content/administration/db_upgrade.rst:40
#: ../../content/administration/db_upgrade.rst:98
#: ../../content/administration/db_upgrade.rst:230
#: ../../content/administration/db_upgrade.rst:360
#: ../../content/administration/db_upgrade.rst:369
#: ../../content/administration/db_upgrade.rst:381
msgid "|assistance-contact|"
msgstr ""
#: ../../content/administration/db_upgrade.rst:45
msgid "Process workflow"
msgstr ""
#: ../../content/administration/db_upgrade.rst:47
msgid "The upgrade process in a nutshell:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:49
msgid "You create a test upgrade request."
msgstr ""
#: ../../content/administration/db_upgrade.rst:0
msgid "The request is processed by Odoo:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:0
msgid "This happens via an automated process that runs the database through an upgrade script and takes between 20 and 120 minutes. Only if an issue(s) arises will we have to intervene manually and adjust the script specifically to your database until the upgrade succeeds."
msgstr ""
#: ../../content/administration/db_upgrade.rst:54
msgid "Odoo delivers a test database."
msgstr ""
#: ../../content/administration/db_upgrade.rst:55
msgid "You test your database for possible discrepancies (see :ref:`db-upgrade/test-guidance`)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:56
msgid "If there are any discrepancies, you report them to the Upgrade support team via the :ref:`Help portal <db-upgrade/test-assistance>`."
msgstr ""
#: ../../content/administration/db_upgrade.rst:58
msgid "We will fix the issues and send you a new test database."
msgstr ""
#: ../../content/administration/db_upgrade.rst:59
msgid "Once you completed the testing and are happy with the result, you decide on a date and time when you stop users from accessing Odoo, freeze all data entries and create an upgrade request for the production upgrade."
msgstr ""
#: ../../content/administration/db_upgrade.rst:62
msgid "Odoo delivers the production database through the automated process."
msgstr ""
#: ../../content/administration/db_upgrade.rst:63
msgid "You restore it in your Production environment a few short hours later and continue working on the newly upgraded database."
msgstr ""
#: ../../content/administration/db_upgrade.rst:69
msgid "Service Level Agreement"
msgstr ""
#: ../../content/administration/db_upgrade.rst:72
msgid "What is covered by the Enterprise Licence?"
msgstr ""
#: ../../content/administration/db_upgrade.rst:74
msgid "Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise (Self-Hosting) enjoy the following service at all times."
msgstr ""
#: ../../content/administration/db_upgrade.rst:77
msgid "The upgrade of:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:79
msgid "standard applications"
msgstr ""
#: ../../content/administration/db_upgrade.rst:80
msgid "Studio customization (as long as the Studio app is still active)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:81
msgid "customizations done by our consulting and developer services *if* they are covered by a ‘Maintenance of Customisations’ subscription"
msgstr ""
#: ../../content/administration/db_upgrade.rst:84
msgid "The Upgrade Service is limited to the technical conversion and adaptation of your database (standard modules and data) to make it compatible with the targeted version."
msgstr ""
#: ../../content/administration/db_upgrade.rst:88
msgid "What upgrading does NOT cover"
msgstr ""
#: ../../content/administration/db_upgrade.rst:90
msgid "The cleaning of pre-existing data & configuration while upgrading"
msgstr ""
#: ../../content/administration/db_upgrade.rst:91
msgid "Any new developments and/or upgrade of your own :ref:`custom modules <db-upgrade/faq/custom-modules>`"
msgstr ""
#: ../../content/administration/db_upgrade.rst:93
msgid "`Training <https://www.odoo.com/learn>`_ on the new version"
msgstr ""
#: ../../content/administration/db_upgrade.rst:95
msgid "You can get more information about your Enterprise Licence on our :ref:`Odoo Enterprise Subscription Agreement <upgrade>` page."
msgstr ""
#: ../../content/administration/db_upgrade.rst:103
#: ../../content/administration/odoo_sh/getting_started.rst:4
msgid "Get started"
msgstr ""
#: ../../content/administration/db_upgrade.rst:105
msgid "The upgrade process varies depending on where your database is hosted."
msgstr ""
#: ../../content/administration/db_upgrade.rst:110
msgid "Online (SaaS)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:112
msgid "If you are hosted Online, please check our :ref:`instruction page for our Online (SaaS) customers <upgrade_button>`."
msgstr ""
#: ../../content/administration/db_upgrade.rst:118
msgid "Odoo.sh"
msgstr ""
#: ../../content/administration/db_upgrade.rst:120
msgid "If you are Odoo.sh hosted, check our :doc:`specific instructions to be able to upgrade <odoo_sh/advanced/upgrade_your_database>`."
msgstr ""
#: ../../content/administration/db_upgrade.rst:126
msgid "On-Premise"
msgstr ""
#: ../../content/administration/db_upgrade.rst:128
msgid "There are two possibilities:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:130
msgid "Via the interface of our `website form <https://upgrade.odoo.com>`_"
msgstr ""
#: ../../content/administration/db_upgrade.rst:0
msgid "For technically-advanced users and partners, via the following command line (to be used on the machine where your database is hosted):"
msgstr ""
#: ../../content/administration/db_upgrade.rst:0
msgid "``python <(curl -s beta.upgrade.odoo.com/upgrade) test -d <your db name> -t 14.0``"
msgstr ""
#: ../../content/administration/db_upgrade.rst:136
msgid "What does it do?"
msgstr ""
#: ../../content/administration/db_upgrade.rst:138
msgid "The above command will dump your database to a file, then send it to the upgrade platform for upgrade, displaying you the live logs, then restore the upgraded database back on your server as a duplicate test database."
msgstr ""
#: ../../content/administration/db_upgrade.rst:145
msgid "Steps"
msgstr ""
#: ../../content/administration/db_upgrade.rst:150
msgid "The testing phase"
msgstr ""
#: ../../content/administration/db_upgrade.rst:155
msgid "Test process"
msgstr ""
#: ../../content/administration/db_upgrade.rst:157
msgid "Also referred to as the pre-production phase, the test phase allows you to review an upgraded version of your database without affecting your production database in any way."
msgstr ""
#: ../../content/administration/db_upgrade.rst:160
msgid "We suggest that you run the test upgrade process at least once, but you can do it as often as you want (one at a time)."
msgstr ""
#: ../../content/administration/db_upgrade.rst:163
msgid "Once you receive your upgraded test database, you should check that all data, processes and functionality are still correct and working as expected."
msgstr ""
#: ../../content/administration/db_upgrade.rst:166
msgid "If you do find discrepancies, you'll be able to:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:0
msgid ":ref:`Report your issues <db-upgrade/test-assistance>`"
msgstr ""
#: ../../content/administration/db_upgrade.rst:0
msgid "and/or"
msgstr ""
#: ../../content/administration/db_upgrade.rst:170
msgid "Ask for a new :ref:`test request <db-upgrade/test-db-request>` after the reported issues have been fixed in the upgrade script."
msgstr ""
#: ../../content/administration/db_upgrade.rst:173
msgid "When you do not find any discrepancies, you'll be able to:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:175
msgid "Move on to the upgrade of your :ref:`production database <db-upgrade/production-live>`."
msgstr ""
#: ../../content/administration/db_upgrade.rst:180
msgid "Request a test database"
msgstr ""
#: ../../content/administration/db_upgrade.rst:182
msgid "When filling the `website form <https://upgrade.odoo.com>`_, select *Testing* purpose."
msgstr ""
#: ../../content/administration/db_upgrade.rst:191
msgid "Test guidance"
msgstr ""
#: ../../content/administration/db_upgrade.rst:193
msgid "Every business and organization has its own operational needs and will have to test its specific Odoo instance respectively. However, we recommend you look at `the test scenario <https://drive.google.com/open?id=1Lm4JqbsHBirB1wMi14UChoz_YHLjx5ec>`_ we created, a high-level idea of what you should test and look out for."
msgstr ""
#: ../../content/administration/db_upgrade.rst:198
#: ../../content/administration/deployment/deploy.rst:408
msgid "Todo"
msgstr ""
#: ../../content/administration/db_upgrade.rst:198
msgid "change link \"test scenario\" once the related doc is published"
msgstr ""
#: ../../content/administration/db_upgrade.rst:203
#: ../../content/administration/db_upgrade.rst:262
#: ../../content/administration/db_upgrade.rst:394
msgid "Assistance"
msgstr ""
#: ../../content/administration/db_upgrade.rst:205
msgid "If you encounter issues or problems in the **test database**, please contact the Odoo Upgrade Support:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:208
#: ../../content/administration/db_upgrade.rst:267
msgid "Connect to our `Odoo Support page <https://www.odoo.com/help>`_."
msgstr ""
#: ../../content/administration/db_upgrade.rst:209
msgid "Under the *Ticket Description* section, select *An issue related to my upgrade* ticket type."
msgstr ""
#: ../../content/administration/db_upgrade.rst:216
msgid "If you choose another *Ticket Description* type, the request will be redirected to another team than the upgrade one and will slow down the processing and response time."
msgstr ""
#: ../../content/administration/db_upgrade.rst:219
#: ../../content/administration/db_upgrade.rst:275
msgid "Please provide as much detail as you can. Where applicable, illustrate the current and previous flows with videos and/or screenshots. This will avoid clarifying questions and speed up the resolution process significantly."
msgstr ""
#: ../../content/administration/db_upgrade.rst:228
msgid "The purpose of the test phase is not to correct existing data or configurations in your database."
msgstr ""
#: ../../content/administration/db_upgrade.rst:235
msgid "The production launch"
msgstr ""
#: ../../content/administration/db_upgrade.rst:240
msgid "Production goes live"
msgstr ""
#: ../../content/administration/db_upgrade.rst:242
msgid "The production upgrade request is when you decide to upgrade your current database with all your production data (invoices, VAT returns, inventories, current orders) to a new version of your choice."
msgstr ""
#: ../../content/administration/db_upgrade.rst:245
msgid "After your :ref:`tests <db-upgrade/steps-test>` are completed to your satisfaction, submit the request to upgrade your production database via our `website form <https://upgrade.odoo.com>`_. Select *Production* purpose."
msgstr ""
#: ../../content/administration/db_upgrade.rst:254
msgid "Going into production without first testing may lead to:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:256
msgid "business interruptions (e.g. no longer having the possibility to validate an action)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:257
msgid "poor customer experiences (e.g. an eCommerce website that does not work correctly)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:264
msgid "If you encounter issues or problems in the **production database**, please contact the **Odoo Support**:"
msgstr ""
#: ../../content/administration/db_upgrade.rst:268
msgid "Under the *Ticket Description* section, select the appropriate type related to your issue but **do not select** the option *An issue related to my upgrade*."
msgstr ""
#: ../../content/administration/db_upgrade.rst:272
msgid "After upgrading to production, the support will be provided by the Support team instead of the Upgrade team."
msgstr ""
#: ../../content/administration/db_upgrade.rst:284
msgid "If you choose *An issue related to my upgrade* as ticket type, the request will be redirected to another team than the support one and will slow down the processing and response time."
msgstr ""
#: ../../content/administration/db_upgrade.rst:290
msgid "FAQ"
msgstr ""
#: ../../content/administration/db_upgrade.rst:295
msgid "Why upgrade?"
msgstr ""
#: ../../content/administration/db_upgrade.rst:297
msgid "You benefit from the latest features of the :ref:`new major version <db-upgrade/faq/release-notes>` released by Odoo."
msgstr ""
#: ../../content/administration/db_upgrade.rst:299
msgid "If you are in an :ref:`unsupported version <db-upgrade/supported-versions>`, you get a new version with support."
msgstr ""
#: ../../content/administration/db_upgrade.rst:305
msgid "When to upgrade?"
msgstr ""
#: ../../content/administration/db_upgrade.rst:307
msgid "Whenever you want. You can make your upgrade request as soon as a new version is released on our `website form <https://upgrade.odoo.com>`_."
msgstr ""
#: ../../content/administration/db_upgrade.rst:313
msgid "Availability of the new version"
msgstr ""
#: ../../content/administration/db_upgrade.rst:315
msgid "Please kindly note that as soon as we announce the release of a new major version (usually at the end of year), the Upgrade Service team needs to adapt the upgrade scripts to it, which is why the new version is not immediately available for existing databases."
msgstr ""
#: ../../content/administration/db_upgrade.rst:322
msgid "Finalization of the upgrade (:abbr:`ETA (Estimated Time of Arrival)`)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:324
msgid "Unfortunately, it is impossible to give time estimates for every upgrade request. Odoo offers so many possibilities (e.g. branding, workflows, customization, etc) that it can get tricky to upgrade, and translate to the new structure. If you use multiple apps managing sensitive data (e.g., Accounting, Inventory, etc.), some cases may still require a human intervention, making the process slower."
msgstr ""
#: ../../content/administration/db_upgrade.rst:330
msgid "This is especially true during the first months following the release of a new major version, which can significantly lengthen the upgrade delay."
msgstr ""
#: ../../content/administration/db_upgrade.rst:333
msgid "In general, the ‘smaller’ the database, the quickest the upgrade. A single-user database that uses only CRM will be processed faster than a multi-company, multi-user database that uses Accounting, Sales, Purchase, and Manufacturing."
msgstr ""
#: ../../content/administration/db_upgrade.rst:337
msgid "So, in a nutshell, what can impact your upgrade lead time?"
msgstr ""
#: ../../content/administration/db_upgrade.rst:339
msgid "Source & targeted versions"
msgstr ""
#: ../../content/administration/db_upgrade.rst:340
msgid "Installed apps"
msgstr ""
#: ../../content/administration/db_upgrade.rst:341
msgid "Volume of data"
msgstr ""
#: ../../content/administration/db_upgrade.rst:342
msgid "Amount of customization (models, fields, methods, workflows, reports, website, etc.)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:343
msgid "Installation of new apps or configuration changes after the start of the test phase"
msgstr ""
#: ../../content/administration/db_upgrade.rst:345
msgid "Usually, the delays experienced during the first request (waiting time between the time you submitted your first request for a test upgrade) can generally give you an idea of the time to wait for the production request."
msgstr ""
#: ../../content/administration/db_upgrade.rst:352
msgid "Upgrade of the custom modules"
msgstr ""
#: ../../content/administration/db_upgrade.rst:354
msgid "As stated in our :doc:`../legal/terms/enterprise`, section :ref:`charges_standard`, this optional service is subject to additional fees."
msgstr ""
#: ../../content/administration/db_upgrade.rst:357
msgid "If you have a custom code, you can choose to have it upgraded by our services, by one of our `partners <https://www.odoo.com/partners>`_ or you can do it yourself."
msgstr ""
#: ../../content/administration/db_upgrade.rst:365
msgid "Editions change (from Community to Enterprise)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:367
msgid "An upgrade does not cover a change of `Editions <https://www.odoo.com/page/editions>`_"
msgstr ""
#: ../../content/administration/db_upgrade.rst:374
msgid "Switching the hosting types (Self-hosted vs Online vs Odoo.sh)"
msgstr ""
#: ../../content/administration/db_upgrade.rst:376
msgid "An upgrade does not cover a change of `Hosting types <https://www.odoo.com/page/hosting-types>`_."
msgstr ""
#: ../../content/administration/db_upgrade.rst:378
msgid "Open the following link to get :doc:`more information about how to change your hosting type <db_management/hosting_changes>`."
msgstr ""
#: ../../content/administration/db_upgrade.rst:386
msgid "Release Notes by version"
msgstr ""
#: ../../content/administration/db_upgrade.rst:388
msgid "Open our `Release Note <https://www.odoo.com/page/release-notes>`_ page to get a summary of the new features and improvements made in each version."
msgstr ""
#: ../../content/administration/db_upgrade.rst:399
msgid "Contact our Upgrade service support"
msgstr ""
#: ../../content/administration/db_upgrade.rst:401
msgid "Should you have any more questions about the upgrade, do not hesitate to send a message to `Odoo Upgrade Team <mailto:upgrade@odoo.com>`_. We will be very pleased to answer it as soon as possible."
msgstr ""
#: ../../content/administration/db_upgrade.rst:407
msgid "Supported versions"
msgstr ""
#: ../../content/administration/db_upgrade.rst:409
msgid "Please note that Odoo provides support and bug fixing only for the three last major versions of Odoo."
msgstr ""
#: ../../content/administration/db_upgrade.rst:411
msgid "This is a factor to take into consideration before upgrading. If you are on an older version, we suggest you to prefer the most recent version to benefit from a longer support (before having to upgrade again)."
msgstr ""
#: ../../content/administration/db_upgrade.rst:415
msgid "You can get more information about our :doc:`supported versions <../services/support/supported_versions>`."
msgstr ""
#: ../../content/administration/deployment.rst:3
msgid "Deployment"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:4
msgid "Deploying with Content Delivery Networks"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:9
msgid "Deploying with KeyCDN_"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:13
msgid "This document will guide you through the setup of a KeyCDN_ account with your Odoo powered website."
msgstr ""
#: ../../content/administration/deployment/cdn.rst:17
msgid "Step 1: Create a pull zone in the KeyCDN dashboard"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:22
msgid "When creating the zone, enable the CORS option in the :guilabel:`advanced features` submenu. (more on that later)"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:28
msgid "Once done, you'll have to wait a bit while KeyCDN_ is crawling your website."
msgstr ""
#: ../../content/administration/deployment/cdn.rst:33
msgid "a new URL has been generated for your Zone, in this case it is ``http://pulltest-b49.kxcdn.com``"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:37
msgid "Step 2: Configure the odoo instance with your zone"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:39
msgid "In the Odoo back end, go to the :guilabel:`Website Settings`: menu, then activate the CDN support and copy/paste your zone URL in the :guilabel:`CDN Base URL` field. This field is only visible and configurable if you have developer mode activated."
msgstr ""
#: ../../content/administration/deployment/cdn.rst:47
msgid "Now your website is using the CDN for the resources matching the :guilabel:`CDN filters` regular expressions."
msgstr ""
#: ../../content/administration/deployment/cdn.rst:50
msgid "You can have a look to the HTML of your website in order to check if the CDN integration is properly working."
msgstr ""
#: ../../content/administration/deployment/cdn.rst:58
msgid "Why should I activate CORS?"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:60
msgid "A security restriction in some browsers (Firefox and Chrome at time of writing) prevents a remotely linked CSS file to fetch relative resources on this same external server."
msgstr ""
#: ../../content/administration/deployment/cdn.rst:64
msgid "If you don't activate the CORS option in the CDN zone, the more obvious resulting problem on a default Odoo website will be the lack of font-awesome icons because the font file declared in the font-awesome CSS won't be loaded on the remote server."
msgstr ""
#: ../../content/administration/deployment/cdn.rst:69
msgid "Here's what you would see on your homepage in such a case:"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:74
msgid "A security error message will also appear in the browser's console:"
msgstr ""
#: ../../content/administration/deployment/cdn.rst:79
msgid "Enabling the CORS option in the CDN fixes this issue."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:4
msgid "Deploying Odoo"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:6
msgid "This document describes basic steps to set up Odoo in production or on an internet-facing server. It follows :ref:`installation <setup/install>`, and is not generally necessary for a development systems that is not exposed on the internet."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:11
msgid "If you are setting up a public server, be sure to check our :ref:`security` recommandations!"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:17
msgid "dbfilter"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:19
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/deployment/deploy.rst:23
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/deployment/deploy.rst:27
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/deployment/deploy.rst:33
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/deployment/deploy.rst:39
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/deployment/deploy.rst:44
msgid "Configuration samples"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:46
msgid "Show only databases with names beginning with 'mycompany'"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:48
#: ../../content/administration/deployment/deploy.rst:60
#: ../../content/administration/deployment/deploy.rst:155
#: ../../content/administration/deployment/deploy.rst:281
msgid "in ``/etc/odoo.conf`` set:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:55
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/deployment/deploy.rst:68
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 paramater to prevent listing your databases, and to block access to the database management screens. See also security_."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:78
#: ../../content/administration/install.rst:299
#: ../../content/administration/install.rst:460
#: ../../content/administration/install.rst:629
msgid "PostgreSQL"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:80
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/deployment/deploy.rst:84
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/deployment/deploy.rst:89
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/deployment/deploy.rst:92
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/deployment/deploy.rst:97
#: ../../content/administration/deployment/deploy.rst:147
#: ../../content/administration/deployment/deploy.rst:236
#: ../../content/administration/deployment/deploy.rst:276
msgid "Configuration sample"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:99
msgid "Allow tcp connection on localhost"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:100
msgid "Allow tcp connection from 192.168.1.x network"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:102
msgid "in ``/etc/postgresql/9.5/main/pg_hba.conf`` set:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:110
msgid "in ``/etc/postgresql/9.5/main/postgresql.conf`` set:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:121
msgid "Configuring Odoo"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:123
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/deployment/deploy.rst:128
msgid "The :ref:`packaged installers <setup/install/packaged>` will automatically create a new user (``odoo``) and set it as the database user."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:131
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/deployment/deploy.rst:136
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/deployment/deploy.rst:140
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/deployment/deploy.rst:144
msgid "the PostgreSQL user *must not* be a superuser"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:149
msgid "connect to a PostgreSQL server on 192.168.1.2"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:150
msgid "port 5432"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:151
msgid "using an 'odoo' user account,"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:152
msgid "with 'pwd' as a password"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:153
msgid "filtering only db with a name beginning with 'mycompany'"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:170
msgid "SSL Between Odoo and PostgreSQL"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:172
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 choosed out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or 'verify-full'"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:177
msgid "`PostgreSQL Doc <https://www.postgresql.org/docs/current/static/libpq-ssl.html>`_"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:182
msgid "Builtin server"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:184
msgid "Odoo includes built-in HTTP servers, using either multithreading or multiprocessing."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:187
msgid "For production use, it is recommended to use the multiprocessing server as it increases stability, makes somewhat better use of computing resources and can be better monitored and resource-restricted."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:191
msgid "Multiprocessing is enabled by configuring :option:`a non-zero number of worker processes <odoo-bin --workers>`, the number of workers should be based on the number of cores in the machine (possibly with some room for cron workers depending on how much cron work is predicted)"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:195
msgid "Worker limits can be configured based on the hardware configuration to avoid resources exhaustion"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:198
msgid "multiprocessing mode currently isn't available on Windows"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:202
msgid "Worker number calculation"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:204
msgid "Rule of thumb : (#CPU * 2) + 1"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:205
msgid "Cron workers need CPU"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:206
msgid "1 worker ~= 6 concurrent users"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:209
msgid "memory size calculation"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:211
msgid "We consider 20% of the requests are heavy requests, while 80% are simpler ones"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:212
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/deployment/deploy.rst:213
msgid "A lighter worker, in the same scenario, is estimated to consume around 150MB of RAM"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:215
msgid "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) + (heavy_worker_ratio * heavy_worker_ram_estimation) )"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:218
#: ../../content/administration/deployment/deploy.rst:375
msgid "LiveChat"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:220
msgid "In multiprocessing, a dedicated LiveChat worker is automatically started and listening on :option:`the longpolling port <odoo-bin --longpolling-port>` but the client will not connect to it."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:224
msgid "Instead you must have a proxy redirecting requests whose URL starts with ``/longpolling/`` to the longpolling port. Other request should be proxied to the :option:`normal HTTP port <odoo-bin --http-port>`"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:228
msgid "To achieve such a thing, you'll need to deploy a reverse proxy in front of Odoo, like nginx or apache. When doing so, you'll need to forward some more http Headers to Odoo, and activate the proxy_mode in Odoo configuration to have Odoo read those headers."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:238
msgid "Server with 4 CPU, 8 Thread"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:239
msgid "60 concurrent users"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:241
msgid "60 users / 6 = 10 <- theorical number of worker needed"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:242
msgid "(4 * 2) + 1 = 9 <- theorical maximal number of worker"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:243
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/deployment/deploy.rst:244
msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:246
msgid "in ``/etc/odoo.conf``:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:262
msgid "HTTPS"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:264
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/deployment/deploy.rst:269
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/deployment/deploy.rst:270
msgid "Set up the SSL termination proxy (`Nginx termination example`_)"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:271
msgid "Set up the proxying itself (`Nginx proxying example`_)"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:272
msgid "Your SSL termination proxy should also automatically redirect non-secure connections to the secure port"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:278
msgid "Redirect http requests to https"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:279
msgid "Proxy requests to odoo"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:287
msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:349
msgid "Odoo as a WSGI Application"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:351
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/deployment/deploy.rst:357
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/deployment/deploy.rst:362
msgid "Cron Workers"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:364
msgid "To run cron jobs for an Odoo deployment as a WSGI application requires"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:366
msgid "A classical Odoo (run via ``odoo-bin``)"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:367
msgid "Connected to the database in which cron jobs have to be run (via :option:`odoo-bin -d`)"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:369
msgid "Which should not be exposed to the network. To ensure cron runners are not network-accessible, it is possible to disable the built-in HTTP server entirely with :option:`odoo-bin --no-http` or setting ``http_enable = False`` in the configuration file"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:377
msgid "The second problematic subsystem for WSGI deployments is the LiveChat: where most HTTP connections are relatively short and quickly free up their worker process for the next request, LiveChat require a long-lived connection for each client in order to implement near-real-time notifications."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:382
msgid "This is in conflict with the process-based worker model, as it will tie up worker processes and prevent new users from accessing the system. However, those long-lived connections do very little and mostly stay parked waiting for notifications."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:387
msgid "The solutions to support livechat/motifications in a WSGI application are:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:389
msgid "Deploy a threaded version of Odoo (instread of a process-based preforking one) and redirect only requests to URLs starting with ``/longpolling/`` to that Odoo, this is the simplest and the longpolling URL can double up as the cron instance."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:393
msgid "Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting with ``/longpolling/`` to :option:`the longpolling port <odoo-bin --longpolling-port>`."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:398
msgid "Serving Static Files"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:400
msgid "For development convenience, Odoo directly serves all static files in its modules. This may not be ideal when it comes to performances, and static files should generally be served by a static HTTP server."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:404
msgid "Odoo static files live in each module's ``static/`` folder, so static files can be served by intercepting all requests to :samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) in the various addons paths."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:408
msgid "test whether it would be interesting to serve filestored attachments via this, and how (e.g. possibility of mapping ir.attachment id to filestore hash in the database?)"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:415
msgid "Security"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:417
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/deployment/deploy.rst:421
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/deployment/deploy.rst:427
msgid "When deploying an internet-facing server, please be sure to consider the following security-related topics:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:430
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/deployment/deploy.rst:433
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/deployment/deploy.rst:438
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/deployment/deploy.rst:442
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/deployment/deploy.rst:449
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/deployment/deploy.rst:455
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/deployment/deploy.rst:460
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/deployment/deploy.rst:464
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/deployment/deploy.rst:467
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/deployment/deploy.rst:474
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/deployment/deploy.rst:480
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/deployment/deploy.rst:484
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/deployment/deploy.rst:488
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/deployment/deploy.rst:492
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/deployment/deploy.rst:503
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/deployment/deploy.rst:514
msgid "If you are hosting multiple customers, isolate customer data and files from each other using containers or appropriate \"jail\" techniques."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:517
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/deployment/deploy.rst:524
msgid "Blocking Brute Force Attacks"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:525
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/deployment/deploy.rst:529
msgid "The log entries will have the following form."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:531
msgid "Failed login::"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:535
msgid "Successful login::"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:540
msgid "These logs can be easily analyzed by an intrusion prevention system such as `fail2ban`."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:542
msgid "For example, the following fail2ban filter definition should match a failed login::"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:549
msgid "This could be used with a jail definition to block the attacking IP on HTTP(S)."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:551
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/deployment/deploy.rst:568
msgid "Database Manager Security"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:570
msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:572
msgid "This setting is used on all database management screens (to create, delete, dump or restore databases)."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:575
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/deployment/deploy.rst:581
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/deployment/deploy.rst:587
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/deployment/deploy.rst:590
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/deployment/deploy.rst:595
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/deployment/deploy.rst:599
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/deployment/deploy.rst:603
msgid "It should be stored securely, and should be generated randomly e.g."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:609
msgid "which will generate a 32 characters pseudorandom printable string."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:612
msgid "Supported Browsers"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:614
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/deployment/deploy.rst:617
msgid "Here are the supported browsers:"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:619
msgid "Google Chrome"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:620
msgid "Mozilla Firefox"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:621
msgid "Microsoft Edge"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:622
msgid "Apple Safari"
msgstr ""
#: ../../content/administration/deployment/deploy.rst:624
msgid "Please make sure your browser is up-to-date and still supported by its publisher before filing a bug report."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:630
msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:634
msgid "to have multiple Odoo installations use the same PostgreSQL database, or to provide more computing resources to both software."
msgstr ""
#: ../../content/administration/deployment/deploy.rst:637
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/deployment/deploy.rst:641
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/deployment/email_gateway.rst:4
msgid "Odoo email gateway"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:6
msgid "The Odoo mail gateway allows you to inject directly all the received emails in Odoo."
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:8
msgid "Its principle is straightforward: your SMTP server executes the \"mailgate\" script for every new incoming email."
msgstr ""
#: ../../content/administration/deployment/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/deployment/email_gateway.rst:14
msgid "Prerequisites"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:15
msgid "Administrator access to the Odoo database."
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:16
msgid "Your own mail server such as Postfix or Exim."
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:17
msgid "Technical knowledge on how to configure an email server."
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:20
msgid "For Postfix"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:21
msgid "In you alias config (:file:`/etc/aliases`):"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:28
#: ../../content/administration/deployment/email_gateway.rst:42
msgid "Resources"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:30
msgid "`Postfix <http://www.postfix.org/documentation.html>`_"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:31
msgid "`Postfix aliases <http://www.postfix.org/aliases.5.html>`_"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:32
msgid "`Postfix virtual <http://www.postfix.org/virtual.8.html>`_"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:36
msgid "For Exim"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:44
msgid "`Exim <https://www.exim.org/docs.html>`_"
msgstr ""
#: ../../content/administration/deployment/email_gateway.rst:47
msgid "If you don't have access/manage your email server, use :ref:`inbound messages <discuss/email_servers/inbound_messages>`."
msgstr ""
#: ../../content/administration/enterprise.rst:6
msgid "From Community to Enterprise"
msgstr ""
#: ../../content/administration/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/enterprise.rst:12
#: ../../content/administration/enterprise.rst:31
#: ../../content/administration/enterprise.rst:63
#: ../../content/administration/enterprise.rst:80
msgid "Backup your community database"
msgstr ""
#: ../../content/administration/enterprise.rst:17
#: ../../content/administration/enterprise.rst:62
msgid "Shutdown your server"
msgstr ""
#: ../../content/administration/enterprise.rst:19
msgid "Install the web_enterprise module"
msgstr ""
#: ../../content/administration/enterprise.rst:21
msgid "Restart your server"
msgstr ""
#: ../../content/administration/enterprise.rst:23
msgid "Enter your Odoo Enterprise Subscription code"
msgstr ""
#: ../../content/administration/enterprise.rst:29
msgid "On Linux, using an installer"
msgstr ""
#: ../../content/administration/enterprise.rst:33
msgid "Stop the odoo service"
msgstr ""
#: ../../content/administration/enterprise.rst:39
msgid "Install the enterprise .deb (it should install over the community package)"
msgstr ""
#: ../../content/administration/enterprise.rst:45
msgid "Update your database to the enterprise packages using"
msgstr ""
#: ../../content/administration/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/enterprise.rst:57
msgid "On Linux, using the source code"
msgstr ""
#: ../../content/administration/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/enterprise.rst:64
msgid "Update the ``--addons-path`` parameter of your launch command (see :ref:`setup/install/source`)"
msgstr ""
#: ../../content/administration/enterprise.rst:65
msgid "Install the web_enterprise module by using"
msgstr ""
#: ../../content/administration/enterprise.rst:71
msgid "Depending on the size of your database, this may take some time."
msgstr ""
#: ../../content/administration/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/enterprise.rst:78
msgid "On Windows"
msgstr ""
#: ../../content/administration/enterprise.rst:82
msgid "Uninstall Odoo Community (using the Uninstall executable in the installation folder) - PostgreSQL will remain installed"
msgstr ""
#: ../../content/administration/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/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/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/install.rst:6
msgid "Installing Odoo"
msgstr ""
#: ../../content/administration/install.rst:8
msgid "There are multiple ways to install Odoo, or not install it at all, depending on the intended use case."
msgstr ""
#: ../../content/administration/install.rst:11
msgid "This documents attempts to describe most of the installation options."
msgstr ""
#: ../../content/administration/install.rst:14
msgid ":ref:`setup/install/online`"
msgstr ""
#: ../../content/administration/install.rst:14
msgid "The easiest way to use Odoo in production or to try it."
msgstr ""
#: ../../content/administration/install.rst:18
msgid ":ref:`setup/install/packaged`"
msgstr ""
#: ../../content/administration/install.rst:17
msgid "Suitable for testing Odoo, developing modules and can be used for long-term production use with additional deployment and maintenance work."
msgstr ""
#: ../../content/administration/install.rst:23
msgid ":ref:`setup/install/source`"
msgstr ""
#: ../../content/administration/install.rst:21
msgid "Provides greater flexibility: e.g. allow multiple running Odoo versions on the same system. Good for developing modules, can be used as base for production deployment."
msgstr ""
#: ../../content/administration/install.rst:28
msgid ":ref:`setup/install/docker`"
msgstr ""
#: ../../content/administration/install.rst:26
msgid "If you usually use docker_ for development or deployment, an official docker_ base image is available."
msgstr ""
#: ../../content/administration/install.rst:33
msgid "Editions"
msgstr ""
#: ../../content/administration/install.rst:35
msgid "There are two different Editions_ of Odoo: the Community and Enterprise versions. Using the Enterprise version is possible on our SaaS_ and accessing the code is restricted to Enterprise customers and partners. The Community version is freely available to anyone."
msgstr ""
#: ../../content/administration/install.rst:40
msgid "If you already use the Community version and wish to upgrade to Enterprise, please refer to :ref:`setup/enterprise` (except for :ref:`setup/install/source`)."
msgstr ""
#: ../../content/administration/install.rst:47
msgid "Online"
msgstr ""
#: ../../content/administration/install.rst:50
msgid "Demo"
msgstr ""
#: ../../content/administration/install.rst:52
msgid "To simply get a quick idea of Odoo, demo_ instances are available. They are shared instances which only live for a few hours, and can be used to browse around and try things out with no commitment."
msgstr ""
#: ../../content/administration/install.rst:56
msgid "Demo_ instances require no local installation, just a web browser."
msgstr ""
#: ../../content/administration/install.rst:59
msgid "SaaS"
msgstr ""
#: ../../content/administration/install.rst:61
msgid "Trivial to start with, fully managed and migrated by Odoo S.A., Odoo's SaaS_ provides private instances and starts out free. It can be used to discover and test Odoo and do non-code customizations (i.e. incompatible with custom modules or the Odoo Apps Store) without having to install it locally."
msgstr ""
#: ../../content/administration/install.rst:66
msgid "Can be used for both testing Odoo and long-term production use."
msgstr ""
#: ../../content/administration/install.rst:68
msgid "Like demo_ instances, SaaS_ instances require no local installation, a web browser is sufficient."
msgstr ""
#: ../../content/administration/install.rst:75
msgid "Packaged installers"
msgstr ""
#: ../../content/administration/install.rst:77
msgid "Odoo provides packaged installers for Windows, deb-based distributions (Debian, Ubuntu, …) and RPM-based distributions (Fedora, CentOS, RHEL, …) for both the Community and Enterprise versions."
msgstr ""
#: ../../content/administration/install.rst:81
msgid "These packages automatically set up all dependencies (for the Community version), but may be difficult to keep up-to-date."
msgstr ""
#: ../../content/administration/install.rst:84
msgid "Official Community packages with all relevant dependency requirements are available on our nightly_ server. Both Communtiy and Enterprise packages can be downloaded from our download_ page (you must to be logged in as a paying customer or partner to download the Enterprise packages)."
msgstr ""
#: ../../content/administration/install.rst:90
#: ../../content/administration/install.rst:226
msgid "Windows"
msgstr ""
#: ../../content/administration/install.rst:92
msgid "Download the installer from our nightly_ server (Community only) or the Windows installer from the download_ page (any edition)."
msgstr ""
#: ../../content/administration/install.rst:94
msgid "Execute the downloaded file."
msgstr ""
#: ../../content/administration/install.rst:0
msgid "On Windows 8 and later you may see a warning titled \"Windows protected your PC\"."
msgstr ""
#: ../../content/administration/install.rst:0
msgid "Click on **More Info** and then on **Run anyway**."
msgstr ""
#: ../../content/administration/install.rst:99
msgid "Accept the UAC_ prompt."
msgstr ""
#: ../../content/administration/install.rst:100
msgid "Go through the various installation steps."
msgstr ""
#: ../../content/administration/install.rst:102
msgid "Odoo will automatically be started at the end of the installation."
msgstr ""
#: ../../content/administration/install.rst:105
#: ../../content/administration/install.rst:390
msgid "Linux"
msgstr ""
#: ../../content/administration/install.rst:108
msgid "Debian/Ubuntu"
msgstr ""
#: ../../content/administration/install.rst:110
msgid "Odoo 14.0 'deb' package currently supports `Debian Buster`_, `Ubuntu 20.04`_ or above."
msgstr ""
#: ../../content/administration/install.rst:112
#: ../../content/administration/install.rst:172
#: ../../content/administration/install.rst:341
#: ../../content/administration/install.rst:512
#: ../../content/administration/install.rst:674
msgid "`wkhtmltopdf` is not installed through **pip** and must be installed manually in version `0.12.5 <the wkhtmltopdf download page_>`_ for it to support headers and footers. See our `wiki <https://github.com/odoo/odoo/wiki/Wkhtmltopdf>`_ for more details on the various versions."
msgstr ""
#: ../../content/administration/install.rst:118
#: ../../content/administration/install.rst:178
msgid "Repository"
msgstr ""
#: ../../content/administration/install.rst:120
msgid "Odoo S.A. provides a repository that can be used with Debian and Ubuntu distributions. It can be used to install *Odoo Community Edition* by executing the following commands:"
msgstr ""
#: ../../content/administration/install.rst:129
msgid "You can then use the usual `apt-get upgrade` command to keep your installation up-to-date."
msgstr ""
#: ../../content/administration/install.rst:131
msgid "At this moment, there is no nightly repository for the Enterprise Edition."
msgstr ""
#: ../../content/administration/install.rst:134
msgid "Deb Package"
msgstr ""
#: ../../content/administration/install.rst:136
msgid "Instead of using the repository as described above, the 'deb' packages for both the *Community* and *Enterprise* editions can be downloaded from the `official download page <download_>`_."
msgstr ""
#: ../../content/administration/install.rst:139
msgid "Next, execute the following commands:"
msgstr ""
#: ../../content/administration/install.rst:145
msgid "This will install Odoo as a service, create the necessary PostgreSQL_ user and automatically start the server."
msgstr ""
#: ../../content/administration/install.rst:148
msgid "The recommended `postgresql-server` package will be installed by the Debian Odoo package. The `--no-install-recommends` argument of the `apt-get` tool should be used if you plan to install the Postgresql server on another machine."
msgstr ""
#: ../../content/administration/install.rst:153
msgid "Fedora"
msgstr ""
#: ../../content/administration/install.rst:155
msgid "Odoo 14.0 'rpm' package supports Fedora 32."
msgstr ""
#: ../../content/administration/install.rst:157
msgid "The Odoo 14.0 rpm package does not support Fedora 33 or above."
msgstr ""
#: ../../content/administration/install.rst:160
#: ../../content/administration/install.rst:274
#: ../../content/administration/install.rst:438
#: ../../content/administration/install.rst:607
msgid "Prepare"
msgstr ""
#: ../../content/administration/install.rst:161
msgid "Odoo needs a `PostgreSQL`_ server to run properly. Make sure that the `sudo` command is available and well configured and, only then, execute the following command in order to install the PostgreSQL server:"
msgstr ""
#: ../../content/administration/install.rst:180
msgid "Odoo S.A. provides a repository that can be used with the Fedora distributions. It can be used to install *Odoo Community Edition* by executing the following commands:"
msgstr ""
#: ../../content/administration/install.rst:192
msgid "RPM package"
msgstr ""
#: ../../content/administration/install.rst:194
msgid "Instead of using the repository as described above, the 'rpm' packages for both the *Community* and *Enterprise* editions can be downloaded from the `official download page <download_>`_."
msgstr ""
#: ../../content/administration/install.rst:197
msgid "Once downloaded, the package can be installed using the 'dnf' package manager:"
msgstr ""
#: ../../content/administration/install.rst:209
msgid "Source Install"
msgstr ""
#: ../../content/administration/install.rst:211
msgid "The source \"installation\" is really about not installing Odoo, and running it directly from source instead."
msgstr ""
#: ../../content/administration/install.rst:214
msgid "This can be more convenient for module developers as the Odoo source is more easily accessible than using packaged installation (for information or to build this documentation and have it available offline)."
msgstr ""
#: ../../content/administration/install.rst:218
msgid "It also makes starting and stopping Odoo more flexible and explicit than the services set up by the packaged installations, and allows overriding settings using :ref:`command-line parameters <reference/cmdline>` without needing to edit a configuration file."
msgstr ""
#: ../../content/administration/install.rst:222
msgid "Finally it provides greater control over the system's set up, and allows to more easily keep (and run) multiple versions of Odoo side-by-side."
msgstr ""
#: ../../content/administration/install.rst:229
#: ../../content/administration/install.rst:393
#: ../../content/administration/install.rst:562
msgid "Fetch the sources"
msgstr ""
#: ../../content/administration/install.rst:231
#: ../../content/administration/install.rst:395
#: ../../content/administration/install.rst:564
msgid "There are two ways to obtain the source code of Odoo: as a zip **archive** or through **git**."
msgstr ""
#: ../../content/administration/install.rst:234
#: ../../content/administration/install.rst:398
#: ../../content/administration/install.rst:567
msgid "Archive"
msgstr ""
#: ../../content/administration/install.rst:236
#: ../../content/administration/install.rst:253
#: ../../content/administration/install.rst:400
#: ../../content/administration/install.rst:417
#: ../../content/administration/install.rst:569
#: ../../content/administration/install.rst:586
msgid "Community Edition:"
msgstr ""
#: ../../content/administration/install.rst:238
#: ../../content/administration/install.rst:244
#: ../../content/administration/install.rst:402
#: ../../content/administration/install.rst:408
#: ../../content/administration/install.rst:571
#: ../../content/administration/install.rst:577
msgid "`Official download page <download_>`_"
msgstr ""
#: ../../content/administration/install.rst:239
#: ../../content/administration/install.rst:403
#: ../../content/administration/install.rst:572
msgid "`GitHub repository <community-repository_>`_"
msgstr ""
#: ../../content/administration/install.rst:240
#: ../../content/administration/install.rst:404
#: ../../content/administration/install.rst:573
msgid "`Nightly server <nightly_>`_"
msgstr ""
#: ../../content/administration/install.rst:242
#: ../../content/administration/install.rst:406
#: ../../content/administration/install.rst:575
msgid "Enterprise Edition:"
msgstr ""
#: ../../content/administration/install.rst:245
#: ../../content/administration/install.rst:409
#: ../../content/administration/install.rst:578
msgid "`GitHub repository <enterprise-repository_>`_"
msgstr ""
#: ../../content/administration/install.rst:248
#: ../../content/administration/install.rst:412
#: ../../content/administration/install.rst:581
msgid "Git"
msgstr ""
#: ../../content/administration/install.rst:250
#: ../../content/administration/install.rst:414
#: ../../content/administration/install.rst:583
msgid "The following requires git_ to be installed on your machine and that you have basic knowledge of git commands."
msgstr ""
#: ../../content/administration/install.rst:260
#: ../../content/administration/install.rst:424
#: ../../content/administration/install.rst:593
msgid "Enterprise Edition: (see :ref:`setup/install/editions` to get access)"
msgstr ""
#: ../../content/administration/install.rst:266
#: ../../content/administration/install.rst:430
#: ../../content/administration/install.rst:599
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 version. Running the Enterprise version actually means running the server from the Community version with the addons-path option set to the folder with the Enterprise version. You need to clone both the Community and Enterprise repository to have a working Odoo Enterprise installation."
msgstr ""
#: ../../content/administration/install.rst:277
#: ../../content/administration/install.rst:441
#: ../../content/administration/install.rst:610
msgid "Python"
msgstr ""
#: ../../content/administration/install.rst:279
msgid "Odoo requires Python 3.6 or later to run. Visit `Python's download page <https://www.python.org/downloads/windows/>`_ to download and install the latest version of Python 3 on your machine."
msgstr ""
#: ../../content/administration/install.rst:282
msgid "During installation, check **Add Python 3 to PATH**, then click **Customize Installation** and make sure that **pip** is checked."
msgstr ""
#: ../../content/administration/install.rst:285
#: ../../content/administration/install.rst:446
#: ../../content/administration/install.rst:615
msgid "If Python 3 is already installed, make sure that the version is 3.6 or above, as previous versions are not compatible with Odoo."
msgstr ""
#: ../../content/administration/install.rst:292
#: ../../content/administration/install.rst:453
#: ../../content/administration/install.rst:622
msgid "Verify also that pip_ is installed for this version."
msgstr ""
#: ../../content/administration/install.rst:301
msgid "Odoo uses PostgreSQL as database management system. `Download and install PostgreSQL <https://www.postgresql.org/download/windows/>`_ (supported version: 10.0 and later)."
msgstr ""
#: ../../content/administration/install.rst:304
#: ../../content/administration/install.rst:471
#: ../../content/administration/install.rst:634
msgid "By default, the only user is `postgres` but Odoo forbids connecting as `postgres`, so you need to create a new PostgreSQL user:"
msgstr ""
#: ../../content/administration/install.rst:307
msgid "Add PostgreSQL's `bin` directory (by default: `C:\\\\Program Files\\\\PostgreSQL\\\\<version>\\\\bin`) to your `PATH`."
msgstr ""
#: ../../content/administration/install.rst:309
msgid "Create a postgres user with a password using the pg admin gui:"
msgstr ""
#: ../../content/administration/install.rst:311
msgid "Open **pgAdmin**."
msgstr ""
#: ../../content/administration/install.rst:312
msgid "Double-click the server to create a connection."
msgstr ""
#: ../../content/administration/install.rst:313
msgid "Select :menuselection:`Object --> Create --> Login/Group Role`."
msgstr ""
#: ../../content/administration/install.rst:314
msgid "Enter the username in the **Role Name** field (e.g. `odoo`)."
msgstr ""
#: ../../content/administration/install.rst:315
msgid "Open the **Definition** tab and enter the password (e.g. ``odoo``), then click **Save**."
msgstr ""
#: ../../content/administration/install.rst:316
msgid "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create database?** to `Yes`."
msgstr ""
#: ../../content/administration/install.rst:320
#: ../../content/administration/install.rst:483
#: ../../content/administration/install.rst:646
msgid "Dependencies"
msgstr ""
#: ../../content/administration/install.rst:322
msgid "Before installing the dependencies, you must download and install the `Build Tools for Visual Studio <https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2019>`_. When prompted, select **C++ build tools** in the **Workloads** tab and install them."
msgstr ""
#: ../../content/administration/install.rst:326
#: ../../content/administration/install.rst:497
#: ../../content/administration/install.rst:648
msgid "Odoo dependencies are listed in the `requirements.txt` file located at the root of the Odoo community directory."
msgstr ""
#: ../../content/administration/install.rst:329
#: ../../content/administration/install.rst:500
#: ../../content/administration/install.rst:651
msgid "It can be preferable to not mix python modules packages between different instances of Odoo or with your system. You can use virtualenv_ to create isolated Python environments."
msgstr ""
#: ../../content/administration/install.rst:332
msgid "Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file in a terminal **with Administrator privileges**:"
msgstr ""
#: ../../content/administration/install.rst:346
#: ../../content/administration/install.rst:517
#: ../../content/administration/install.rst:679
msgid "For languages with right-to-left interface (such as Arabic or Hebrew), the package `rtlcss` is needed:"
msgstr ""
#: ../../content/administration/install.rst:349
msgid "Download and install `nodejs <https://nodejs.org/en/download/>`_."
msgstr ""
#: ../../content/administration/install.rst:350
#: ../../content/administration/install.rst:521
#: ../../content/administration/install.rst:683
msgid "Install `rtlcss`:"
msgstr ""
#: ../../content/administration/install.rst:356
msgid "Edit the System Environment's variable `PATH` to add the folder where `rtlcss.cmd` is located (typically: `C:\\\\Users\\\\<user>\\\\AppData\\\\Roaming\\\\npm\\\\`)."
msgstr ""
#: ../../content/administration/install.rst:360
#: ../../content/administration/install.rst:528
#: ../../content/administration/install.rst:690
msgid "Running Odoo"
msgstr ""
#: ../../content/administration/install.rst:362
#: ../../content/administration/install.rst:530
#: ../../content/administration/install.rst:692
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.rst:365
#: ../../content/administration/install.rst:533
#: ../../content/administration/install.rst:695
msgid "To configure the server, you can either specify :ref:`command-line arguments <reference/cmdline/server>` or a :ref:`configuration file <reference/cmdline/config>`."
msgstr ""
#: ../../content/administration/install.rst:368
#: ../../content/administration/install.rst:536
#: ../../content/administration/install.rst:698
msgid "For the Enterprise edition, you must add the path to the `enterprise` addons to the `addons-path` argument. Note that it must come before the other paths in `addons-path` for addons to be loaded correctly."
msgstr ""
#: ../../content/administration/install.rst:372
#: ../../content/administration/install.rst:540
#: ../../content/administration/install.rst:702
msgid "Common necessary configurations are:"
msgstr ""
#: ../../content/administration/install.rst:374
msgid "PostgreSQL user and password."
msgstr ""
#: ../../content/administration/install.rst:375
#: ../../content/administration/install.rst:545
#: ../../content/administration/install.rst:707
msgid "Custom addon paths beyond the defaults, to load your own modules."
msgstr ""
#: ../../content/administration/install.rst:377
#: ../../content/administration/install.rst:547
#: ../../content/administration/install.rst:709
msgid "A typical way to run the server would be:"
msgstr ""
#: ../../content/administration/install.rst:384
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 default database to serve on `localhost:8069`. You can add other directory paths separated by a comma to ``addons`` at the end of the addons-path option."
msgstr ""
#: ../../content/administration/install.rst:443
msgid "Odoo requires Python 3.6 or later to run. Use your package manager to download and install Python 3 on your machine if it is not already done."
msgstr ""
#: ../../content/administration/install.rst:462
msgid "Odoo uses PostgreSQL as database management system. Use your package manager to download and install PostgreSQL (supported version: 10.0 and later)."
msgstr ""
#: ../../content/administration/install.rst:465
msgid "On Debian/Unbuntu, it can be achieved by executing the following:"
msgstr ""
#: ../../content/administration/install.rst:479
#: ../../content/administration/install.rst:642
msgid "Because your PostgreSQL user has the same name as your Unix login, you will be able to connect to the database without password."
msgstr ""
#: ../../content/administration/install.rst:485
msgid "For libraries using native code, it is necessary to install development tools and native dependencies before the Python dependencies of Odoo. They are available in `-dev` or `-devel` packages for Python, PostgreSQL, libxml2, libxslt1, libevent, libsasl2 and libldap2."
msgstr ""
#: ../../content/administration/install.rst:489
msgid "On Debian/Unbuntu, the following command should install all the required libraries:"
msgstr ""
#: ../../content/administration/install.rst:503
#: ../../content/administration/install.rst:654
msgid "Navigate to the path of your Odoo Community installation (`CommunityPath`) and run **pip** on the requirements file:"
msgstr ""
#: ../../content/administration/install.rst:520
msgid "Download and install **nodejs** and **npm** with your package manager."
msgstr ""
#: ../../content/administration/install.rst:542
#: ../../content/administration/install.rst:704
msgid "PostgreSQL user and password. Odoo has no defaults beyond `psycopg2's defaults <http://initd.org/psycopg/docs/module.html>`_: connects over a UNIX socket on port `5432` with the current user and no password."
msgstr ""
#: ../../content/administration/install.rst:554
#: ../../content/administration/install.rst:716
msgid "Where `CommunityPath` is the path of the Odoo Community installation and `mydb` is the default database to serve on `localhost:8069`. You can add other directory paths separated by a comma to ``addons`` at the end of the addons-path option."
msgstr ""
#: ../../content/administration/install.rst:559
msgid "Mac OS"
msgstr ""
#: ../../content/administration/install.rst:612
msgid "Odoo requires Python 3.6 or later to run. Use your preferred package manager (homebrew_, macports_) to download and install Python 3 on your machine if it is not already done."
msgstr ""
#: ../../content/administration/install.rst:631
msgid "Odoo uses PostgreSQL as database management system. Use `postgres.app <https://postgresapp.com>`_ to download and install PostgreSQL (supported version: 10.0 and later)."
msgstr ""
#: ../../content/administration/install.rst:663
msgid "Non-Python dependencies need to be installed with a package manager:"
msgstr ""
#: ../../content/administration/install.rst:665
msgid "Download and install the **Command Line Tools**:"
msgstr ""
#: ../../content/administration/install.rst:671
msgid "Download and install the package manager of your choice (homebrew_, macports_)."
msgstr ""
#: ../../content/administration/install.rst:672
msgid "Install non-python dependencies."
msgstr ""
#: ../../content/administration/install.rst:682
msgid "Download and install **nodejs** with your preferred package manager (homebrew_, macports_)."
msgstr ""
#: ../../content/administration/install.rst:724
#: ../../content/administration/update.rst:147
msgid "Docker"
msgstr ""
#: ../../content/administration/install.rst:726
msgid "The full documentation on how to use Odoo with Docker can be found on the official Odoo `docker image <https://registry.hub.docker.com/_/odoo/>`_ page."
msgstr ""
#: ../../content/administration/odoo_sh.rst:3
msgid "Odoo sh"
msgstr ""
#: ../../content/administration/odoo_sh/advanced.rst:4
msgid "Advanced"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/containers.rst:4
msgid "Containers"
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/14.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/cmdline>`."
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/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:110
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:358
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:487
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/advanced/upgrade_your_database.rst:4
msgid "Upgrade your database"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:9
msgid "Download and Upload your database"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:11
msgid "Download a dump of your database (from the :ref:`Builds view <odoosh-gettingstarted-builds-download-dump>`), choose the exact copy and without filestore options. Upload the .sql.gz dump on https://upgrade.odoo.com/upload and select the Testing Purpose. If you have custom code, you can choose to have it upgraded by us, or do it yourself. Once it's processed, you'll get a dump of the database in return."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:17
msgid "Do *not* upload *backups* of your production database (found in the Backups tab of the production branch) as these are incompatible with the Upgrade platform - they contain your complete sources, etc. that are not needed for the upgrade. Make sure to download a **Dump** instead - either through the Backups tab using the *Download Dump* button or through the Builds page by using the *Download Dump* entry of the contextual menu of your latest production build."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:23
msgid "Test your upgraded database"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:25
msgid "Create a staging branch that will run the upgraded database. Either make sure your production branch's code is compatible between the two Odoo versions and fork your production branch, or make a new staging branch containing the upgraded code."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:29
msgid "Once the staging build is done (it doesn't matter if it failed due to the version incompatibility), import your upgraded dump in the backups tab of the branch. The platform will automatically detect the version of the dump and change the version of Odoo's source code to the corresponding version for the build."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:33
msgid "Test the upgraded database and make sure everything runs as it's supposed to."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:36
msgid "Replace your existing production database"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:38
msgid "Once you've tested everything and you're satisfied, start the process over to get an up-to-date upgraded dump:"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:40
msgid "Make a new dump of your production database (as described in step 1)"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:41
msgid "Upload it on upgrade.odoo.com and select the Production purpose"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:42
msgid "Receive the newly upgraded dump and import it in your production branch. The build might get marked as failed because the platform will run it with the upgraded databases' Odoo version together with the old custom code."
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:44
msgid "Merge or commit the upgraded custom code in the production branch"
msgstr ""
#: ../../content/administration/odoo_sh/advanced/upgrade_your_database.rst:46
msgid "If anything goes wrong, remember you can restore a backup. The platform will always make one before you make any Odoo.sh operation on the production database. If the restored backup comes from a previous version, the platform will detect it and change the project's Odoo version back if it needs to."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:4
msgid "Branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:9
msgid "The branches view gives you an overview of the different branches your repository has."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:17
#: ../../content/administration/odoo_sh/getting_started/builds.rst:40
msgid "Stages"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:19
msgid "Odoo.sh offers three different stages for your branches: production, staging and development."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:21
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:29
#: ../../content/administration/odoo_sh/getting_started/builds.rst:43
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/cmdline>`."
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:61
msgid "Staging"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:62
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:66
msgid "The neutralization includes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:68
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:71
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:74
msgid "Setting payment acquirers and shipping providers in test mode."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:75
msgid "Disabling IAP services"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:77
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:82
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:80
#: ../../content/administration/odoo_sh/getting_started/settings.rst:52
msgid "Development"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:89
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:93
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:100
msgid "Similar to staging branches, the emails are not sent but are intercepted by a mailcatcher and scheduled actions are not triggered as often is the database is not in use."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:103
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:109
msgid "Merging your branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:110
msgid "You can merge your branches easily by drag and dropping them into each other."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:115
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:118
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:119
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:121
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:125
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:129
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:131
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:134
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:137
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:139
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:145
msgid "pass them manually from your staging to your production database, by copy/pasting them."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:150
msgid "Tabs"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:153
#: ../../content/administration/odoo_sh/getting_started/settings.rst:52
#: ../../content/administration/odoo_sh/getting_started/settings.rst:64
msgid "History"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:154
msgid "An overview of your branch history:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:156
msgid "The messages of the commits and their authors,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:157
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:162
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:170
#: ../../content/administration/odoo_sh/getting_started/settings.rst:60
#: ../../content/administration/odoo_sh/getting_started/settings.rst:72
msgid "Mails"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:171
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:180
msgid "Shell"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:181
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:187
#: ../../content/administration/odoo_sh/getting_started/branches.rst:203
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:192
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:196
msgid "Editor"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:197
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:207
#: ../../content/administration/odoo_sh/getting_started/settings.rst:74
msgid "Monitoring"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:208
msgid "This link contains various monitoring metrics of the current build."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:213
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:217
#: ../../content/administration/odoo_sh/getting_started/settings.rst:56
#: ../../content/administration/odoo_sh/getting_started/settings.rst:68
msgid "Logs"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:218
msgid "A viewer to have a look to your server logs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:223
msgid "Different logs are available:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:225
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:226
msgid "pip.log: The logs of the Python dependencies installation."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:227
msgid "odoo.log: The logs of the running server."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:228
msgid "update.log: The logs of the database updates."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:229
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:231
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:234
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:240
#: ../../content/administration/odoo_sh/getting_started/settings.rst:76
msgid "Backups"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:241
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:247
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:250
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:254
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:257
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:260
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:266
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:272
msgid "The *import database* feature accepts database archives in the format provided by:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:274
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:276
msgid "the Odoo online databases manager,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:277
msgid "the Odoo.sh backup download button of this *Backups* tab,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:278
msgid "the Odoo.sh dump download button in the :ref:`Builds view <odoosh-gettingstarted-builds>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:283
#: ../../content/administration/odoo_sh/getting_started/settings.rst:4
#: ../../content/administration/odoo_sh/getting_started/settings.rst:62
#: ../../content/administration/odoo_sh/getting_started/settings.rst:78
#: ../../content/administration/odoo_sh/getting_started/settings.rst:82
msgid "Settings"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:284
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:289
msgid "**Behaviour upon new commit**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:291
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:299
msgid "**Modules installation**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:301
msgid "Choose the modules to install automatically for your development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:306
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:308
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:310
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:313
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:318
msgid "**Test suite**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:320
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:324
msgid "**Odoo Version**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:326
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:329
msgid "In addition, for each version you have two options regarding the code update."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:331
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:333
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:338
msgid "**Custom domains**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:340
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:343
msgid "own or purchase the domain name,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:344
msgid "add the domain name in this list,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:345
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:348
msgid "For instance, to associate *www.mycompany.com* to your database *mycompany.odoo.com*:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:350
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:351
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:354
msgid "Bare domains (e.g. *mycompany.com*) are not accepted:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:356
msgid "they can only be configured using ``A`` records,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:357
msgid "``A`` records only accept IP addresses as value,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:358
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:361
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:363
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:370
msgid "**HTTPS/SSL**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:372
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:376
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:380
msgid "**SPF and DKIM compliance**"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:382
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 :ref:`Discuss app documentation <discuss-email_servers-spf-compliant>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:388
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:393
msgid "Shell commands"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:394
msgid "In the top right-hand corner of the view, different shell commands are available."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:399
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:405
msgid "Clone"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:406
msgid "Download the Git repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:412
msgid "Clones the repository *odoo/odoo*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:414
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:415
msgid ":code:`--branch`: checks out a specific branch of the repository, in this case *master*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:417
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:420
msgid "Fork"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:421
msgid "Create a new branch based on the current branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:427
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:433
msgid "Uploads the new branch *feature-1* on your remote repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:436
msgid "Merge"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:437
msgid "Merge the current branch in another branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:443
msgid "Merges the branch *staging-1* in the current branch."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:449
#: ../../content/administration/odoo_sh/getting_started/branches.rst:521
msgid "Uploads the changes you just added in the *master* branch on your remote repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:452
msgid "SSH"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:454
msgid "Setup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:455
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:458
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:460
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:463
msgid "Paste the copied content to your profile SSH keys and press \"Add\""
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:468
msgid "The key should appear below"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:474
msgid "Connection"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:476
msgid "To connect to your builds using ssh use the following command in a terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:482
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:487
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:491
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:496
msgid "Submodule"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:498
msgid "Add a branch from another repository in your current branch as a *submodule*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:500
msgid "*Submodules* allows you to use modules from other repositories in your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:502
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:509
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:515
msgid "Commits all your current changes."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:524
msgid "Delete"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:526
msgid "Delete a branch from your repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:532
msgid "Deletes the branch in your remote repository."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/branches.rst:538
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:19
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:21
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:25
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:28
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:31
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:34
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:45
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:48
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:51
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:54
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:57
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:63
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:66
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:69
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:72
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:75
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:82
msgid "Development builds create new databases, load the demo data and run the unit tests."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:84
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:87
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:89
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:93
msgid "Features"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/builds.rst:95
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:101
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:109
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:121
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:25
msgid "Authorize Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:27
msgid "Grant Odoo.sh the required accesses to your account by clicking the *Authorize* button."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:32
msgid "Odoo.sh basically needs:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:34
msgid "to know your Github login and email,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:35
msgid "to create a new repository in case you decide to start from scratch,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:36
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:37
msgid "to create a webhook to be notified each time you push changes,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:38
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:41
msgid "Submit your project"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:43
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:45
msgid "Then, choose a name or select the repository you want to use."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:47
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:49
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:51
msgid "It should be the code of your Enterprise subscription that includes Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:53
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 the full amount as back commission. Contact your sales representative or account manager in order to get it."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:56
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:58
msgid "it is not an existing subscription,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:59
msgid "it is not a partnership subscription,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:60
msgid "it is an enterprise subscription, but which does not include Odoo.sh,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:61
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:63
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:69
msgid "You're done !"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:71
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:79
msgid "Import your database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:81
msgid "You can import your database in your Odoo.sh project as long as this is an Odoo 10.0, 11.0 or above database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:84
msgid "Push your modules in production"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:86
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:90
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:94
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:97
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:101
msgid "Download a backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:104
msgid "On-premise databases"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:106
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:110
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:113
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:118
msgid "Choose a zip including the filestore as the backup format."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:124
msgid "Odoo Online databases"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:126
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:133
msgid "Saas releases (e.g. *saas-**) are not supported on Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:136
msgid "Upload the backup"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:138
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:143
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:149
msgid "Check your outgoing email servers"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:151
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` (:doc:`Developer mode </applications/general/developer_mode/activate>` must be activated)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:156
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:161
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:164
msgid "Check your scheduled actions"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:166
msgid "All scheduled actions are disabled after the import."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:168
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:172
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:177
msgid "Register your subscription"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:179
msgid "Your subscription is unlinked after the import."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/create.rst:181
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:184
msgid "If you plan to make it your production, unlink your former database from the subscription, and register the newly imported database. Read the :ref:`database registration documentation <db_premise>` for instructions."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:4
msgid "Your first module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:9
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:11
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:47
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:57
msgid "From your computer"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:60
msgid "Clone your Github repository on your computer:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:69
msgid "Create a new branch:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77
msgid "Create the module structure"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:80
msgid "Scaffolding the module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82
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:85
msgid "From the Odoo.sh editor, in a terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:91
msgid "Or, from your computer, if you have an :ref:`installation of Odoo <setup/install/source>`:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:97
msgid "If you do not want to bother installing Odoo on your computer, you can also :download:`download this module structure template <media/my_module.zip>` in which you replace every occurrences of *my_module* to the name of your choice."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:101
msgid "The below structure will be generated:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:124
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:128
msgid "Uncomment the content of the files:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:130
msgid "*models/models.py*, an example of model with its fields,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:132
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:134
msgid "*demo/demo.xml*, demo records for the above example model,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:136
msgid "*controllers/controllers.py*, an example of controller implementing some routes,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:138
msgid "*views/templates.xml*, two example qweb views used by the above controller routes,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:140
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:149
msgid "Manually"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:151
msgid "If you want to create your module structure manually, you can follow :doc:`Build an Odoo module </developer/howtos/backend>` to understand the structure of a module and the content of each file."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:156
msgid "Push the development branch"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:158
msgid "Stage the changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:164
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:392
msgid "Commit your changes"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:170
msgid "Push your changes to your remote repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:172
msgid "From an Odoo.sh editor terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:178
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:186
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:380
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:406
msgid "Or, from your computer terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:192
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:200
msgid "Test your module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:202
msgid "Your branch should appear in your development branches in your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:207
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:213
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:219
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:222
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:226
msgid "Test with the production data"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:228
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:230
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:233
msgid "You can either:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:235
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:240
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:245
#: ../../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:247
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:253
#: ../../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:258
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300
msgid "Install your module"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:260
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:264
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 :doc:`Developer mode </applications/general/developer_mode/activate>`"
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:314
msgid "From the Odoo.sh editor,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:313
msgid "browse to your module folder *~/src/user/my_module*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314
msgid "then, open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:319
msgid "Or, from your computer,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:317
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:318
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:321
msgid "Then, after the description field"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:327
msgid "Add a datetime field"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:333
msgid "Then, open the file *views/views.xml*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:462
msgid "After"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:341
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:468
msgid "Add"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:347
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:350
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:353
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:356
msgid "Open the module manifest *__manifest__.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:364
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:493
msgid "with"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:370
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:372
msgid "Browse to your Git folder."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:374
msgid "Then, from an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:386
msgid "Then, stage your changes to be committed"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:398
msgid "Push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:400
msgid "From an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:412
msgid "The platform will then create a new build for the branch *feature-1*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:417
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:423
msgid "Use an external Python library"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:425
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:428
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:430
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:433
msgid "Create a file *requirements.txt* in the root folder of your repository"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:435
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:437
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:445
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:448
msgid "Open the file *models/models.py*."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450
msgid "Before"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:483
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:485
msgid "Edit the module manifest *__manifest__.py*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:499
msgid "Stage and commit your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:507
msgid "Then, push your changes:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:509
msgid "In an Odoo.sh terminal:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/first_module.rst:515
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:50
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:53
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:57
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:60
msgid "The source code of your Github repository is located under */src/user*,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:61
msgid "The source code of Odoo is located under"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63
msgid "*/src/odoo* (`odoo/odoo <https://github.com/odoo/odoo>`_),"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64
msgid "*/src/enterprise* (`odoo/enterprise <https://github.com/odoo/enterprise>`_),"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:65
msgid "*/src/themes* (`odoo/design-themes <https://github.com/odoo/design-themes>`_)."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:67
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:72
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:78
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:85
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:94
msgid "You can also open a terminal and execute the command:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:103
msgid "Commit & Push your changes"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:105
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:107
msgid "Open a terminal (:menuselection:`File --> New --> Terminal`),"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108
msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109
msgid "Stage your changes using :code:`git add`,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110
msgid "Commit your changes using :code:`git commit`,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:111
msgid "Push your changes using :code:`git push https HEAD:<branch>`."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:113
msgid "In this last command,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:115
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:117
msgid "HEAD is the reference to the latest revision you committed,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:118
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:125
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:139
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:143
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:150
msgid "Consoles"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:152
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:160
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:166
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:171
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:177
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:187
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:195
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:9
msgid "The settings allow you to manage the configuration of your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:15
msgid "Project name"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:17
msgid "The name of your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:22
msgid "This defines the address that will be used to access your production database."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:24
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:30
msgid "Collaborators"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:32
msgid "Manage the Github users who can access your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:37
msgid "There are two levels of users:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:39
msgid "Admin: has access to all features of Odoo.sh."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:40
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:42
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:47
msgid "In addition, they cannot use the webshell nor have access to the server logs."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:50
msgid "User"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:50
msgid "Admin"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:52
#: ../../content/administration/odoo_sh/getting_started/settings.rst:52
#: ../../content/administration/odoo_sh/getting_started/settings.rst:54
#: ../../content/administration/odoo_sh/getting_started/settings.rst:54
#: ../../content/administration/odoo_sh/getting_started/settings.rst:56
#: ../../content/administration/odoo_sh/getting_started/settings.rst:56
#: ../../content/administration/odoo_sh/getting_started/settings.rst:58
#: ../../content/administration/odoo_sh/getting_started/settings.rst:58
#: ../../content/administration/odoo_sh/getting_started/settings.rst:60
#: ../../content/administration/odoo_sh/getting_started/settings.rst:60
#: ../../content/administration/odoo_sh/getting_started/settings.rst:62
#: ../../content/administration/odoo_sh/getting_started/settings.rst:62
#: ../../content/administration/odoo_sh/getting_started/settings.rst:64
#: ../../content/administration/odoo_sh/getting_started/settings.rst:64
#: ../../content/administration/odoo_sh/getting_started/settings.rst:66
#: ../../content/administration/odoo_sh/getting_started/settings.rst:68
#: ../../content/administration/odoo_sh/getting_started/settings.rst:70
#: ../../content/administration/odoo_sh/getting_started/settings.rst:72
#: ../../content/administration/odoo_sh/getting_started/settings.rst:74
#: ../../content/administration/odoo_sh/getting_started/settings.rst:76
#: ../../content/administration/odoo_sh/getting_started/settings.rst:78
#: ../../content/administration/odoo_sh/getting_started/settings.rst:78
#: ../../content/administration/odoo_sh/getting_started/settings.rst:80
#: ../../content/administration/odoo_sh/getting_started/settings.rst:80
#: ../../content/administration/odoo_sh/getting_started/settings.rst:82
msgid "X"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:54
#: ../../content/administration/odoo_sh/getting_started/settings.rst:66
msgid "1-click connect"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:58
#: ../../content/administration/odoo_sh/getting_started/settings.rst:70
msgid "Shell/SSH"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:64
msgid "Production & Staging"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:80
#: ../../content/administration/odoo_sh/getting_started/status.rst:4
msgid "Status"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:86
msgid "Public Access"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:88
msgid "Allow public access to your development builds."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:93
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:95
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:97
msgid "Production and staging builds are excluded, visitors can only see their status."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:103
msgid "Custom domains"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:105
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:112
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:116
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:123
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:128
msgid "To configure the deploy key for a private repository, proceed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:130
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:132
msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:133
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:135
msgid "copy the public key,"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:137
msgid "it should look like *ssh-rsa some...random...characters...here...==*"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:139
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:141
msgid "Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:142
msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:143
msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:144
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:147
msgid "Storage Size"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:149
msgid "This section shows the storage size used by your project."
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:154
msgid "Storage size is computed as follows:"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:156
msgid "the size of the PostgreSQL database"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:158
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:161
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:163
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:167
msgid "Database Workers"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:169
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:177
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:183
msgid "Staging Branches"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:185
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:192
msgid "Activation"
msgstr ""
#: ../../content/administration/odoo_sh/getting_started/settings.rst:194
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:9
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:4
msgid "Introduction to Odoo.sh"
msgstr ""
#: ../../content/administration/odoo_sh/overview/introduction.rst:11
msgid "The documentation will help you go live with your Odoo.sh project in no time."
msgstr ""
#: ../../content/administration/update.rst:6
msgid "Updating an Odoo installation"
msgstr ""
#: ../../content/administration/update.rst:9
msgid "Introduction"
msgstr ""
#: ../../content/administration/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/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/update.rst:17
msgid "The terminology surrounding software updates is often confusing, so here are some preliminary definitions:"
msgstr ""
#: ../../content/administration/update.rst:25
msgid "Updating (an Odoo installation)"
msgstr ""
#: ../../content/administration/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/update.rst:35
msgid "Upgrading (an Odoo database)"
msgstr ""
#: ../../content/administration/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/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/update.rst:43
msgid "In a nutshell"
msgstr ""
#: ../../content/administration/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/update.rst:49
msgid "The main reference for updating is logically our :ref:`installation guide <setup/install>`, which explains the common installation methods."
msgstr ""
#: ../../content/administration/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/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/update.rst:64
msgid "Step 1: Download an updated Odoo version"
msgstr ""
#: ../../content/administration/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/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/update.rst:73
msgid "Downloading an updated version is not necessary if you installed via Github (see below)"
msgstr ""
#: ../../content/administration/update.rst:77
msgid "Step 2: Make a backup of your database"
msgstr ""
#: ../../content/administration/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/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/update.rst:89
msgid "Step 3: Install the updated version"
msgstr ""
#: ../../content/administration/update.rst:91
msgid "Choose the method that matches your current installation:"
msgstr ""
#: ../../content/administration/update.rst:95
msgid "Packaged Installers"
msgstr ""
#: ../../content/administration/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/update.rst:106
msgid "Source Install (Tarball)"
msgstr ""
#: ../../content/administration/update.rst:107
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/update.rst:112
msgid "You will get a folder labelled 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/update.rst:118
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/update.rst:125
msgid "Source Install (Github)"
msgstr ""
#: ../../content/administration/update.rst:126
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/update.rst:134
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/update.rst:138
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/update.rst:143
msgid "Finally, restart the Odoo service or reboot the machine, and you should be done."
msgstr ""
#: ../../content/administration/update.rst:149
msgid "Please refer to our `Docker image documentation <https://hub.docker.com/_/odoo/>`_ for specific update instructions."
msgstr ""
Reference in New Issue Copy Permalink