# SOME DESCRIPTIVE TITLE. # Copyright (C) Odoo S.A. # This file is distributed under the same license as the Odoo package. # FIRST AUTHOR , YEAR. # # Translators: # Dennis Sluijk , 2022 # Martien van Geene , 2022 # Erwin van der Ploeg , 2022 # Yenthe Van Ginneken , 2022 # Martin Trigaux, 2022 # #, fuzzy msgid "" msgstr "" "Project-Id-Version: Odoo 15.0\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2022-04-08 13:26+0000\n" "PO-Revision-Date: 2022-03-18 14:59+0000\n" "Last-Translator: Martin Trigaux, 2022\n" "Language-Team: Dutch (https://www.transifex.com/odoo/teams/41243/nl/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Language: nl\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" #: ../../content/administration.rst:8 msgid "Install and Maintain" msgstr "" #: ../../content/administration.rst:10 msgid "" "These guides provide instructions on how to install, maintain and upgrade " "Odoo databases." msgstr "" #: ../../content/administration.rst:13 msgid "" ":doc:`History of Versions `" msgstr "" #: ../../content/administration/install.rst:5 msgid "Install" msgstr "Installeren" #: ../../content/administration/install/cdn.rst:3 msgid "Setting up a Content Delivery Network (CDN)" msgstr "" #: ../../content/administration/install/cdn.rst:8 msgid "Deploying with KeyCDN_" msgstr "" #: ../../content/administration/install/cdn.rst:12 msgid "" "This document will guide you through the setup of a KeyCDN_ account with " "your Odoo powered website." msgstr "" #: ../../content/administration/install/cdn.rst:16 msgid "Step 1: Create a pull zone in the KeyCDN dashboard" msgstr "" #: ../../content/administration/install/cdn.rst:21 msgid "" "When creating the zone, enable the CORS option in the :guilabel:`advanced " "features` submenu. (more on that later)" msgstr "" #: ../../content/administration/install/cdn.rst:27 msgid "" "Once done, you'll have to wait a bit while KeyCDN_ is crawling your website." msgstr "" #: ../../content/administration/install/cdn.rst:32 msgid "" "a new URL has been generated for your Zone, in this case it is " "``http://pulltest-b49.kxcdn.com``" msgstr "" #: ../../content/administration/install/cdn.rst:36 msgid "Step 2: Configure the odoo instance with your zone" msgstr "" #: ../../content/administration/install/cdn.rst:38 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/install/cdn.rst:46 msgid "" "Now your website is using the CDN for the resources matching the " ":guilabel:`CDN filters` regular expressions." msgstr "" #: ../../content/administration/install/cdn.rst:49 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/install/cdn.rst:57 msgid "Why should I activate CORS?" msgstr "" #: ../../content/administration/install/cdn.rst:59 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/install/cdn.rst:63 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/install/cdn.rst:68 msgid "Here's what you would see on your homepage in such a case:" msgstr "" #: ../../content/administration/install/cdn.rst:73 msgid "A security error message will also appear in the browser's console:" msgstr "" #: ../../content/administration/install/cdn.rst:78 msgid "Enabling the CORS option in the CDN fixes this issue." msgstr "" #: ../../content/administration/install/deploy.rst:3 msgid "System configuration" msgstr "" #: ../../content/administration/install/deploy.rst:5 msgid "" "This document describes basic steps to set up Odoo in production or on an " "internet-facing server. It follows :ref:`installation `, and " "is not generally necessary for a development systems that is not exposed on " "the internet." msgstr "" #: ../../content/administration/install/deploy.rst:10 msgid "" "If you are setting up a public server, be sure to check our :ref:`security` " "recommendations!" msgstr "" #: ../../content/administration/install/deploy.rst:15 msgid "dbfilter" msgstr "" #: ../../content/administration/install/deploy.rst:17 msgid "" "Odoo is a multi-tenant system: a single Odoo system may run and serve a " "number of database instances. It is also highly customizable, with " "customizations (starting from the modules being loaded) depending on the " "\"current database\"." msgstr "" #: ../../content/administration/install/deploy.rst:21 msgid "" "This is not an issue when working with the backend (web client) as a logged-" "in company user: the database can be selected when logging in, and " "customizations loaded afterwards." msgstr "" #: ../../content/administration/install/deploy.rst:25 msgid "" "However it is an issue for non-logged users (portal, website) which aren't " "bound to a database: Odoo needs to know which database should be used to " "load the website page or perform the operation. If multi-tenancy is not used" " that is not an issue, there's only one database to use, but if there are " "multiple databases accessible Odoo needs a rule to know which one it should " "use." msgstr "" #: ../../content/administration/install/deploy.rst:31 msgid "" "That is one of the purposes of :option:`--db-filter `:" " it specifies how the database should be selected based on the hostname " "(domain) that is being requested. The value is a `regular expression`_, " "possibly including the dynamically injected hostname (``%h``) or the first " "subdomain (``%d``) through which the system is being accessed." msgstr "" #: ../../content/administration/install/deploy.rst:37 msgid "" "For servers hosting multiple databases in production, especially if " "``website`` is used, dbfilter **must** be set, otherwise a number of " "features will not work correctly." msgstr "" #: ../../content/administration/install/deploy.rst:42 msgid "Configuration samples" msgstr "" #: ../../content/administration/install/deploy.rst:44 msgid "Show only databases with names beginning with 'mycompany'" msgstr "" #: ../../content/administration/install/deploy.rst:46 #: ../../content/administration/install/deploy.rst:58 #: ../../content/administration/install/deploy.rst:153 #: ../../content/administration/install/deploy.rst:276 msgid "in ``/etc/odoo.conf`` set:" msgstr "" #: ../../content/administration/install/deploy.rst:53 msgid "" "Show only databases matching the first subdomain after ``www``: for example " "the database \"mycompany\" will be shown if the incoming request was sent to" " ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " "``www2.mycompany.com`` or ``helpdesk.mycompany.com``." msgstr "" #: ../../content/administration/install/deploy.rst:67 msgid "" "Setting a proper :option:`--db-filter ` is an " "important part of securing your deployment. Once it is correctly working and" " only matching a single database per hostname, it is strongly recommended to" " block access to the database manager screens, and to use the ``--no-" "database-list`` startup parameter to prevent listing your databases, and to " "block access to the database management screens. See also security_." msgstr "" #: ../../content/administration/install/deploy.rst:76 #: ../../content/administration/install/install.rst:325 #: ../../content/administration/install/install.rst:488 #: ../../content/administration/install/install.rst:659 msgid "PostgreSQL" msgstr "" #: ../../content/administration/install/deploy.rst:78 msgid "" "By default, PostgreSQL only allows connection over UNIX sockets and loopback" " connections (from \"localhost\", the same machine the PostgreSQL server is " "installed on)." msgstr "" #: ../../content/administration/install/deploy.rst:82 msgid "" "UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " "machine, and is the default when no host is provided, but if you want Odoo " "and PostgreSQL to execute on different machines [#different-machines]_ it " "will need to `listen to network interfaces`_ [#remote-socket]_, either:" msgstr "" #: ../../content/administration/install/deploy.rst:87 msgid "" "Only accept loopback connections and `use an SSH tunnel`_ between the " "machine on which Odoo runs and the one on which PostgreSQL runs, then " "configure Odoo to connect to its end of the tunnel" msgstr "" #: ../../content/administration/install/deploy.rst:90 msgid "" "Accept connections to the machine on which Odoo is installed, possibly over " "ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" " to connect over the network" msgstr "" #: ../../content/administration/install/deploy.rst:95 #: ../../content/administration/install/deploy.rst:145 #: ../../content/administration/install/deploy.rst:231 #: ../../content/administration/install/deploy.rst:271 msgid "Configuration sample" msgstr "" #: ../../content/administration/install/deploy.rst:97 msgid "Allow tcp connection on localhost" msgstr "" #: ../../content/administration/install/deploy.rst:98 msgid "Allow tcp connection from 192.168.1.x network" msgstr "" #: ../../content/administration/install/deploy.rst:100 msgid "in ``/etc/postgresql/9.5/main/pg_hba.conf`` set:" msgstr "" #: ../../content/administration/install/deploy.rst:108 msgid "in ``/etc/postgresql/9.5/main/postgresql.conf`` set:" msgstr "" #: ../../content/administration/install/deploy.rst:119 msgid "Configuring Odoo" msgstr "" #: ../../content/administration/install/deploy.rst:121 msgid "" "Out of the box, Odoo connects to a local postgres over UNIX socket via port " "5432. This can be overridden using :ref:`the database options " "` when your Postgres deployment is not " "local and/or does not use the installation defaults." msgstr "" #: ../../content/administration/install/deploy.rst:126 msgid "" "The :ref:`packaged installers ` will automatically " "create a new user (``odoo``) and set it as the database user." msgstr "" #: ../../content/administration/install/deploy.rst:129 msgid "" "The database management screens are protected by the ``admin_passwd`` " "setting. This setting can only be set using configuration files, and is " "simply checked before performing database alterations. It should be set to a" " randomly generated value to ensure third parties can not use this " "interface." msgstr "" #: ../../content/administration/install/deploy.rst:134 msgid "" "All database operations use the :ref:`database options " "`, including the database management " "screen. For the database management screen to work requires that the " "PostgreSQL user have ``createdb`` right." msgstr "" #: ../../content/administration/install/deploy.rst:138 msgid "" "Users can always drop databases they own. For the database management screen" " to be completely non-functional, the PostgreSQL user needs to be created " "with ``no-createdb`` and the database must be owned by a different " "PostgreSQL user." msgstr "" #: ../../content/administration/install/deploy.rst:142 msgid "the PostgreSQL user *must not* be a superuser" msgstr "" #: ../../content/administration/install/deploy.rst:147 msgid "connect to a PostgreSQL server on 192.168.1.2" msgstr "" #: ../../content/administration/install/deploy.rst:148 msgid "port 5432" msgstr "" #: ../../content/administration/install/deploy.rst:149 msgid "using an 'odoo' user account," msgstr "" #: ../../content/administration/install/deploy.rst:150 msgid "with 'pwd' as a password" msgstr "" #: ../../content/administration/install/deploy.rst:151 msgid "filtering only db with a name beginning with 'mycompany'" msgstr "" #: ../../content/administration/install/deploy.rst:168 msgid "SSL Between Odoo and PostgreSQL" msgstr "" #: ../../content/administration/install/deploy.rst:170 msgid "" "Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." " in Odoo the db_sslmode control the ssl security of the connection with " "value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " "'verify-full'" msgstr "" #: ../../content/administration/install/deploy.rst:175 msgid "" "`PostgreSQL Doc `_" msgstr "" #: ../../content/administration/install/deploy.rst:180 msgid "Builtin server" msgstr "" #: ../../content/administration/install/deploy.rst:182 msgid "" "Odoo includes built-in HTTP servers, using either multithreading or " "multiprocessing." msgstr "" #: ../../content/administration/install/deploy.rst:185 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/install/deploy.rst:189 msgid "" "Multiprocessing is enabled by configuring :option:`a non-zero number of " "worker processes `, 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/install/deploy.rst:193 msgid "" "Worker limits can be configured based on the hardware configuration to avoid" " resources exhaustion" msgstr "" #: ../../content/administration/install/deploy.rst:196 msgid "multiprocessing mode currently isn't available on Windows" msgstr "" #: ../../content/administration/install/deploy.rst:199 msgid "Worker number calculation" msgstr "" #: ../../content/administration/install/deploy.rst:201 msgid "Rule of thumb : (#CPU * 2) + 1" msgstr "" #: ../../content/administration/install/deploy.rst:202 msgid "Cron workers need CPU" msgstr "" #: ../../content/administration/install/deploy.rst:203 msgid "1 worker ~= 6 concurrent users" msgstr "" #: ../../content/administration/install/deploy.rst:206 msgid "memory size calculation" msgstr "" #: ../../content/administration/install/deploy.rst:208 msgid "" "We consider 20% of the requests are heavy requests, while 80% are simpler " "ones" msgstr "" #: ../../content/administration/install/deploy.rst:209 msgid "" "A heavy worker, when all computed field are well designed, SQL requests are " "well designed, ... is estimated to consume around 1GB of RAM" msgstr "" #: ../../content/administration/install/deploy.rst:210 msgid "" "A lighter worker, in the same scenario, is estimated to consume around 150MB" " of RAM" msgstr "" #: ../../content/administration/install/deploy.rst:212 msgid "" "Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " "+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" msgstr "" #: ../../content/administration/install/deploy.rst:215 #: ../../content/administration/install/deploy.rst:369 msgid "LiveChat" msgstr "" #: ../../content/administration/install/deploy.rst:217 msgid "" "In multiprocessing, a dedicated LiveChat worker is automatically started and" " listening on :option:`the longpolling port ` " "but the client will not connect to it." msgstr "" #: ../../content/administration/install/deploy.rst:221 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 `" msgstr "" #: ../../content/administration/install/deploy.rst:225 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/install/deploy.rst:233 msgid "Server with 4 CPU, 8 Thread" msgstr "" #: ../../content/administration/install/deploy.rst:234 msgid "60 concurrent users" msgstr "" #: ../../content/administration/install/deploy.rst:236 msgid "60 users / 6 = 10 <- theoretical number of worker needed" msgstr "" #: ../../content/administration/install/deploy.rst:237 msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" msgstr "" #: ../../content/administration/install/deploy.rst:238 msgid "" "We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " "measure cpu load, and check if it's between 7 and 7.5 ." msgstr "" #: ../../content/administration/install/deploy.rst:239 msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3Go RAM for Odoo" msgstr "" #: ../../content/administration/install/deploy.rst:241 msgid "in ``/etc/odoo.conf``:" msgstr "" #: ../../content/administration/install/deploy.rst:257 msgid "HTTPS" msgstr "HTTPS" #: ../../content/administration/install/deploy.rst:259 msgid "" "Whether it's accessed via website/web client or web service, Odoo transmits " "authentication information in cleartext. This means a secure deployment of " "Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " "just about any SSL termination proxy, but requires the following setup:" msgstr "" #: ../../content/administration/install/deploy.rst:264 msgid "" "Enable Odoo's :option:`proxy mode `. This should only" " be enabled when Odoo is behind a reverse proxy" msgstr "" #: ../../content/administration/install/deploy.rst:265 msgid "Set up the SSL termination proxy (`Nginx termination example`_)" msgstr "" #: ../../content/administration/install/deploy.rst:266 msgid "Set up the proxying itself (`Nginx proxying example`_)" msgstr "" #: ../../content/administration/install/deploy.rst:267 msgid "" "Your SSL termination proxy should also automatically redirect non-secure " "connections to the secure port" msgstr "" #: ../../content/administration/install/deploy.rst:273 msgid "Redirect http requests to https" msgstr "" #: ../../content/administration/install/deploy.rst:274 msgid "Proxy requests to odoo" msgstr "" #: ../../content/administration/install/deploy.rst:282 msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" msgstr "" #: ../../content/administration/install/deploy.rst:343 msgid "Odoo as a WSGI Application" msgstr "" #: ../../content/administration/install/deploy.rst:345 msgid "" "It is also possible to mount Odoo as a standard WSGI_ application. Odoo " "provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " "That script should be customized (possibly after copying it from the setup " "directory) to correctly set the configuration directly in " ":mod:`odoo.tools.config` rather than through the command-line or a " "configuration file." msgstr "" #: ../../content/administration/install/deploy.rst:351 msgid "" "However the WSGI server will only expose the main HTTP endpoint for the web " "client, website and webservice API. Because Odoo does not control the " "creation of workers anymore it can not setup cron or livechat workers" msgstr "" #: ../../content/administration/install/deploy.rst:356 msgid "Cron Workers" msgstr "" #: ../../content/administration/install/deploy.rst:358 msgid "To run cron jobs for an Odoo deployment as a WSGI application requires" msgstr "" #: ../../content/administration/install/deploy.rst:360 msgid "A classical Odoo (run via ``odoo-bin``)" msgstr "" #: ../../content/administration/install/deploy.rst:361 msgid "" "Connected to the database in which cron jobs have to be run (via " ":option:`odoo-bin -d`)" msgstr "" #: ../../content/administration/install/deploy.rst:363 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/install/deploy.rst:371 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/install/deploy.rst:376 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/install/deploy.rst:381 msgid "" "The solutions to support livechat/motifications in a WSGI application are:" msgstr "" #: ../../content/administration/install/deploy.rst:383 msgid "" "Deploy a threaded version of Odoo (instead of a process-based preforking " "one) and redirect only requests to URLs starting with ``/longpolling/`` to " "that Odoo, this is the simplest and the longpolling URL can double up as the" " cron instance." msgstr "" #: ../../content/administration/install/deploy.rst:387 msgid "" "Deploy an evented Odoo via ``odoo-gevent`` and proxy requests starting with " "``/longpolling/`` to :option:`the longpolling port `." msgstr "" #: ../../content/administration/install/deploy.rst:392 msgid "Serving Static Files" msgstr "" #: ../../content/administration/install/deploy.rst:394 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/install/deploy.rst:398 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/install/deploy.rst:402 #: ../../content/administration/upgrade.rst:122 msgid "Todo" msgstr "Te doen" #: ../../content/administration/install/deploy.rst:402 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/install/deploy.rst:409 msgid "Security" msgstr "Beveiliging" #: ../../content/administration/install/deploy.rst:411 msgid "" "For starters, keep in mind that securing an information system is a " "continuous process, not a one-shot operation. At any moment, you will only " "be as secure as the weakest link in your environment." msgstr "" #: ../../content/administration/install/deploy.rst:415 msgid "" "So please do not take this section as the ultimate list of measures that " "will prevent all security problems. It's only intended as a summary of the " "first important things you should be sure to include in your security action" " plan. The rest will come from best security practices for your operating " "system and distribution, best practices in terms of users, passwords, and " "access control management, etc." msgstr "" #: ../../content/administration/install/deploy.rst:421 msgid "" "When deploying an internet-facing server, please be sure to consider the " "following security-related topics:" msgstr "" #: ../../content/administration/install/deploy.rst:424 msgid "" "Always set a strong super-admin admin password, and restrict access to the " "database management pages as soon as the system is set up. See " ":ref:`db_manager_security`." msgstr "" #: ../../content/administration/install/deploy.rst:427 msgid "" "Choose unique logins and strong passwords for all administrator accounts on " "all databases. Do not use 'admin' as the login. Do not use those logins for " "day-to-day operations, only for controlling/managing the installation. " "*Never* use any default passwords like admin/admin, even for test/staging " "databases." msgstr "" #: ../../content/administration/install/deploy.rst:432 msgid "" "Do **not** install demo data on internet-facing servers. Databases with demo" " data contain default logins and passwords that can be used to get into your" " systems and cause significant trouble, even on staging/dev systems." msgstr "" #: ../../content/administration/install/deploy.rst:436 msgid "" "Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " "hostname. See :ref:`db_filter`. You may also use :option:`-d ` " "to provide your own (comma-separated) list of available databases to filter " "from, instead of letting the system fetch them all from the database " "backend." msgstr "" #: ../../content/administration/install/deploy.rst:443 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 ` command-line " "option)" msgstr "" #: ../../content/administration/install/deploy.rst:449 msgid "" "Make sure the PostgreSQL user (:option:`--db_user `) is " "*not* a super-user, and that your databases are owned by a different user. " "For example they could be owned by the ``postgres`` super-user if you are " "using a dedicated non-privileged ``db_user``. See also " ":ref:`setup/deploy/odoo`." msgstr "" #: ../../content/administration/install/deploy.rst:454 msgid "" "Keep installations updated by regularly installing the latest builds, either" " via GitHub or by downloading the latest version from " "https://www.odoo.com/page/download or http://nightly.odoo.com" msgstr "" #: ../../content/administration/install/deploy.rst:458 msgid "" "Configure your server in multi-process mode with proper limits matching your" " typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." msgstr "" #: ../../content/administration/install/deploy.rst:461 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 ` option. See also " ":ref:`https_proxy`." msgstr "" #: ../../content/administration/install/deploy.rst:468 msgid "" "If you need to allow remote SSH access to your servers, make sure to set a " "strong password for **all** accounts, not just `root`. It is strongly " "recommended to entirely disable password-based authentication, and only " "allow public key authentication. Also consider restricting access via a VPN," " allowing only trusted IPs in the firewall, and/or running a brute-force " "detection system such as `fail2ban` or equivalent." msgstr "" #: ../../content/administration/install/deploy.rst:474 msgid "" "Consider installing appropriate rate-limiting on your proxy or firewall, to " "prevent brute-force attacks and denial of service attacks. See also " ":ref:`login_brute_force` for specific measures." msgstr "" #: ../../content/administration/install/deploy.rst:478 msgid "" "Many network providers provide automatic mitigation for Distributed Denial " "of Service attacks (DDOS), but this is often an optional service, so you " "should consult with them." msgstr "" #: ../../content/administration/install/deploy.rst:482 msgid "" "Whenever possible, host your public-facing demo/test/staging instances on " "different machines than the production ones. And apply the same security " "precautions as for production." msgstr "" #: ../../content/administration/install/deploy.rst:486 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 " "`_ may also be useful to implement per-process network access " "control." msgstr "" #: ../../content/administration/install/deploy.rst:497 msgid "" "If your public-facing Odoo server is behind a Web Application Firewall, a " "load-balancer, a transparent DDoS protection service (like CloudFlare) or a " "similar network-level device, you may wish to avoid direct access to the " "Odoo system. It is generally difficult to keep the endpoint IP addresses of " "your Odoo servers secret. For example they can appear in web server logs " "when querying public systems, or in the headers of emails posted from Odoo. " "In such a situation you may want to configure your firewall so that the " "endpoints are not accessible publicly except from the specific IP addresses " "of your WAF, load-balancer or proxy service. Service providers like " "CloudFlare usually maintain a public list of their IP address ranges for " "this purpose." msgstr "" #: ../../content/administration/install/deploy.rst:508 msgid "" "If you are hosting multiple customers, isolate customer data and files from " "each other using containers or appropriate \"jail\" techniques." msgstr "" #: ../../content/administration/install/deploy.rst:511 msgid "" "Setup daily backups of your databases and filestore data, and copy them to a" " remote archiving server that is not accessible from the server itself." msgstr "" #: ../../content/administration/install/deploy.rst:518 msgid "Blocking Brute Force Attacks" msgstr "" #: ../../content/administration/install/deploy.rst:519 msgid "" "For internet-facing deployments, brute force attacks on user passwords are " "very common, and this threat should not be neglected for Odoo servers. Odoo " "emits a log entry whenever a login attempt is performed, and reports the " "result: success or failure, along with the target login and source IP." msgstr "" #: ../../content/administration/install/deploy.rst:523 msgid "The log entries will have the following form." msgstr "" #: ../../content/administration/install/deploy.rst:525 msgid "Failed login::" msgstr "" #: ../../content/administration/install/deploy.rst:529 msgid "Successful login::" msgstr "" #: ../../content/administration/install/deploy.rst:534 msgid "" "These logs can be easily analyzed by an intrusion prevention system such as " "`fail2ban`." msgstr "" #: ../../content/administration/install/deploy.rst:536 msgid "" "For example, the following fail2ban filter definition should match a failed " "login::" msgstr "" #: ../../content/administration/install/deploy.rst:543 msgid "" "This could be used with a jail definition to block the attacking IP on " "HTTP(S)." msgstr "" #: ../../content/administration/install/deploy.rst:545 msgid "" "Here is what it could look like for blocking the IP for 15 minutes when 10 " "failed login attempts are detected from the same IP within 1 minute::" msgstr "" #: ../../content/administration/install/deploy.rst:559 msgid "Database Manager Security" msgstr "" #: ../../content/administration/install/deploy.rst:561 msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." msgstr "" #: ../../content/administration/install/deploy.rst:563 msgid "" "This setting is used on all database management screens (to create, delete, " "dump or restore databases)." msgstr "" #: ../../content/administration/install/deploy.rst:566 msgid "" "If the management screens must not be accessible at all, you should set " "``list_db`` configuration option to ``False``, to block access to all the " "database selection and management screens." msgstr "" #: ../../content/administration/install/deploy.rst:572 msgid "" "It is strongly recommended to disable the Database Manager for any internet-" "facing system! It is meant as a development/demo tool, to make it easy to " "quickly create and manage databases. It is not designed for use in " "production, and may even expose dangerous features to attackers. It is also " "not designed to handle large databases, and may trigger memory limits." msgstr "" #: ../../content/administration/install/deploy.rst:578 msgid "" "On production systems, database management operations should always be " "performed by the system administrator, including provisioning of new " "databases and automated backups." msgstr "" #: ../../content/administration/install/deploy.rst:581 msgid "" "Be sure to setup an appropriate ``db_name`` parameter (and optionally, " "``db_filter`` too) so that the system can determine the target database for " "each request, otherwise users will be blocked as they won't be allowed to " "choose the database themselves." msgstr "" #: ../../content/administration/install/deploy.rst:586 msgid "" "If the management screens must only be accessible from a selected set of " "machines, use the proxy server's features to block access to all routes " "starting with ``/web/database`` except (maybe) ``/web/database/selector`` " "which displays the database-selection screen." msgstr "" #: ../../content/administration/install/deploy.rst:590 msgid "" "If the database-management screen should be left accessible, the " "``admin_passwd`` setting must be changed from its ``admin`` default: this " "password is checked before allowing database-alteration operations." msgstr "" #: ../../content/administration/install/deploy.rst:594 msgid "It should be stored securely, and should be generated randomly e.g." msgstr "" #: ../../content/administration/install/deploy.rst:600 msgid "which will generate a 32 characters pseudorandom printable string." msgstr "" #: ../../content/administration/install/deploy.rst:603 msgid "Supported Browsers" msgstr "" #: ../../content/administration/install/deploy.rst:605 msgid "" "Odoo supports all the major desktop and mobile browsers available on the " "market, as long as they are supported by their publishers." msgstr "" #: ../../content/administration/install/deploy.rst:608 msgid "Here are the supported browsers:" msgstr "" #: ../../content/administration/install/deploy.rst:610 msgid "Google Chrome" msgstr "" #: ../../content/administration/install/deploy.rst:611 msgid "Mozilla Firefox" msgstr "" #: ../../content/administration/install/deploy.rst:612 msgid "Microsoft Edge" msgstr "" #: ../../content/administration/install/deploy.rst:613 msgid "Apple Safari" msgstr "" #: ../../content/administration/install/deploy.rst:615 msgid "" "Please make sure your browser is up-to-date and still supported by its " "publisher before filing a bug report." msgstr "" #: ../../content/administration/install/deploy.rst:620 msgid "Since Odoo 13.0, ES6 is supported. Therefore, IE support is dropped." msgstr "" #: ../../content/administration/install/deploy.rst:623 msgid "" "to have multiple Odoo installations use the same PostgreSQL database, or to " "provide more computing resources to both software." msgstr "" #: ../../content/administration/install/deploy.rst:626 msgid "" "technically a tool like socat_ can be used to proxy UNIX sockets across " "networks, but that is mostly for software which can only be used over UNIX " "sockets" msgstr "" #: ../../content/administration/install/deploy.rst:630 msgid "" "or be accessible only over an internal packet-switched network, but that " "requires secured switches, protections against `ARP spoofing`_ and precludes" " usage of WiFi. Even over secure packet-switched networks, deployment over " "HTTPS is recommended, and possible costs are lowered as \"self-signed\" " "certificates are easier to deploy on a controlled environment than over the " "internet." msgstr "" #: ../../content/administration/install/email_gateway.rst:3 msgid "Email gateway" msgstr "" #: ../../content/administration/install/email_gateway.rst:5 msgid "" "The Odoo mail gateway allows you to inject directly all the received emails " "in Odoo." msgstr "" #: ../../content/administration/install/email_gateway.rst:7 msgid "" "Its principle is straightforward: your SMTP server executes the \"mailgate\"" " script for every new incoming email." msgstr "" #: ../../content/administration/install/email_gateway.rst:9 msgid "" "The script takes care of connecting to your Odoo database through XML-RPC, " "and send the emails via the `MailThread.message_process()` feature." msgstr "" #: ../../content/administration/install/email_gateway.rst:13 msgid "Prerequisites" msgstr "Vereisten" #: ../../content/administration/install/email_gateway.rst:14 msgid "Administrator access to the Odoo database." msgstr "" #: ../../content/administration/install/email_gateway.rst:15 msgid "Your own mail server such as Postfix or Exim." msgstr "" #: ../../content/administration/install/email_gateway.rst:16 msgid "Technical knowledge on how to configure an email server." msgstr "" #: ../../content/administration/install/email_gateway.rst:19 msgid "For Postfix" msgstr "" #: ../../content/administration/install/email_gateway.rst:20 msgid "In you alias config (:file:`/etc/aliases`):" msgstr "" #: ../../content/administration/install/email_gateway.rst:27 #: ../../content/administration/install/email_gateway.rst:41 msgid "Resources" msgstr "Resources" #: ../../content/administration/install/email_gateway.rst:29 msgid "`Postfix `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:30 msgid "`Postfix aliases `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:31 msgid "`Postfix virtual `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:35 msgid "For Exim" msgstr "" #: ../../content/administration/install/email_gateway.rst:43 msgid "`Exim `_" msgstr "" #: ../../content/administration/install/email_gateway.rst:46 msgid "" "If you don't have access/manage your email server, use :ref:`inbound " "messages `." msgstr "" #: ../../content/administration/install/install.rst:6 msgid "Installing Odoo" msgstr "" #: ../../content/administration/install/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/install.rst:11 msgid "This documents attempts to describe most of the installation options." msgstr "" #: ../../content/administration/install/install.rst:14 msgid ":ref:`setup/install/online`" msgstr "" #: ../../content/administration/install/install.rst:14 msgid "The easiest way to use Odoo in production or to try it." msgstr "" #: ../../content/administration/install/install.rst:18 msgid ":ref:`setup/install/packaged`" msgstr "" #: ../../content/administration/install/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/install.rst:23 msgid ":ref:`setup/install/source`" msgstr "" #: ../../content/administration/install/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/install.rst:28 msgid ":ref:`setup/install/docker`" msgstr "" #: ../../content/administration/install/install.rst:26 msgid "" "If you usually use docker_ for development or deployment, an official " "docker_ base image is available." msgstr "" #: ../../content/administration/install/install.rst:33 msgid "Editions" msgstr "" #: ../../content/administration/install/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/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/install.rst:47 msgid "Online" msgstr "Online" #: ../../content/administration/install/install.rst:50 msgid "Demo" msgstr "Demo" #: ../../content/administration/install/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/install.rst:56 msgid "Demo_ instances require no local installation, just a web browser." msgstr "" #: ../../content/administration/install/install.rst:59 msgid "SaaS" msgstr "" #: ../../content/administration/install/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/install.rst:66 msgid "Can be used for both testing Odoo and long-term production use." msgstr "" #: ../../content/administration/install/install.rst:68 msgid "" "Like demo_ instances, SaaS_ instances require no local installation, a web " "browser is sufficient." msgstr "" #: ../../content/administration/install/install.rst:75 msgid "Packaged installers" msgstr "" #: ../../content/administration/install/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/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/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/install.rst:90 #: ../../content/administration/install/install.rst:252 msgid "Windows" msgstr "" #: ../../content/administration/install/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/install.rst:94 msgid "Execute the downloaded file." msgstr "" #: ../../content/administration/install/install.rst:0 msgid "" "On Windows 8 and later you may see a warning titled \"Windows protected your" " PC\"." msgstr "" #: ../../content/administration/install/install.rst:0 msgid "Click on **More Info** and then on **Run anyway**." msgstr "" #: ../../content/administration/install/install.rst:99 msgid "Accept the UAC_ prompt." msgstr "" #: ../../content/administration/install/install.rst:100 msgid "Go through the various installation steps." msgstr "" #: ../../content/administration/install/install.rst:102 msgid "Odoo will automatically be started at the end of the installation." msgstr "" #: ../../content/administration/install/install.rst:105 #: ../../content/administration/install/install.rst:418 msgid "Linux" msgstr "" #: ../../content/administration/install/install.rst:108 msgid "Debian/Ubuntu" msgstr "" #: ../../content/administration/install/install.rst:110 msgid "" "Odoo 15.0 'deb' package currently supports `Debian 11 (Bullseye)`_, `Ubuntu " "20.04 (Focal)`_ or above." msgstr "" #: ../../content/administration/install/install.rst:113 #: ../../content/administration/install/install.rst:186 #: ../../content/administration/install/install.rst:300 #: ../../content/administration/install/install.rst:466 #: ../../content/administration/install/install.rst:637 msgid "Prepare" msgstr "Voorbereiden" #: ../../content/administration/install/install.rst:115 msgid "" "Odoo needs a `PostgreSQL`_ server to run properly. The default configuration" " for the Odoo 'deb' package is to use the PostgreSQL server on the same host" " as your Odoo instance. Execute the following command in order to install " "the PostgreSQL server:" msgstr "" #: ../../content/administration/install/install.rst:123 #: ../../content/administration/install/install.rst:198 #: ../../content/administration/install/install.rst:367 #: ../../content/administration/install/install.rst:540 #: ../../content/administration/install/install.rst:704 msgid "" "`wkhtmltopdf` is not installed through **pip** and must be installed " "manually in version `0.12.5 `_ for it to " "support headers and footers. See our `wiki " "`_ for more details on the " "various versions." msgstr "" #: ../../content/administration/install/install.rst:129 #: ../../content/administration/install/install.rst:204 msgid "Repository" msgstr "Repository" #: ../../content/administration/install/install.rst:131 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 **as root**:" msgstr "" #: ../../content/administration/install/install.rst:140 msgid "" "You can then use the usual `apt-get upgrade` command to keep your " "installation up-to-date." msgstr "" #: ../../content/administration/install/install.rst:142 msgid "" "At this moment, there is no nightly repository for the Enterprise Edition." msgstr "" #: ../../content/administration/install/install.rst:145 msgid "Deb Package" msgstr "" #: ../../content/administration/install/install.rst:147 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 `_." msgstr "" #: ../../content/administration/install/install.rst:150 msgid "Next, execute the following commands **as root**:" msgstr "" #: ../../content/administration/install/install.rst:158 msgid "" "This will install Odoo as a service, create the necessary PostgreSQL_ user " "and automatically start the server." msgstr "" #: ../../content/administration/install/install.rst:161 msgid "" "The `python3-xlwt` Debian package does not exists in Debian Buster nor " "Ubuntu 18.04. This python module is needed to export into xls format." msgstr "" #: ../../content/administration/install/install.rst:164 msgid "If you need the feature, you can install it manually with:" msgstr "" #: ../../content/administration/install/install.rst:170 msgid "" "The `num2words` python package does not exists in Debian Buster nor Ubuntu " "18.04. Textual amounts will not be rendered by Odoo and this could cause " "problems with the `l10n_mx_edi` module." msgstr "" #: ../../content/administration/install/install.rst:174 msgid "If you need this feature, you can install manually with:" msgstr "" #: ../../content/administration/install/install.rst:181 msgid "Fedora" msgstr "Fedora" #: ../../content/administration/install/install.rst:183 msgid "Odoo 15.0 'rpm' package supports Fedora 34." msgstr "" #: ../../content/administration/install/install.rst:187 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/install.rst:206 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/install.rst:218 msgid "RPM package" msgstr "" #: ../../content/administration/install/install.rst:220 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 `_." msgstr "" #: ../../content/administration/install/install.rst:223 msgid "" "Once downloaded, the package can be installed using the 'dnf' package " "manager:" msgstr "" #: ../../content/administration/install/install.rst:235 msgid "Source Install" msgstr "" #: ../../content/administration/install/install.rst:237 msgid "" "The source \"installation\" is really about not installing Odoo, and running" " it directly from source instead." msgstr "" #: ../../content/administration/install/install.rst:240 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/install.rst:244 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 ` without " "needing to edit a configuration file." msgstr "" #: ../../content/administration/install/install.rst:248 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/install.rst:255 #: ../../content/administration/install/install.rst:421 #: ../../content/administration/install/install.rst:592 msgid "Fetch the sources" msgstr "" #: ../../content/administration/install/install.rst:257 #: ../../content/administration/install/install.rst:423 #: ../../content/administration/install/install.rst:594 msgid "" "There are two ways to obtain the source code of Odoo: as a zip **archive** " "or through **git**." msgstr "" #: ../../content/administration/install/install.rst:260 #: ../../content/administration/install/install.rst:426 #: ../../content/administration/install/install.rst:597 msgid "Archive" msgstr "Archiveren" #: ../../content/administration/install/install.rst:262 #: ../../content/administration/install/install.rst:279 #: ../../content/administration/install/install.rst:428 #: ../../content/administration/install/install.rst:445 #: ../../content/administration/install/install.rst:599 #: ../../content/administration/install/install.rst:616 msgid "Community Edition:" msgstr "" #: ../../content/administration/install/install.rst:264 #: ../../content/administration/install/install.rst:270 #: ../../content/administration/install/install.rst:430 #: ../../content/administration/install/install.rst:436 #: ../../content/administration/install/install.rst:601 #: ../../content/administration/install/install.rst:607 msgid "`Official download page `_" msgstr "" #: ../../content/administration/install/install.rst:265 #: ../../content/administration/install/install.rst:431 #: ../../content/administration/install/install.rst:602 msgid "`GitHub repository `_" msgstr "" #: ../../content/administration/install/install.rst:266 #: ../../content/administration/install/install.rst:432 #: ../../content/administration/install/install.rst:603 msgid "`Nightly server `_" msgstr "" #: ../../content/administration/install/install.rst:268 #: ../../content/administration/install/install.rst:434 #: ../../content/administration/install/install.rst:605 msgid "Enterprise Edition:" msgstr "" #: ../../content/administration/install/install.rst:271 #: ../../content/administration/install/install.rst:437 #: ../../content/administration/install/install.rst:608 msgid "`GitHub repository `_" msgstr "" #: ../../content/administration/install/install.rst:274 #: ../../content/administration/install/install.rst:440 #: ../../content/administration/install/install.rst:611 msgid "Git" msgstr "" #: ../../content/administration/install/install.rst:276 #: ../../content/administration/install/install.rst:442 #: ../../content/administration/install/install.rst:613 msgid "" "The following requires git_ to be installed on your machine and that you " "have basic knowledge of git commands." msgstr "" #: ../../content/administration/install/install.rst:286 #: ../../content/administration/install/install.rst:452 #: ../../content/administration/install/install.rst:623 msgid "Enterprise Edition: (see :ref:`setup/install/editions` to get access)" msgstr "" #: ../../content/administration/install/install.rst:292 #: ../../content/administration/install/install.rst:458 #: ../../content/administration/install/install.rst:629 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/install.rst:303 #: ../../content/administration/install/install.rst:469 #: ../../content/administration/install/install.rst:640 msgid "Python" msgstr "" #: ../../content/administration/install/install.rst:305 msgid "" "Odoo requires Python 3.7 or later to run. Visit `Python's download page " "`_ to download and install the " "latest version of Python 3 on your machine." msgstr "" #: ../../content/administration/install/install.rst:308 msgid "" "During installation, check **Add Python 3 to PATH**, then click **Customize " "Installation** and make sure that **pip** is checked." msgstr "" #: ../../content/administration/install/install.rst:311 #: ../../content/administration/install/install.rst:474 #: ../../content/administration/install/install.rst:645 msgid "" "If Python 3 is already installed, make sure that the version is 3.7 or " "above, as previous versions are not compatible with Odoo." msgstr "" #: ../../content/administration/install/install.rst:318 #: ../../content/administration/install/install.rst:481 #: ../../content/administration/install/install.rst:652 msgid "Verify also that pip_ is installed for this version." msgstr "" #: ../../content/administration/install/install.rst:327 msgid "" "Odoo uses PostgreSQL as database management system. `Download and install " "PostgreSQL `_ (supported " "version: 10.0 and later)." msgstr "" #: ../../content/administration/install/install.rst:330 #: ../../content/administration/install/install.rst:499 #: ../../content/administration/install/install.rst:664 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/install.rst:333 msgid "" "Add PostgreSQL's `bin` directory (by default: `C:\\\\Program " "Files\\\\PostgreSQL\\\\\\\\bin`) to your `PATH`." msgstr "" #: ../../content/administration/install/install.rst:335 msgid "Create a postgres user with a password using the pg admin gui:" msgstr "" #: ../../content/administration/install/install.rst:337 msgid "Open **pgAdmin**." msgstr "" #: ../../content/administration/install/install.rst:338 msgid "Double-click the server to create a connection." msgstr "" #: ../../content/administration/install/install.rst:339 msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." msgstr "" #: ../../content/administration/install/install.rst:340 msgid "Enter the username in the **Role Name** field (e.g. `odoo`)." msgstr "" #: ../../content/administration/install/install.rst:341 msgid "" "Open the **Definition** tab and enter the password (e.g. ``odoo``), then " "click **Save**." msgstr "" #: ../../content/administration/install/install.rst:342 msgid "" "Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " "database?** to `Yes`." msgstr "" #: ../../content/administration/install/install.rst:346 #: ../../content/administration/install/install.rst:511 #: ../../content/administration/install/install.rst:676 msgid "Dependencies" msgstr "Afhankelijkheden" #: ../../content/administration/install/install.rst:348 msgid "" "Before installing the dependencies, you must download and install the `Build" " Tools for Visual Studio " "`_. When prompted, select **C++ build tools** in the " "**Workloads** tab and install them." msgstr "" #: ../../content/administration/install/install.rst:352 #: ../../content/administration/install/install.rst:525 #: ../../content/administration/install/install.rst:678 msgid "" "Odoo dependencies are listed in the `requirements.txt` file located at the " "root of the Odoo community directory." msgstr "" #: ../../content/administration/install/install.rst:355 #: ../../content/administration/install/install.rst:528 #: ../../content/administration/install/install.rst:681 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/install.rst:358 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/install.rst:372 #: ../../content/administration/install/install.rst:545 #: ../../content/administration/install/install.rst:709 msgid "" "For languages with right-to-left interface (such as Arabic or Hebrew), the " "package `rtlcss` is needed:" msgstr "" #: ../../content/administration/install/install.rst:375 msgid "Download and install `nodejs `_." msgstr "" #: ../../content/administration/install/install.rst:376 #: ../../content/administration/install/install.rst:549 #: ../../content/administration/install/install.rst:713 msgid "Install `rtlcss`:" msgstr "" #: ../../content/administration/install/install.rst:382 msgid "" "Edit the System Environment's variable `PATH` to add the folder where " "`rtlcss.cmd` is located (typically: " "`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." msgstr "" #: ../../content/administration/install/install.rst:386 #: ../../content/administration/install/install.rst:556 #: ../../content/administration/install/install.rst:720 msgid "Running Odoo" msgstr "" #: ../../content/administration/install/install.rst:388 #: ../../content/administration/install/install.rst:558 #: ../../content/administration/install/install.rst:722 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/install.rst:391 #: ../../content/administration/install/install.rst:561 #: ../../content/administration/install/install.rst:725 msgid "" "To configure the server, you can either specify :ref:`command-line arguments" " ` or a :ref:`configuration file " "`." msgstr "" #: ../../content/administration/install/install.rst:394 #: ../../content/administration/install/install.rst:564 #: ../../content/administration/install/install.rst:728 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/install.rst:398 #: ../../content/administration/install/install.rst:568 #: ../../content/administration/install/install.rst:732 msgid "Common necessary configurations are:" msgstr "" #: ../../content/administration/install/install.rst:400 msgid "PostgreSQL user and password." msgstr "" #: ../../content/administration/install/install.rst:401 #: ../../content/administration/install/install.rst:573 #: ../../content/administration/install/install.rst:737 msgid "Custom addon paths beyond the defaults, to load your own modules." msgstr "" #: ../../content/administration/install/install.rst:403 #: ../../content/administration/install/install.rst:575 #: ../../content/administration/install/install.rst:739 msgid "A typical way to run the server would be:" msgstr "" #: ../../content/administration/install/install.rst:410 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`." msgstr "" #: ../../content/administration/install/install.rst:415 #: ../../content/administration/install/install.rst:586 #: ../../content/administration/install/install.rst:750 msgid "" ":doc:`The exhaustive list of arguments for odoo-bin " "`." msgstr "" #: ../../content/administration/install/install.rst:471 msgid "" "Odoo requires Python 3.7 or later to run. Use your package manager to " "download and install Python 3 on your machine if it is not already done." msgstr "" #: ../../content/administration/install/install.rst:490 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/install.rst:493 msgid "On Debian/Unbuntu, it can be achieved by executing the following:" msgstr "" #: ../../content/administration/install/install.rst:507 #: ../../content/administration/install/install.rst:672 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/install.rst:513 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/install.rst:517 msgid "" "On Debian/Unbuntu, the following command should install all the required " "libraries:" msgstr "" #: ../../content/administration/install/install.rst:531 #: ../../content/administration/install/install.rst:684 msgid "" "Navigate to the path of your Odoo Community installation (`CommunityPath`) " "and run **pip** on the requirements file:" msgstr "" #: ../../content/administration/install/install.rst:548 msgid "Download and install **nodejs** and **npm** with your package manager." msgstr "" #: ../../content/administration/install/install.rst:570 #: ../../content/administration/install/install.rst:734 msgid "" "PostgreSQL user and password. Odoo has no defaults beyond `psycopg2's " "defaults `_: connects over a UNIX" " socket on port `5432` with the current user and no password." msgstr "" #: ../../content/administration/install/install.rst:582 #: ../../content/administration/install/install.rst:746 msgid "" "Where `CommunityPath` is the path of the Odoo Community installation and " "`mydb` is the default database to serve on `localhost:8069`." msgstr "" #: ../../content/administration/install/install.rst:589 msgid "Mac OS" msgstr "" #: ../../content/administration/install/install.rst:642 msgid "" "Odoo requires Python 3.7 or later to run. Use your preferred package manager" " (homebrew_, macports_) to download and install Python 3 on your machine if " "it is not already done." msgstr "" #: ../../content/administration/install/install.rst:661 msgid "" "Odoo uses PostgreSQL as database management system. Use `postgres.app " "`_ to download and install PostgreSQL (supported " "version: 10.0 and later)." msgstr "" #: ../../content/administration/install/install.rst:693 msgid "Non-Python dependencies need to be installed with a package manager:" msgstr "" #: ../../content/administration/install/install.rst:695 msgid "Download and install the **Command Line Tools**:" msgstr "" #: ../../content/administration/install/install.rst:701 msgid "" "Download and install the package manager of your choice (homebrew_, " "macports_)." msgstr "" #: ../../content/administration/install/install.rst:702 msgid "Install non-python dependencies." msgstr "" #: ../../content/administration/install/install.rst:712 msgid "" "Download and install **nodejs** with your preferred package manager " "(homebrew_, macports_)." msgstr "" #: ../../content/administration/install/install.rst:755 #: ../../content/administration/maintain/update.rst:147 msgid "Docker" msgstr "" #: ../../content/administration/install/install.rst:757 msgid "" "The full documentation on how to use Odoo with Docker can be found on the " "official Odoo `docker image `_ page." msgstr "" #: ../../content/administration/maintain.rst:5 msgid "Maintain" msgstr "" #: ../../content/administration/maintain/domain_names.rst:3 msgid "Domain names" msgstr "" #: ../../content/administration/maintain/domain_names.rst:5 msgid "" "A **domain name** works as an address for your website. It makes the " "Internet much more accessible as it allows users to type a meaningful web " "address, such as ``www.odoo.com``, rather than its server's IP address with " "a series of numbers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:9 msgid "" "You can use a custom domain name to access your Odoo database and websites:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:11 msgid "" "By :ref:`registering a free domain name with Odoo ` (for Odoo Online databases)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:13 msgid "" "By :ref:`configuring a custom domain that you already own `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:16 msgid "" "Odoo Online and Odoo.sh databases, including their websites, use by default " "a subdomain of ``odoo.com`` for both the URL and the emails (e.g., " "``https://example.odoo.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:20 msgid "" "Odoo offers a :ref:`free custom domain name ` to " "all Odoo Online databases for one year. Visitors can then access your " "website with an address such as ``www.example.com`` rather than the default " "``example.odoo.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:27 msgid "About domain names" msgstr "" #: ../../content/administration/maintain/domain_names.rst:29 msgid "" "Having a **good domain name** is as important to your branding as the name " "of your business or organization as it is the first thing your visitors will" " notice. We recommend you keep them *simple, short, easy to remember and " "spell*." msgstr "" #: ../../content/administration/maintain/domain_names.rst:33 msgid "" "A **subdomain** is a domain that is a part of another domain. It often " "refers to the additional part that comes before the main domain name. " "Traditionally, most websites use the ``www.`` subdomain, but any string of " "letters can be used as well. You can use subdomains to direct your visitors " "to other websites than your main website or to specific pages (e.g., " "``experience.odoo.com`` points to a specific page.)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:39 msgid "" "All domain names are referenced in the **Domain Name System**, or **DNS**, " "which works as a giant directory for the Internet. There are many DNS " "servers, so any modification to the DNS can take up to 72 hours to propagate" " worldwide on all servers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:46 msgid "Register a free domain name with Odoo" msgstr "" #: ../../content/administration/maintain/domain_names.rst:48 msgid "" "You can register a domain name for your Odoo Online database directly from " "Odoo Website or your database manager." msgstr "" #: ../../content/administration/maintain/domain_names.rst:52 msgid "" "Your domain name is **free for one year** if you register it with Odoo!" msgstr "" #: ../../content/administration/maintain/domain_names.rst:53 msgid "" "The domain name is registered with `Gandi `_, the " "domain name registrar." msgstr "" #: ../../content/administration/maintain/domain_names.rst:55 msgid "" "You are the owner of the domain name and can use it for other purposes." msgstr "" #: ../../content/administration/maintain/domain_names.rst:56 msgid "Odoo manages payment and technical support for you." msgstr "" #: ../../content/administration/maintain/domain_names.rst:58 msgid "" "To do so, go to :menuselection:`Website --> Go to website --> Promote --> " "Domain Name`. Alternatively, open your `database manager " "`_, click on the :guilabel:`settings` " "button next to your database, then on :guilabel:`Domain names`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:66 msgid "" "Search for the domain name of your choice to check its availability, then " "select the one you want to register for your website." msgstr "" #: ../../content/administration/maintain/domain_names.rst:73 msgid "" "Next, fill in the form with your information to become the domain name " "owner." msgstr "" #: ../../content/administration/maintain/domain_names.rst:75 msgid "" "Your domain name is directly linked to your database, but you still have to " ":ref:`map your domain name with your website `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:79 msgid "" "Free domain names are also available for free Odoo Online databases (if you " "installed one app only, for example). In this case, Odoo reviews your " "request and your website to avoid abuse. This process may take up to three " "days." msgstr "" #: ../../content/administration/maintain/domain_names.rst:82 msgid "This is not available for Odoo.sh databases yet." msgstr "" #: ../../content/administration/maintain/domain_names.rst:87 msgid "Manage your domain name registered with Odoo" msgstr "" #: ../../content/administration/maintain/domain_names.rst:89 msgid "" "To manage the DNS records of your domain name registered with Odoo or to " "visualize the contacts associated with it, open your `database manager " "`_, click on the :guilabel:`settings` " "button next to your database, on :guilabel:`Domain names`, and then on " ":guilabel:`Contacts` or :guilabel:`DNS`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:99 msgid "" "Please `submit a support ticket `_ if you need " "further assistance to manage your domain name." msgstr "" #: ../../content/administration/maintain/domain_names.rst:105 msgid "Configure your existing domain name" msgstr "" #: ../../content/administration/maintain/domain_names.rst:107 msgid "" "If you already own a domain name, you can use it to point to your website." msgstr "" #: ../../content/administration/maintain/domain_names.rst:109 msgid "" "To avoid any issue with the :ref:`SSL certificate validation `, we highly recommend that you proceed with the following actions " "in this order:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:112 msgid "" ":ref:`Add a CNAME record ` on your domain name's DNS " "zone." msgstr "" #: ../../content/administration/maintain/domain_names.rst:113 msgid "" ":ref:`Map your domain name with your Odoo database `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:114 msgid "" ":ref:`Map your domain name with your Odoo website `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:119 msgid "Add a CNAME record" msgstr "" #: ../../content/administration/maintain/domain_names.rst:121 msgid "" "A **CNAME record** is a type of DNS record that points to the IP address of " "another website rather than to directly to an IP address." msgstr "" #: ../../content/administration/maintain/domain_names.rst:124 msgid "" "You need a CNAME record that points to your Odoo database. The requirements " "are detailed in your database manager." msgstr "" #: ../../content/administration/maintain/domain_names.rst:129 #: ../../content/administration/maintain/domain_names.rst:199 #: ../../content/administration/maintain/supported_versions.rst:26 msgid "Odoo Online" msgstr "" #: ../../content/administration/maintain/domain_names.rst:131 msgid "" "The target address is the current address of your database, as defined at " "its creation (e.g., ``example.odoo.com``)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:134 #: ../../content/administration/maintain/domain_names.rst:213 #: ../../content/administration/maintain/supported_versions.rst:26 #: ../../content/administration/odoo_sh.rst:5 #: ../../content/administration/upgrade/odoo_sh.rst:4 msgid "Odoo.sh" msgstr "" #: ../../content/administration/maintain/domain_names.rst:136 msgid "" "Your project's main address is defined in :menuselection:`Settings --> " "Project Name`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:138 msgid "" "If you want to target a specific branch (production, staging or " "development), go to :menuselection:`Branches --> select your branch --> " "Settings --> Custom domains`, and click on :guilabel:`How to set up my " "domain?`. A message indicates which address your CNAME record should target." msgstr "" #: ../../content/administration/maintain/domain_names.rst:143 #: ../../content/administration/maintain/domain_names.rst:185 msgid "Open your domain name's manager dashboard." msgstr "" #: ../../content/administration/maintain/domain_names.rst:144 msgid "" "Open the **DNS zone** management page for the domain name you want to " "configure." msgstr "" #: ../../content/administration/maintain/domain_names.rst:145 msgid "Create a **CNAME record** pointing to the address of your database." msgstr "" #: ../../content/administration/maintain/domain_names.rst:147 msgid "" "While Odoo suggests creating a CNAME record for your ``www.`` subdomain " "(``www.example.com``, you can of course use any domain name of your choice, " "with any subdomain (e.g., ``anything.example.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:152 msgid "" "You own the domain name ``example.com``, and you have an Odoo Online " "database at the address ``example.odoo.com``. You want to access your Odoo " "database primarily with the domain ``www.example.com`` but also with the " ":ref:`naked domain ` ``example.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:157 msgid "" "To do so, you create a CNAME record for the ``www`` subdomain, with " "``example.odoo.com`` as the target. The DNS zone manager generates the " "following rule and adds it to your DNS zone: ``www IN CNAME " "example.odoo.com.``" msgstr "" #: ../../content/administration/maintain/domain_names.rst:161 msgid "" "You also create a redirection from ``example.com`` to ``wwww.example.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:163 msgid "Your new DNS records are propagated to all DNS servers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:166 msgid "Here are some specific guidelines to create a CNAME record:" msgstr "" "Hier zijn een paar specifieke richtlijnen om een CNAME record aan te maken:" #: ../../content/administration/maintain/domain_names.rst:168 msgid "`GoDaddy `_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:169 msgid "" "`Namecheap " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:170 msgid "" "`OVH " "`_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:171 msgid "" "`CloudFlare `_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:172 msgid "" "`Google Domains `_" msgstr "" #: ../../content/administration/maintain/domain_names.rst:177 msgid "Naked domain" msgstr "" #: ../../content/administration/maintain/domain_names.rst:179 msgid "" "A **naked domain** is a domain name that doesn't have any subdomain at the " "beginning of the address (e.g., ``odoo.com`` instead of ``www.odoo.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:182 msgid "" "You may want your naked domain to redirect to your website as some visitors " "may not type the full domain name to access your website." msgstr "" #: ../../content/administration/maintain/domain_names.rst:186 msgid "" "Create a **redirection** from the naked domain (``example.com``) to your " "main domain name (``www.example.com``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:190 msgid "" "Depending on your domain name registrar, this redirection may be already " "pre-configured." msgstr "" #: ../../content/administration/maintain/domain_names.rst:195 msgid "Map your domain name with your Odoo database" msgstr "" #: ../../content/administration/maintain/domain_names.rst:201 msgid "" "Open your `database manager `_, click on " "the :guilabel:`settings` button next to your database, on :guilabel:`Domain " "names`, and then on :guilabel:`Use my own domain` at the bottom of the right" " column." msgstr "" #: ../../content/administration/maintain/domain_names.rst:205 msgid "" "Type the domain name you want to add to this database, then click on " ":guilabel:`Verify` to check if the CNAME record is correctly configured. " "Once done, click on :guilabel:`I confirm, it's done`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:215 msgid "" "Go to :menuselection:`Branches --> select your branch --> Settings --> " "Custom domains`, type the domain name you want to add to this database, then" " click on :guilabel:`Add domain`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:223 msgid "" ":ref:`Odoo.sh branches: settings tab `" msgstr "" #: ../../content/administration/maintain/domain_names.rst:226 msgid "" "Make sure to :ref:`add a CNAME record ` to your domain " "name's DNS **before** mapping your domain name with your Odoo database." msgstr "" #: ../../content/administration/maintain/domain_names.rst:229 msgid "" "Failing to do so may impede the validation of the :ref:`SSL certificate " "` and would result in a *certificate name mismatch* error. " "This is often displayed by web browsers as a warning such as *\"Your " "connection is not private\"*." msgstr "" #: ../../content/administration/maintain/domain_names.rst:233 msgid "" "If this is the case and you have added the domain name to your database's " "settings less than five days ago, wait 24 hours as the validation may still " "happen. Otherwise, please `submit a support ticket " "`_ including screenshots of your CNAME records." msgstr "" #: ../../content/administration/maintain/domain_names.rst:240 msgid "SSL encryption (HTTPS protocol)" msgstr "" #: ../../content/administration/maintain/domain_names.rst:242 msgid "" "**SSL encryption** is an encryption-based Internet security protocol. It " "allows your visitors to navigate your website through a secure connection, " "which appears as an ``https://`` protocol at the beginning of your web " "address, rather than a non-secure ``http://`` protocol." msgstr "" #: ../../content/administration/maintain/domain_names.rst:246 msgid "" "Odoo generates a separate SSL certificate for each domain :ref:`mapped in " "the database manager `, using integration with `Let's " "Encrypt Certificate Authority and ACME protocol " "`_." msgstr "" #: ../../content/administration/maintain/domain_names.rst:251 msgid "The certificate generation may take up to 24h." msgstr "" #: ../../content/administration/maintain/domain_names.rst:252 msgid "" "Several attempts to validate your certificate are made during the five days " "following the moment you add your domain name in your database's settings." msgstr "" #: ../../content/administration/maintain/domain_names.rst:254 msgid "" "If you already use another service, you can keep using it or simply change " "for Odoo." msgstr "" #: ../../content/administration/maintain/domain_names.rst:259 msgid "Web base URL of a database" msgstr "" #: ../../content/administration/maintain/domain_names.rst:262 msgid "" "If you have Odoo Website, you can disregard this part and directly :ref:`map" " your domain name with your website `." msgstr "" #: ../../content/administration/maintain/domain_names.rst:265 msgid "" "The **web base URL** of a database, or **root URL** affects your main " "website address and all the links sent to your customers (e.g., quotations, " "portal links, etc.)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:268 msgid "" "To configure it, access your Odoo database with your custom address, then " "log in as an administrator of your database (any user in the *Settings* " "group) from the login screen." msgstr "" #: ../../content/administration/maintain/domain_names.rst:272 msgid "" "Connecting to your database with the original Odoo subdomain address (e.g., " "``example.odoo.com`` also updates the web base URL of your database. See " "below to prevent these automatic updates." msgstr "" #: ../../content/administration/maintain/domain_names.rst:275 msgid "" "Alternatively, you can do it manually. To do so, activate the " ":ref:`developer mode `, then go to :menuselection:`Settings " "--> Technical --> System Parameters`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:278 msgid "" "Find the key called ``web.base.url`` (or create it if it does not exist) and" " enter the full address of your website as value, such as " "``https://www.example.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:282 msgid "" "The URL must include the protocol ``https://`` (or ``http://``) and must not" " end with a slash (``/``)." msgstr "" #: ../../content/administration/maintain/domain_names.rst:285 msgid "" "To prevent the automatic update of the web base URL when an administrator " "logs in the database, you can create the following System Parameter:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:288 msgid "key: ``web.base.url.freeze``" msgstr "" #: ../../content/administration/maintain/domain_names.rst:289 msgid "value: ``True``" msgstr "" #: ../../content/administration/maintain/domain_names.rst:294 msgid "Map your domain name with your website" msgstr "" #: ../../content/administration/maintain/domain_names.rst:296 msgid "" "Mapping your domain name to your website isn't the same as mapping it with " "your database:" msgstr "" #: ../../content/administration/maintain/domain_names.rst:298 msgid "" "It defines your domain name as the main one for your website, helping search" " engines to index your website properly." msgstr "" #: ../../content/administration/maintain/domain_names.rst:300 msgid "" "It defines your domain name as the base URL for your database, including the" " portal links sent by email to your customers." msgstr "" #: ../../content/administration/maintain/domain_names.rst:302 msgid "" "If you have multiple websites, it maps your domain name with the appropriate" " website." msgstr "" #: ../../content/administration/maintain/domain_names.rst:304 msgid "" "Go to :menuselection:`Website --> Configuration --> Settings --> Website " "Info`. If you have multiple websites, select the one you want to configure." msgstr "" #: ../../content/administration/maintain/domain_names.rst:307 msgid "" "In the :guilabel:`Domain` field, fill in the web address of your website " "(e.g., ``https://www.example.com``) and click on :guilabel:`Save`." msgstr "" #: ../../content/administration/maintain/domain_names.rst:315 msgid "" "Mapping your domain name with your Odoo website prevents Google from " "indexing both your custom domain name ``www.example.com`` and your original " "odoo database address ``example.odoo.com``." msgstr "" #: ../../content/administration/maintain/domain_names.rst:318 msgid "" "If both addresses are already indexed, it may take some time before Google " "removes the indexation of the second address. You may also try using the " "`Google Search Console `_ " "to fix this." msgstr "" #: ../../content/administration/maintain/domain_names.rst:323 msgid "" "If you have multiple websites and companies on your database, make sure that" " you select the right :guilabel:`Company` in the website settings, next to " "the :guilabel:`Domain` settings. Doing so indicates Odoo which URL to use as" " the :ref:`base URL ` according to the company in " "use." msgstr "" #: ../../content/administration/maintain/domain_names.rst:329 msgid ":doc:`/applications/general/email_communication/email_servers`" msgstr "" #: ../../content/administration/maintain/enterprise.rst:6 msgid "Upgrade Community to Enterprise" msgstr "" #: ../../content/administration/maintain/enterprise.rst:8 msgid "" "Depending on your current installation, there are multiple ways to upgrade " "your community version. In any case the basic guidelines are:" msgstr "" #: ../../content/administration/maintain/enterprise.rst:12 #: ../../content/administration/maintain/enterprise.rst:31 #: ../../content/administration/maintain/enterprise.rst:63 #: ../../content/administration/maintain/enterprise.rst:80 msgid "Backup your community database" msgstr "" #: ../../content/administration/maintain/enterprise.rst:17 #: ../../content/administration/maintain/enterprise.rst:62 msgid "Shutdown your server" msgstr "" #: ../../content/administration/maintain/enterprise.rst:19 msgid "Install the web_enterprise module" msgstr "" #: ../../content/administration/maintain/enterprise.rst:21 msgid "Restart your server" msgstr "" #: ../../content/administration/maintain/enterprise.rst:23 msgid "Enter your Odoo Enterprise Subscription code" msgstr "" #: ../../content/administration/maintain/enterprise.rst:29 msgid "On Linux, using an installer" msgstr "" #: ../../content/administration/maintain/enterprise.rst:33 msgid "Stop the odoo service" msgstr "" #: ../../content/administration/maintain/enterprise.rst:39 msgid "" "Install the enterprise .deb (it should install over the community package)" msgstr "" #: ../../content/administration/maintain/enterprise.rst:45 msgid "Update your database to the enterprise packages using" msgstr "" #: ../../content/administration/maintain/enterprise.rst:51 msgid "" "You should be able to connect to your Odoo Enterprise instance using your " "usual mean of identification. You can then link your database with your Odoo" " Enterprise Subscription by entering the code you received by e-mail in the " "form input" msgstr "" #: ../../content/administration/maintain/enterprise.rst:57 msgid "On Linux, using the source code" msgstr "" #: ../../content/administration/maintain/enterprise.rst:59 msgid "" "There are many ways to launch your server when using sources, and you " "probably have your own favourite. You may need to adapt sections to your " "usual workflow." msgstr "" #: ../../content/administration/maintain/enterprise.rst:64 msgid "" "Update the ``--addons-path`` parameter of your launch command (see " ":ref:`setup/install/source`)" msgstr "" #: ../../content/administration/maintain/enterprise.rst:65 msgid "Install the web_enterprise module by using" msgstr "" #: ../../content/administration/maintain/enterprise.rst:71 msgid "Depending on the size of your database, this may take some time." msgstr "" #: ../../content/administration/maintain/enterprise.rst:73 msgid "" "Restart your server with the updated addons path of point 3. You should be " "able to connect to your instance. You can then link your database with your " "Odoo Enterprise Subscription by entering the code you received by e-mail in " "the form input" msgstr "" #: ../../content/administration/maintain/enterprise.rst:78 msgid "On Windows" msgstr "" #: ../../content/administration/maintain/enterprise.rst:82 msgid "" "Uninstall Odoo Community (using the Uninstall executable in the installation" " folder) - PostgreSQL will remain installed" msgstr "" #: ../../content/administration/maintain/enterprise.rst:88 msgid "" "Launch the Odoo Enterprise Installer and follow the steps normally. When " "choosing the installation path, you can set the folder of the Community " "installation (this folder still contains the PostgreSQL installation). " "Uncheck ``Start Odoo`` at the end of the installation" msgstr "" #: ../../content/administration/maintain/enterprise.rst:96 msgid "" "Using a command window, update your Odoo Database using this command (from " "the Odoo installation path, in the server subfolder)" msgstr "" #: ../../content/administration/maintain/enterprise.rst:103 msgid "" "No need to manually launch the server, the service is running. You should be" " able to connect to your Odoo Enterprise instance using your usual mean of " "identification. You can then link your database with your Odoo Enterprise " "Subscription by entering the code you received by e-mail in the form input" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:6 msgid "Change hosting solution" msgstr "" #: ../../content/administration/maintain/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/maintain/hosting_changes.rst:12 msgid "From on-premises to Odoo Online" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:14 #: ../../content/administration/maintain/hosting_changes.rst:48 msgid "Odoo Online is not compatible with **non-standard apps**." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:16 msgid "" "Create a :ref:`duplicate ` of your database: in this " "duplicate, uninstall all the **non-standard apps**." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:17 msgid "" "Grab a \"dump with filestore\" of your database by using the Database " "Manager." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:18 #: ../../content/administration/maintain/hosting_changes.rst:51 msgid "" "**If you have time constraints, contact us earlier to schedule the " "transfer.**" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:19 msgid "" "`Create a support ticket `_ 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/maintain/hosting_changes.rst:20 #: ../../content/administration/maintain/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/maintain/hosting_changes.rst:21 #: ../../content/administration/maintain/hosting_changes.rst:54 msgid "It's done!" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:24 msgid "From on-premises to Odoo.sh" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:26 #: ../../content/administration/maintain/hosting_changes.rst:43 msgid "" "Follow the :ref:`Import your database section of the Odoo.sh documentation " "`." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:27 msgid "...and voilà!" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:30 msgid "From Odoo Online to on-premises" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:32 #: ../../content/administration/maintain/hosting_changes.rst:40 msgid "" "Log into `your Odoo Online user portal " "`_ and look for the version " "number of your database." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:33 msgid "" "If your database does not run a :ref:`major version ` 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/maintain/hosting_changes.rst:34 #: ../../content/administration/maintain/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 " "`_)" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:35 #: ../../content/administration/maintain/hosting_changes.rst:60 msgid "Restore it from the database manager on your local server." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:38 msgid "From Odoo Online to Odoo.sh" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:41 msgid "" "If your database does not run a :ref:`major version ` 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/maintain/hosting_changes.rst:46 msgid "From Odoo.sh to Odoo Online" msgstr "" #: ../../content/administration/maintain/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/maintain/hosting_changes.rst:52 msgid "" "`Create a support ticket `_ and include your " "subscription number and the URL you want to use for your database (e.g.: my-" "company.odoo.com)." msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:57 msgid "From Odoo.sh to on-premises" msgstr "" #: ../../content/administration/maintain/hosting_changes.rst:59 msgid "" "Grab a :ref:`backup of your Odoo.sh production database " "`." msgstr "" #: ../../content/administration/maintain/on_premise.rst:3 msgid "On-premise database management" msgstr "" #: ../../content/administration/maintain/on_premise.rst:6 msgid "Register a database" msgstr "Registreer een database" #: ../../content/administration/maintain/on_premise.rst:8 msgid "" "To register your database, you just need to enter your Subscription Code in " "the banner in the App Switcher. Make sure you do not add extra spaces before" " or after your subscription code. If the registration is successful, it will" " turn green and will provide you with the Expiration Date of your freshly-" "registered database. You can check this Expiration Date in the About menu " "(Odoo 9) or in the Settings Dashboard (Odoo 10)." msgstr "" #: ../../content/administration/maintain/on_premise.rst:16 msgid "Registration Error Message" msgstr "Registratie Foutmelding" #: ../../content/administration/maintain/on_premise.rst:18 msgid "" "If you are unable to register your database, you will likely encounter this " "message:" msgstr "" "Indien u uw database niet kan registreren krijgt u waarschijnlijk de " "volgende melding:" #: ../../content/administration/maintain/on_premise.rst:27 #: ../../content/administration/maintain/on_premise.rst:106 #: ../../content/administration/maintain/on_premise.rst:134 msgid "Solutions" msgstr "Oplossingen" #: ../../content/administration/maintain/on_premise.rst:29 msgid "Do you have a valid Enterprise subscription?" msgstr "Heeft u een geldig Enterprise abonnement?" #: ../../content/administration/maintain/on_premise.rst:31 msgid "" "Check if your subscription details get the tag \"In Progress\" on your `Odoo" " Account `__ or with your Account" " Manager" msgstr "" #: ../../content/administration/maintain/on_premise.rst:35 msgid "Have you already linked a database with your subscription reference?" msgstr "Heeft u al een database gelinkt met uw abonnementsnummer?" #: ../../content/administration/maintain/on_premise.rst:37 msgid "" "You can link only one database per subscription. (Need a test or a " "development database? `Find a partner `__)" msgstr "" #: ../../content/administration/maintain/on_premise.rst:41 msgid "" "You can unlink the old database yourself on your `Odoo Contract " "`__ with the button \"Unlink " "database\"" msgstr "" "U kan de oude database zelf ontkoppelen via uw `Odoo Contract " "`__ met de \"Unlink database\" " "knop" #: ../../content/administration/maintain/on_premise.rst:48 msgid "" "A confirmation message will appear; make sure this is the correct database " "as it will be deactivated shortly:" msgstr "" "Een bevestigingsbericht zal verschijnen; zorg ervoor dat dit zeker de " "correcte database is en ze wordt binnenkort gedeactiveerd:" #: ../../content/administration/maintain/on_premise.rst:55 msgid "Do you have the updated version of Odoo 9?" msgstr "Heeft u de geüpdatet versie van Odoo 9?" #: ../../content/administration/maintain/on_premise.rst:57 #: ../../content/administration/maintain/on_premise.rst:167 msgid "" "From July 2016 onward, Odoo 9 now automatically change the uuid of a " "duplicated database; a manual operation is no longer required." msgstr "" #: ../../content/administration/maintain/on_premise.rst:60 msgid "" "If it's not the case, you may have multiple databases sharing the same UUID." " Please check on your `Odoo Contract " "`__, a short message will appear " "specifying which database is problematic:" msgstr "" #: ../../content/administration/maintain/on_premise.rst:69 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 " "`." msgstr "" #: ../../content/administration/maintain/on_premise.rst:72 msgid "" "For your information, we identify database with UUID. Therefore, each " "database should have a distinct UUID to ensure that registration and " "invoicing proceed effortlessly for your and for us." msgstr "" #: ../../content/administration/maintain/on_premise.rst:76 msgid "Check your network and firewall settings" msgstr "" #: ../../content/administration/maintain/on_premise.rst:78 msgid "" "The Update notification must be able to reach Odoo's subscription validation" " servers. In other words, make sure that the Odoo server is able to open " "outgoing connections towards:" msgstr "" #: ../../content/administration/maintain/on_premise.rst:82 msgid "services.odoo.com on port 443 (or 80)" msgstr "" #: ../../content/administration/maintain/on_premise.rst:83 msgid "services.openerp.com on port 443 (or 80) for older deployments" msgstr "" #: ../../content/administration/maintain/on_premise.rst:85 msgid "" "Once you activated your database, you must keep these ports open, as the " "Update notification runs once a week." msgstr "" #: ../../content/administration/maintain/on_premise.rst:91 msgid "Error message due to too many users" msgstr "Foutmelding vanwege te veel gebruikers" #: ../../content/administration/maintain/on_premise.rst:93 msgid "" "If you have more users in your local database than provisionned in your Odoo" " Enterprise subscription, you may encounter this message:" msgstr "" "Indien u meer gebruikers in uw lokale database heeft dan toegewezen in uw " "Odoo Enterprise abonnement kan u deze melding krijgen:" #: ../../content/administration/maintain/on_premise.rst:102 msgid "" "When the message appears you have 30 days before the expiration. The " "countdown is updated everyday." msgstr "" "Wanneer het bericht verschijnt heeft u 30 dagen voordat de database vervalt." " De teller wordt elke dag geüpdatet." #: ../../content/administration/maintain/on_premise.rst:108 msgid "" "**Add more users** on your subscription: follow the link and Validate the " "upsell quotation and pay for the extra users." msgstr "" #: ../../content/administration/maintain/on_premise.rst:110 msgid "" "**Deactivate users** as explained in this `documentation " "`_ and **Reject** the upsell " "quotation." msgstr "" #: ../../content/administration/maintain/on_premise.rst:113 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 ` to make the " "message disappear right away." msgstr "" #: ../../content/administration/maintain/on_premise.rst:120 msgid "Database expired error message" msgstr "Database vervallen foutmelding" #: ../../content/administration/maintain/on_premise.rst:122 msgid "" "If your database reaches its expiration date before your renew your " "subscription, you will encounter this message:" msgstr "" #: ../../content/administration/maintain/on_premise.rst:130 msgid "" "This **blocking** message appears after a non-blocking message that lasts 30" " days. If you fail to take action before the end of the countdown, the " "database is expired." msgstr "" #: ../../content/administration/maintain/on_premise.rst:138 msgid "" "Renew your subscription: follow the link and renew your subscription - note " "that" msgstr "" "Vernieuw uw abonnement: volg de link en vernieuw uw abonnement - merk op dat" #: ../../content/administration/maintain/on_premise.rst:137 msgid "" "if you wish to pay by Wire Transfer, your subscription will effectively be " "renewed only when the payment arrives, which can take a few days. Credit " "card payments are processed immediately." msgstr "" #: ../../content/administration/maintain/on_premise.rst:140 msgid "Contact our `Support `__" msgstr "Contacteer onze `support `__" #: ../../content/administration/maintain/on_premise.rst:142 msgid "" "None of those solutions worked for you? Please contact our `Support " "`__" msgstr "" "Werkte deze oplossingen niet voor u? Contacteer dan onze `Support " "`__" #: ../../content/administration/maintain/on_premise.rst:151 msgid "Duplicate a database" msgstr "Dupliceer een database" #: ../../content/administration/maintain/on_premise.rst:153 msgid "" "You can duplicate your database by accessing the database manager on your " "server (/web/database/manager). In this page, you can easily " "duplicate your database (among other things)." msgstr "" #: ../../content/administration/maintain/on_premise.rst:161 msgid "" "When you duplicate a local database, it is **strongly** advised to change " "the duplicated database's uuid (Unniversally Unique Identifier), since this " "uuid is how your database identifies itself with our servers. Having two " "databases with the same uuid could result in invoicing problems or " "registration problems down the line." msgstr "" #: ../../content/administration/maintain/on_premise.rst:170 msgid "" "The database uuid is currently accessible from the menu " ":menuselection:`Settings --> Technical --> System Parameters`, we advise you" " to use a `uuid generator `_ or to use the unix " "command ``uuidgen`` to generate a new uuid. You can then simply replace it " "like any other record by clicking on it and using the edit button." msgstr "" #: ../../content/administration/maintain/online.rst:3 msgid "Online (SaaS) database management" msgstr "" #: ../../content/administration/maintain/online.rst:5 msgid "" "To manage a database, sign in to https://www.odoo.com and access the " "`database management page `_ by clicking " "on the user icon, then on *My Databases*." msgstr "" #: ../../content/administration/maintain/online.rst:13 msgid "" "Make sure you are connected as the administrator of the database you want to" " manage." msgstr "" #: ../../content/administration/maintain/online.rst:19 msgid "" "Open the drop-down menu next to the database you want to manage by clicking " "on the gear icon." msgstr "" #: ../../content/administration/maintain/online.rst:21 msgid "Several actions are available:" msgstr "Meerdere acties zijn mogelijk:" #: ../../content/administration/maintain/online.rst:23 msgid ":ref:`online/upgrade`" msgstr "" #: ../../content/administration/maintain/online.rst:24 msgid ":ref:`online/duplicate`" msgstr "" #: ../../content/administration/maintain/online.rst:25 msgid ":ref:`online/rename`" msgstr "" #: ../../content/administration/maintain/online.rst:26 msgid ":ref:`online/download`" msgstr "" #: ../../content/administration/maintain/online.rst:27 msgid ":ref:`online/domains`" msgstr "" #: ../../content/administration/maintain/online.rst:28 msgid ":ref:`online/tags`" msgstr "" #: ../../content/administration/maintain/online.rst:29 msgid ":ref:`online/delete`" msgstr "" #: ../../content/administration/maintain/online.rst:30 msgid ":ref:`online/contact-support`" msgstr "" #: ../../content/administration/maintain/online.rst:31 msgid ":ref:`online/users`" msgstr "" #: ../../content/administration/maintain/online.rst:36 #: ../../content/administration/upgrade.rst:10 msgid "Upgrade" msgstr "Bijwerken" #: ../../content/administration/maintain/online.rst:38 msgid "" "If you are *not* on the latest **Online version**, you should receive an " "invitation to :doc:`upgrade <../upgrade>` your database. A **Rolling Release" " button** on your database's main screen proposes an upgrade to the latest " "version (e.g., 13.0 to 15.1)." msgstr "" #: ../../content/administration/maintain/online.rst:0 msgid "" "**If your Odoo database's version is lower than the latest major release:**" msgstr "" #: ../../content/administration/maintain/online.rst:0 msgid "" "You must upgrade your database within two months. After these two months, an" " automatic upgrade is initiated." msgstr "" #: ../../content/administration/maintain/online.rst:0 msgid "" "**If your Odoo database's version is equal to or higher than the latest " "major release:**" msgstr "" #: ../../content/administration/maintain/online.rst:0 msgid "" "You can disregard the invitation to upgrade as you probably wouldn't benefit" " from new features every two months." msgstr "" #: ../../content/administration/maintain/online.rst:51 msgid "" "Versions that are not supported anymore become deprecated and need to be " "updated to avoid security issues. We recommend you initiate the upgrade of " "the database yourself, as this method allows you to request a test upgrade " "of your database to check for any discrepancies." msgstr "" #: ../../content/administration/maintain/online.rst:56 msgid ":doc:`../upgrade`" msgstr "" #: ../../content/administration/maintain/online.rst:57 msgid ":doc:`supported_versions`" msgstr "" #: ../../content/administration/maintain/online.rst:62 msgid "Duplicate" msgstr "Dupliceren" #: ../../content/administration/maintain/online.rst:64 msgid "" "Make an exact copy of the database to be able to perform testing without " "compromising the daily operations." msgstr "" #: ../../content/administration/maintain/online.rst:68 msgid "" "By checking *For testing purposes*, all external communication (emails, " "payments, delivery orders, etc.) are disabled by default on the duplicated " "database." msgstr "" #: ../../content/administration/maintain/online.rst:70 msgid "Duplicate databases expire automatically after 15 days." msgstr "Gedupliceerde databases verlopen automatisch na 15 dagen." #: ../../content/administration/maintain/online.rst:75 msgid "Rename" msgstr "Naam wijzigen" #: ../../content/administration/maintain/online.rst:77 msgid "Rename the database and its URL." msgstr "" #: ../../content/administration/maintain/online.rst:82 msgid "Download" msgstr "Downloaden" #: ../../content/administration/maintain/online.rst:84 msgid "Download instantly a ZIP file with a backup of the database." msgstr "" #: ../../content/administration/maintain/online.rst:87 msgid "" "Databases are backed up daily according to the `Odoo Cloud SLA " "`_." msgstr "" #: ../../content/administration/maintain/online.rst:93 msgid "Domains" msgstr "" #: ../../content/administration/maintain/online.rst:95 msgid "Configure custom domains to access the database via another URL." msgstr "" #: ../../content/administration/maintain/online.rst:98 msgid ":doc:`domain_names`" msgstr "" #: ../../content/administration/maintain/online.rst:103 msgid "Tags" msgstr "Labels" #: ../../content/administration/maintain/online.rst:105 msgid "" "Add tags to sort your databases out. You can search the tags in the search " "bar." msgstr "" #: ../../content/administration/maintain/online.rst:110 #: ../../content/administration/odoo_sh/getting_started/branches.rst:528 msgid "Delete" msgstr "Verwijderen" #: ../../content/administration/maintain/online.rst:112 msgid "Delete a database instantly." msgstr "" #: ../../content/administration/maintain/online.rst:115 msgid "" "Deleting a database means that all data is permanently lost. The deletion is" " instant and for all users. It is recommended to create a backup of the " "database before deleting it." msgstr "" #: ../../content/administration/maintain/online.rst:118 msgid "" "Read carefully the warning message that pops up and proceed only if you " "fully understand the implications of deleting a database:" msgstr "" #: ../../content/administration/maintain/online.rst:126 msgid "Only an administrator can delete a database." msgstr "" #: ../../content/administration/maintain/online.rst:127 msgid "The database name is immediately available for a new database." msgstr "" #: ../../content/administration/maintain/online.rst:128 msgid "" "It is not possible to delete a database if it is expired or linked to a " "subscription. If needed, please get in touch with `Odoo Support " "`_." msgstr "" #: ../../content/administration/maintain/online.rst:130 msgid "" "To delete your account, please get in touch with `Odoo Support " "`_." msgstr "" #: ../../content/administration/maintain/online.rst:135 msgid "Contact Support" msgstr "Neem contact op met support" #: ../../content/administration/maintain/online.rst:137 msgid "" "Access the Odoo `support page `_ with your " "database's details already pre-filled." msgstr "" #: ../../content/administration/maintain/online.rst:143 msgid "Invite / Remove Users" msgstr "" #: ../../content/administration/maintain/online.rst:145 msgid "" "To invite users, fill out the email address of the new user and click on " "*Invite*. To add multiple users, click on *Add more users*." msgstr "" #: ../../content/administration/maintain/online.rst:152 msgid "To remove users, select the users to remove and click on *Remove*." msgstr "" #: ../../content/administration/maintain/online.rst:155 msgid ":doc:`/applications/general/users/manage_users`" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:6 #: ../../content/administration/upgrade.rst:208 msgid "Supported versions" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:8 msgid "" "Odoo provides support and bug fixing **for the 3 last major versions** of " "Odoo." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:11 msgid "" "Odoo releases intermediary versions called **Online versions** on the " ":doc:`Odoo Online ` hosting every two months. Odoo Online users can " "then benefit from the latest features of Odoo." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:14 msgid "" "Admins of Odoo Online databases are invited to :doc:`upgrade <../upgrade>` " "them regularly." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:15 msgid "" "Online versions are *not* released for Odoo.sh and On-Premise installations." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:16 msgid "Online versions are listed below as *SaaS*." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:19 msgid "What's the support status of my Odoo?" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:21 msgid "This matrix shows the support status of every version." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:23 msgid "**Major releases are in bold type.**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:26 #: ../../content/administration/upgrade/on_premise.rst:3 msgid "On-Premise" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:26 msgid "Release date" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:26 msgid "End of support" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:28 msgid "Odoo saas~15.2" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:28 #: ../../content/administration/maintain/supported_versions.rst:32 #: ../../content/administration/maintain/supported_versions.rst:32 #: ../../content/administration/maintain/supported_versions.rst:32 #: ../../content/administration/maintain/supported_versions.rst:34 #: ../../content/administration/maintain/supported_versions.rst:34 #: ../../content/administration/maintain/supported_versions.rst:34 #: ../../content/administration/maintain/supported_versions.rst:36 #: ../../content/administration/maintain/supported_versions.rst:36 #: ../../content/administration/maintain/supported_versions.rst:36 msgid "|green|" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:28 #: ../../content/administration/maintain/supported_versions.rst:28 #: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/maintain/supported_versions.rst:38 #: ../../content/administration/maintain/supported_versions.rst:38 #: ../../content/administration/maintain/supported_versions.rst:42 #: ../../content/administration/maintain/supported_versions.rst:42 #: ../../content/administration/maintain/supported_versions.rst:46 #: ../../content/administration/maintain/supported_versions.rst:46 #: ../../content/administration/maintain/supported_versions.rst:48 #: ../../content/administration/maintain/supported_versions.rst:48 #: ../../content/administration/maintain/supported_versions.rst:52 #: ../../content/administration/maintain/supported_versions.rst:52 #: ../../content/administration/maintain/supported_versions.rst:54 #: ../../content/administration/maintain/supported_versions.rst:56 #: ../../content/administration/maintain/supported_versions.rst:56 #: ../../content/administration/maintain/supported_versions.rst:58 msgid "N/A" msgstr "N/B" #: ../../content/administration/maintain/supported_versions.rst:28 msgid "March 2022" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:30 msgid "Odoo saas~15.1" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:30 #: ../../content/administration/maintain/supported_versions.rst:38 #: ../../content/administration/maintain/supported_versions.rst:40 #: ../../content/administration/maintain/supported_versions.rst:40 #: ../../content/administration/maintain/supported_versions.rst:40 #: ../../content/administration/maintain/supported_versions.rst:42 #: ../../content/administration/maintain/supported_versions.rst:44 #: ../../content/administration/maintain/supported_versions.rst:44 #: ../../content/administration/maintain/supported_versions.rst:44 #: ../../content/administration/maintain/supported_versions.rst:46 #: ../../content/administration/maintain/supported_versions.rst:48 #: ../../content/administration/maintain/supported_versions.rst:50 #: ../../content/administration/maintain/supported_versions.rst:50 #: ../../content/administration/maintain/supported_versions.rst:50 #: ../../content/administration/maintain/supported_versions.rst:52 #: ../../content/administration/maintain/supported_versions.rst:54 #: ../../content/administration/maintain/supported_versions.rst:54 #: ../../content/administration/maintain/supported_versions.rst:56 #: ../../content/administration/maintain/supported_versions.rst:58 #: ../../content/administration/maintain/supported_versions.rst:58 msgid "|red|" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:30 msgid "February 2022" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:32 msgid "**Odoo 15.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:32 #: ../../content/administration/maintain/supported_versions.rst:40 msgid "October 2021" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:32 msgid "October 2024 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:34 msgid "**Odoo 14.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:34 #: ../../content/administration/maintain/supported_versions.rst:44 msgid "October 2020" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:34 msgid "October 2023 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:36 msgid "**Odoo 13.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:36 #: ../../content/administration/maintain/supported_versions.rst:50 msgid "October 2019" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:36 msgid "October 2022 (planned)" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:38 msgid "Odoo saas~12.3" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:38 msgid "August 2019" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:40 msgid "**Odoo 12.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:40 #: ../../content/administration/maintain/supported_versions.rst:54 msgid "October 2018" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:42 msgid "Odoo saas~11.3" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:42 msgid "April 2018" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:44 msgid "**Odoo 11.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:44 #: ../../content/administration/maintain/supported_versions.rst:58 msgid "October 2017" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:46 msgid "Odoo 10.saas~15" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:46 msgid "March 2017" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:48 msgid "Odoo 10.saas~14" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:48 msgid "January 2017" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:50 msgid "**Odoo 10.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:50 msgid "October 2016" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:52 msgid "Odoo 9.saas~11" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:52 msgid "May 2016" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:54 msgid "**Odoo 9.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:54 msgid "October 2015" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:56 msgid "Odoo 8.saas~6" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:56 msgid "February 2015" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:58 msgid "**Odoo 8.0**" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:58 msgid "September 2014" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:63 msgid "|green| Supported version" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:65 msgid "|red| End-of-support" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:67 msgid "N/A Never released for this platform" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:69 msgid "🏁 Future version, not released yet" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:81 msgid "I run an older version of Odoo/OpenERP/TinyERP" msgstr "" #: ../../content/administration/maintain/supported_versions.rst:83 msgid "" "OpenERP 7.0, 6.1, 6.0 and 5.0 is not supported anymore, on any platform." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:85 msgid "" "TinyERP 4.0, 3.0, 2.0 and 1.0 is not supported anymore, on any platform." msgstr "" #: ../../content/administration/maintain/supported_versions.rst:87 msgid "" "Even though we don't support older versions, you can always `upgrade from " "any version `_." msgstr "" #: ../../content/administration/maintain/update.rst:6 msgid "Bugfix updates" msgstr "" #: ../../content/administration/maintain/update.rst:9 msgid "Introduction" msgstr "Introductie" #: ../../content/administration/maintain/update.rst:11 msgid "" "In order to benefit from the latest improvements, security fixes, bug " "corrections and performance boosts, you may need to update your Odoo " "installation from time to time." msgstr "" #: ../../content/administration/maintain/update.rst:14 msgid "" "This guide only applies when are using Odoo on your own hosting " "infrastructure. If you are using one of the Odoo Cloud solutions, updates " "are automatically performed for you." msgstr "" #: ../../content/administration/maintain/update.rst:17 msgid "" "The terminology surrounding software updates is often confusing, so here are" " some preliminary definitions:" msgstr "" #: ../../content/administration/maintain/update.rst:25 msgid "Updating (an Odoo installation)" msgstr "" #: ../../content/administration/maintain/update.rst:21 msgid "" "Refers to the process of obtaining the latest revision of the source code " "for your current Odoo Edition. For example, updating your Odoo Enterprise " "13.0 to the latest revision. This does not directly cause any change to the " "contents of your Odoo database, and can be undone by reinstalling the " "previous revision of the source code." msgstr "" #: ../../content/administration/maintain/update.rst:35 msgid "Upgrading (an Odoo database)" msgstr "" #: ../../content/administration/maintain/update.rst:28 msgid "" "Refers to a complex data processing operation where the structure and " "contents of your database is permanently altered to make it compatible with " "a new release of Odoo. This operation is irreversible and typically " "accomplished via Odoo's `database upgrade service " "`_, when you decide to switch to a newer release " "of Odoo. Historically, this process has also been known as a \"migration\" " "because it involves moving data around inside the database, even though the " "database may end up at the same physical location after the upgrade." msgstr "" #: ../../content/administration/maintain/update.rst:37 msgid "" "This page describes the typical steps needed to *update* an Odoo " "installation to the latest version. If you'd like more information about " "upgrading a database, please visit the `Odoo Upgrade page " "`_ instead." msgstr "" #: ../../content/administration/maintain/update.rst:43 msgid "In a nutshell" msgstr "" #: ../../content/administration/maintain/update.rst:45 msgid "" "Updating Odoo is accomplished by simply reinstalling the latest version of " "your Odoo Edition on top of your current installation. This will preserve " "your data without any alteration, as long as you do not uninstall PostgreSQL" " (the database engine that comes with Odoo)." msgstr "" #: ../../content/administration/maintain/update.rst:49 msgid "" "The main reference for updating is logically our :ref:`installation guide " "`, which explains the common installation methods." msgstr "" #: ../../content/administration/maintain/update.rst:52 msgid "" "Updating is also most appropriately accomplished by the person who deployed " "Odoo initially, because the procedure is very similar." msgstr "" #: ../../content/administration/maintain/update.rst:55 msgid "" "We always recommend to download a complete new up-to-date Odoo version, " "rather than manually applying patches, such as the security patches that " "come with Security Advisories. The patches are mainly provided for " "installations that are heavily customized, or for technical personnel who " "prefer to apply minimal changes temporarily while testing a complete update." msgstr "" #: ../../content/administration/maintain/update.rst:64 msgid "Step 1: Download an updated Odoo version" msgstr "" #: ../../content/administration/maintain/update.rst:66 msgid "" "The central download page is https://www.odoo.com/page/download. If you see " "a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " "into Odoo.com with the same login that is linked to your Odoo Enterprise " "subscription." msgstr "" #: ../../content/administration/maintain/update.rst:70 msgid "" "Alternatively, you can use the unique download link that was included with " "your Odoo Enterprise purchase confirmation email." msgstr "" #: ../../content/administration/maintain/update.rst:73 msgid "" "Downloading an updated version is not necessary if you installed via Github " "(see below)" msgstr "" #: ../../content/administration/maintain/update.rst:77 msgid "Step 2: Make a backup of your database" msgstr "" #: ../../content/administration/maintain/update.rst:79 msgid "" "The update procedure is quite safe and should not alter you data. However " "it's always best to take a full database backup before performing any change" " on your installation, and to store it somewhere safe, on a different " "computer." msgstr "" #: ../../content/administration/maintain/update.rst:83 msgid "" "If you have not disabled the database manager screen (see :ref:`here " "` why you should), you can use it (link at bottom of your database" " selection screen) to download a backup of your database(s). If you disabled" " it, use the same procedure than for your usual backups." msgstr "" #: ../../content/administration/maintain/update.rst:89 msgid "Step 3: Install the updated version" msgstr "" #: ../../content/administration/maintain/update.rst:91 msgid "Choose the method that matches your current installation:" msgstr "" #: ../../content/administration/maintain/update.rst:95 msgid "Packaged Installers" msgstr "" #: ../../content/administration/maintain/update.rst:97 msgid "" "If you installed Odoo with an installation package downloaded on our website" " (the recommended method), updating is very simple. All you have to do is " "download the installation package corresponding to your system (see step #1)" " and install it on your server. They are updated daily and include the " "latest security fixes. Usually, you can simply double-click the package to " "install it on top of the current installation. After installing the package," " be sure to restart the Odoo service or reboot your server, and you're all " "set." msgstr "" #: ../../content/administration/maintain/update.rst:106 msgid "Source Install (Tarball)" msgstr "" #: ../../content/administration/maintain/update.rst: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/maintain/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/maintain/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/maintain/update.rst:125 msgid "Source Install (Github)" msgstr "" #: ../../content/administration/maintain/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/maintain/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/maintain/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/maintain/update.rst:143 msgid "" "Finally, restart the Odoo service or reboot the machine, and you should be " "done." msgstr "" #: ../../content/administration/maintain/update.rst:149 msgid "" "Please refer to our `Docker image documentation " "`_ for specific update instructions." msgstr "" #: ../../content/administration/odoo_sh/advanced.rst:5 msgid "Advanced" msgstr "Geavanceerd" #: ../../content/administration/odoo_sh/advanced/containers.rst:4 msgid "Containers" msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:7 #: ../../content/administration/odoo_sh/advanced/submodules.rst:9 #: ../../content/administration/odoo_sh/getting_started/branches.rst: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:5 msgid "Overview" msgstr "Overzicht" #: ../../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 " "`_ documentation can help you write a :file:`requirements.txt` " "file. To have a concrete example, check out the `requirements.txt file of " "Odoo `_." 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 " "`_" " 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 " "`_ " "(*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 " "`." 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 `_ is installed by default " "in every container." msgstr "" #: ../../content/administration/odoo_sh/advanced/containers.rst:197 msgid "" "If you want to use `pudb `_ or `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 "of" #: ../../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 " "`_: 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 `_ " "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 " "`." 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 `." 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 "Vervangen" #: ../../content/administration/odoo_sh/advanced/submodules.rst:84 msgid "" "*:* by the SSH URL of the " "repository you want to add as submodule," msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:85 msgid "** by the branch you want to use in the above repository," msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:86 msgid "** 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 "" " 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 "" " 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 `_ 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 `_." msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:107 msgid "Ignore modules" msgstr "" #: ../../content/administration/odoo_sh/advanced/submodules.rst:109 msgid "" "If you're adding a repository that contains a lot of modules, you may want " "to ignore some of them in case there are any that are installed " "automatically. To do so, you can prefix your submodule folder with a " ":code:`.`. The platform will ignore this folder and you can hand pick your " "modules by creating symlinks to them from another folder." msgstr "" #: ../../content/administration/odoo_sh/getting_started.rst:5 msgid "Get started" msgstr "Beginnen" #: ../../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 "Fases" #: ../../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 "Productie" #: ../../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 " "`." 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 ` 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 "Ontwikkeling" #: ../../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 `." 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 `." 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 "Tabs" #: ../../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 "Geschiedenis" #: ../../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 "E-mails" #: ../../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 "Editor" #: ../../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:219 #: ../../content/administration/odoo_sh/getting_started/settings.rst:56 #: ../../content/administration/odoo_sh/getting_started/settings.rst:68 msgid "Logs" msgstr "Logs" #: ../../content/administration/odoo_sh/getting_started/branches.rst:220 msgid "A viewer to have a look to your server logs." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:225 msgid "Different logs are available:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:227 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:228 msgid "pip.log: The logs of the Python dependencies installation." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:229 msgid "odoo.log: The logs of the running server." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:230 msgid "update.log: The logs of the database updates." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:231 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:233 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:236 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:242 #: ../../content/administration/odoo_sh/getting_started/settings.rst:76 msgid "Backups" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:243 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:249 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:252 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:256 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:259 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 `_." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:262 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:268 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:274 msgid "" "The *import database* feature accepts database archives in the format " "provided by:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:276 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:278 msgid "the Odoo online databases manager," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:279 msgid "the Odoo.sh backup download button of this *Backups* tab," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:280 msgid "" "the Odoo.sh dump download button in the :ref:`Builds view `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:285 #: ../../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 "Instellingen" #: ../../content/administration/odoo_sh/getting_started/branches.rst:286 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:291 msgid "**Behaviour upon new commit**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:293 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 `). 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:301 msgid "**Modules installation**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:303 msgid "" "Choose the modules to install automatically for your development builds." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:308 msgid "" "*Install only my modules* will install the modules of the branch only. This " "is the default option. The :ref:`submodules ` " "are excluded." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:310 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:312 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:315 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:320 msgid "**Test suite**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:322 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 " "`." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:326 msgid "**Odoo Version**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:328 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:331 msgid "" "In addition, for each version you have two options regarding the code " "update." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:333 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:335 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:340 msgid "**Custom domains**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:342 msgid "" "Here you can configure additional domains for the selected branch. It's " "possible to add other *.odoo.com* domains or your own custom domains. " "For the latter you have to:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:345 msgid "own or purchase the domain name," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:346 msgid "add the domain name in this list," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:347 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:350 msgid "" "For instance, to associate *www.mycompany.com* to your database " "*mycompany.odoo.com*:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:352 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:353 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:356 msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:358 msgid "they can only be configured using ``A`` records," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:359 msgid "``A`` records only accept IP addresses as value," msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:360 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:363 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:365 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 " "`_ (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:372 msgid "**HTTPS/SSL**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:374 msgid "" "If the redirection is correctly set up, the platform will automatically " "generate an SSL certificate with `Let's Encrypt " "`_ within the hour and your domain will be " "accessible through HTTPS." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:378 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:382 msgid "**SPF and DKIM compliance**" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:384 msgid "" "In case the domain of your users email addresses use SPF (Sender Policy " "Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " "Odoo as a sending host in your domain name settings to increase the " "deliverability of your outgoing emails. The configuration steps are " "explained in the documentation about :ref:`SPF " "` and :ref:`DKIM " "`." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:392 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:397 msgid "Shell commands" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:398 msgid "" "In the top right-hand corner of the view, different shell commands are " "available." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:403 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 ````, ````, ..." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:409 msgid "Clone" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:410 msgid "Download the Git repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:416 msgid "Clones the repository *odoo/odoo*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:418 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:419 msgid "" ":code:`--branch`: checks out a specific branch of the repository, in this " "case *master*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:421 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:424 msgid "Fork" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:425 msgid "Create a new branch based on the current branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:431 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:437 msgid "Uploads the new branch *feature-1* on your remote repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:440 msgid "Merge" msgstr "Samenvoegen" #: ../../content/administration/odoo_sh/getting_started/branches.rst:441 msgid "Merge the current branch in another branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:447 msgid "Merges the branch *staging-1* in the current branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:453 #: ../../content/administration/odoo_sh/getting_started/branches.rst:525 msgid "" "Uploads the changes you just added in the *master* branch on your remote " "repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:456 msgid "SSH" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:458 msgid "Setup" msgstr "Instellingen" #: ../../content/administration/odoo_sh/getting_started/branches.rst:459 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:462 msgid "" "`Generate a new SSH key `_" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:464 msgid "" "`Copy the SSH key to your clipboard " "`_ (only apply the step 1)" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:467 msgid "Paste the copied content to your profile SSH keys and press \"Add\"" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:472 msgid "The key should appear below" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:478 msgid "Connection" msgstr "Connectie" #: ../../content/administration/odoo_sh/getting_started/branches.rst:480 msgid "" "To connect to your builds using ssh use the following command in a terminal:" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:486 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:491 msgid "" "Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" " build." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:495 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:500 msgid "Submodule" msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:502 msgid "" "Add a branch from another repository in your current branch as a " "*submodule*." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:504 msgid "" "*Submodules* allows you to use modules from other repositories in your " "project." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:506 msgid "" "The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:513 msgid "" "Adds the branch *master* of the repository ** as a submodule under the " "path ** in your current branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:519 msgid "Commits all your current changes." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:530 msgid "Delete a branch from your repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:536 msgid "Deletes the branch in your remote repository." msgstr "" #: ../../content/administration/odoo_sh/getting_started/branches.rst:542 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 `_ & `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 "Opties" #: ../../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 `: *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 `_ 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 `_ 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 " "`_." 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 it is in a " ":doc:`supported version ` of " "Odoo." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:85 msgid "Push your modules in production" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:87 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:91 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:95 msgid "" "For community modules available in public Git repositories, you can also " "consider to add them using :ref:`Submodules `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:98 msgid "" "Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " "branch `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:102 msgid "Download a backup" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:105 msgid "On-premise databases" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:107 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:111 msgid "" "If you cannot access the database manager, it may have been disabled by your" " system administrator. See the :ref:`database manager security documentation" " `." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:114 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:119 msgid "Choose a zip including the filestore as the backup format." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:125 msgid "Odoo Online databases" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:127 msgid "" "`Access your databases manager " "`_ and download a backup of " "your database." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:134 msgid "Saas releases (e.g. *saas-**) are not supported on Odoo.sh." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:137 msgid "Upload the backup" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:139 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:144 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:150 msgid "Check your outgoing email servers" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:152 msgid "" "There is a default mail server provided with Odoo.sh. To use it, there must " "be no enabled outgoing mail server configured in your database in " ":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " "(:ref:`Developer mode ` must be activated)." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:157 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:162 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:165 msgid "Check your scheduled actions" msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:167 msgid "All scheduled actions are disabled after the import." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:169 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:173 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:178 msgid "Register your subscription" msgstr "Registreer je abonnement" #: ../../content/administration/odoo_sh/getting_started/create.rst:180 msgid "Your subscription is unlinked after the import." msgstr "" #: ../../content/administration/odoo_sh/getting_started/create.rst:182 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:185 msgid "" "If you plan to make it your production, unlink your former database from the" " subscription, and register the newly imported database. Read the " ":doc:`database registration documentation <../../maintain/on_premise>` for " "instructions." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst: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 `, 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 " "`:" 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 ` 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 "Handmatig" #: ../../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 ` 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 ` of the :ref:`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 :ref:`developer mode `" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 msgid "in the apps menu, click the *Update Apps List* button," msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 msgid "in the dialog that appears, click the *Update* button." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 msgid "Your module will then appear in the list of available apps." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 msgid "Deploy in production" msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 msgid "" "Once you tested your module in a staging branch with your production data, " "and believe it is ready for production, you can merge your branch in the " "production branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 msgid "Drag and drop your staging branch on the production branch." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 msgid "" "This will merge the latest changes of your staging branch in the production " "branch, and update your production server with these latest changes." msgstr "" #: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 msgid "" "Your module will not be installed automatically, you have to install it " "manually as explained in the :ref:`above section about installing your " "module in staging databases `." 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 "Na" #: ../../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 "Toevoegen" #: ../../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 "met" #: ../../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 " "`_ 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 "Eerder" #: ../../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 " "`_." 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 " "`, :ref:`the 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 `_)," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 msgid "" "*/src/enterprise* (`odoo/enterprise `_)," msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:65 msgid "" "*/src/themes* (`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:`." 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 "" " 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" " `_ 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 " "`, 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 " "`_. One " "of the most interesting addition to use a Python console rather than a " "IPython shell within a terminal is the `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 " "`_." 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 " "`_ mentioned above." msgstr "" #: ../../content/administration/odoo_sh/getting_started/online-editor.rst:195 msgid "" "You can also use `pandas `_ 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 "Medewerkers" #: ../../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 "Gebruiker" #: ../../content/administration/odoo_sh/getting_started/settings.rst:50 msgid "Admin" msgstr "Admin" #: ../../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 "X" #: ../../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 "Status" #: ../../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 `." 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 ` 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 " "`_ 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 " "`_." 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 "Activatie" #: ../../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/upgrade.rst:20 msgid "" "An upgrade is switching to a newer version of Odoo (e.g., Odoo 14.0 to Odoo " "15.0)." msgstr "" #: ../../content/administration/upgrade.rst:22 msgid "An upgrade does not cover:" msgstr "" #: ../../content/administration/upgrade.rst:24 msgid "" "Changing :ref:`editions ` (i.e., Community to " "Enterprise edition)" msgstr "" #: ../../content/administration/upgrade.rst:25 msgid "" "Switching :ref:`hosting type ` (i.e., On-" "Premise to Online or Odoo.sh)" msgstr "" #: ../../content/administration/upgrade.rst:27 msgid "Migration from another ERP to Odoo" msgstr "" #: ../../content/administration/upgrade.rst:29 #: ../../content/administration/upgrade.rst:148 #: ../../content/administration/upgrade.rst:252 #: ../../content/administration/upgrade/faq.rst:81 #: ../../content/administration/upgrade/faq.rst:92 #: ../../content/administration/upgrade/faq.rst:119 msgid "|assistance-contact|" msgstr "" #: ../../content/administration/upgrade.rst:32 #: ../../content/administration/upgrade/odoo_sh.rst:66 msgid ":ref:`upgrade/sla`" msgstr "" #: ../../content/administration/upgrade.rst:37 msgid "Process workflow" msgstr "" #: ../../content/administration/upgrade.rst:39 msgid "The upgrade process in a nutshell:" msgstr "" #: ../../content/administration/upgrade.rst:41 msgid "You create a test upgrade request." msgstr "" #: ../../content/administration/upgrade.rst:42 msgid "" "Odoo processes the request automatically by running the database through an " "upgrade script, which takes between 20 and 120 minutes." msgstr "" #: ../../content/administration/upgrade.rst:44 msgid "Odoo delivers a test database." msgstr "" #: ../../content/administration/upgrade.rst:45 msgid "" "You test your database for possible discrepancies (see :ref:`upgrade/test-" "guidance`)." msgstr "" #: ../../content/administration/upgrade.rst:46 msgid "" "If there are any discrepancies, you report them to the Upgrade support team " "via the help portal (see :ref:`upgrade/test-assistance`)." msgstr "" #: ../../content/administration/upgrade.rst:48 msgid "We fix the issues and send you a new test database." msgstr "" #: ../../content/administration/upgrade.rst:49 msgid "" "Once you have 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/upgrade.rst:52 msgid "Odoo delivers the production database through the automated process." msgstr "" #: ../../content/administration/upgrade.rst:53 msgid "" "You restore it in your Production environment a few short hours later and " "continue working on the newly upgraded database (this is done automatically " "on Odoo Online)." msgstr "" #: ../../content/administration/upgrade.rst:57 msgid ":doc:`Upgrade process for Odoo Online (SaaS) `" msgstr "" #: ../../content/administration/upgrade.rst:58 msgid ":doc:`Upgrade process for Odoo.sh `" msgstr "" #: ../../content/administration/upgrade.rst:59 msgid ":doc:`Upgrade process for On-Premise `" msgstr "" #: ../../content/administration/upgrade.rst:64 msgid "Testing" msgstr "Testen" #: ../../content/administration/upgrade.rst:66 msgid "" "This phase allows you to review an upgraded version of your database without" " affecting your production database in any way. We suggest that you run the " "test upgrade process at least once, but you can do it as many times as you " "need (one at a time)." msgstr "" #: ../../content/administration/upgrade.rst:70 msgid "" "Once you receive your upgraded test database, check that all data, " "processes, and functionality are still correct and working as expected." msgstr "" #: ../../content/administration/upgrade.rst:73 msgid "" "If you do find discrepancies, :ref:`report your issues ` and :ref:`request a new test database ` when the reported issues are fixed in the upgrade script." msgstr "" #: ../../content/administration/upgrade.rst:77 msgid "" "If you do not find any discrepancies, you can move on to the upgrade of your" " production database." msgstr "" #: ../../content/administration/upgrade.rst:80 msgid "" "A test database is only intended for testing and remains completely " "unrelated to your present or future production database. Any data you add, " "or changes you make, will not be reflected in your upgraded production " "database." msgstr "" #: ../../content/administration/upgrade.rst:85 msgid "" "Test databases are neutered and features are disabled to prevent them from " "having an impact on the production database:" msgstr "" #: ../../content/administration/upgrade.rst:88 msgid "" "The serial number of the database is modified (to prevent it from sending " "information as if it was the production database)." msgstr "" #: ../../content/administration/upgrade.rst:90 msgid "" "The :ref:`base URL of the database ` is reset to " "``http://localhost:8069`` and the email domain to ``localhost``." msgstr "" #: ../../content/administration/upgrade.rst:92 msgid "" "Scheduled actions are disabled (the calendar synchronization, the bank " "statement synchronization, the planned automated actions, the fetching of " "incoming mail servers, etc.)." msgstr "" #: ../../content/administration/upgrade.rst:94 msgid "" "Outgoing mail servers are disabled by archiving the existing ones and adding" " a fake/non-working one." msgstr "" #: ../../content/administration/upgrade.rst:96 msgid "Payment providers and delivery carriers are reset to test environment." msgstr "" #: ../../content/administration/upgrade.rst:97 msgid "" "Accounting localization Electronic Data Interchange (EDI) services are " "disabled." msgstr "" #: ../../content/administration/upgrade.rst:98 msgid "A system parameter is set to tell the database has been neutered." msgstr "" #: ../../content/administration/upgrade.rst:103 msgid "Request a test database" msgstr "" #: ../../content/administration/upgrade.rst:105 msgid "" "Follow the instructions available per hosting type on the `website form " "`_ and select *Testing* purpose." msgstr "" #: ../../content/administration/upgrade.rst:115 msgid "Test guidance" msgstr "" #: ../../content/administration/upgrade.rst:117 msgid "" "Every business and organization has its own operational needs and has to " "test its specific Odoo database individually. We recommend you look at `the " "test scenario " "`_" " for further information." msgstr "" #: ../../content/administration/upgrade.rst:122 msgid "change link \"test scenario\" once the related doc is published" msgstr "" #: ../../content/administration/upgrade.rst:127 #: ../../content/administration/upgrade.rst:172 msgid "Assistance" msgstr "Pechhulp" #: ../../content/administration/upgrade.rst:129 msgid "" "If you encounter an issue in the **test database**, please get in touch with" " Odoo Upgrade Support via the `Odoo Support page " "`_." msgstr "" #: ../../content/administration/upgrade.rst:132 msgid "" "Under the *Ticket Description* section, select *An issue related to my " "upgrade* ticket type." msgstr "" #: ../../content/administration/upgrade.rst:139 msgid "" "If you choose another *Ticket Description* type, the request will be " "redirected to another team. This will slow down the processing and response " "time." msgstr "" #: ../../content/administration/upgrade.rst:142 #: ../../content/administration/upgrade.rst:185 msgid "" "Please provide as much detail as you can (i.e., videos and screenshots to " "illustrate your issue). This will avoid clarifying questions and speed up " "the resolution process significantly." msgstr "" #: ../../content/administration/upgrade.rst:146 msgid "" "The purpose of the test phase is not to correct existing data or " "configurations in your database." msgstr "" #: ../../content/administration/upgrade.rst:153 msgid "The production launch" msgstr "" #: ../../content/administration/upgrade.rst:155 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/upgrade.rst:159 msgid "" "After your :ref:`tests ` are completed to your " "satisfaction, submit the request to upgrade your production database via our" " `website form `_. Select *Production* purpose." msgstr "" #: ../../content/administration/upgrade.rst:164 msgid "Going into production without first testing may lead to:" msgstr "" #: ../../content/administration/upgrade.rst:166 msgid "" "business interruptions (e.g., no longer having the possibility to validate " "an action)" msgstr "" #: ../../content/administration/upgrade.rst:167 msgid "" "poor customer experiences (e.g., an eCommerce website that does not work " "correctly)" msgstr "" #: ../../content/administration/upgrade.rst:174 msgid "" "If you encounter issues or problems in the **production database**, please " "get in touch with **Odoo Support**:" msgstr "" #: ../../content/administration/upgrade.rst:177 msgid "Connect to our `Odoo Support page `_." msgstr "" #: ../../content/administration/upgrade.rst:178 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/upgrade.rst:182 msgid "" "After upgrading to production, the support will be provided by the Support " "team instead of the Upgrade team." msgstr "" #: ../../content/administration/upgrade.rst:189 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/upgrade.rst:195 msgid "Help" msgstr "Help" #: ../../content/administration/upgrade.rst:200 msgid "Contact our Upgrade service support" msgstr "" #: ../../content/administration/upgrade.rst:202 msgid "" "Should you have any more questions about the upgrade, do not hesitate to " "send a message to `Odoo Upgrade Team `_. We will be" " happy to answer it as soon as possible." msgstr "" #: ../../content/administration/upgrade.rst:210 msgid "" "Please note that Odoo provides support and bug fixing only for the three " "last major versions of Odoo." msgstr "" #: ../../content/administration/upgrade.rst:213 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 longer support (before having to upgrade again)." msgstr "" #: ../../content/administration/upgrade.rst:218 #: ../../content/administration/upgrade.rst:257 msgid ":doc:`maintain/supported_versions`" msgstr "" #: ../../content/administration/upgrade.rst:223 msgid "Service Level Agreement" msgstr "" #: ../../content/administration/upgrade.rst:226 msgid "What is covered by the Enterprise Licence?" msgstr "" #: ../../content/administration/upgrade.rst:228 msgid "" "Databases hosted on Odoo’s Cloud platforms (Saas and Odoo.sh) or On-Premise " "(Self-Hosting) enjoy the following services at all times." msgstr "" #: ../../content/administration/upgrade.rst:231 msgid "The upgrade of:" msgstr "" #: ../../content/administration/upgrade.rst:233 msgid "standard applications" msgstr "" #: ../../content/administration/upgrade.rst:234 msgid "" "Studio customization (as long as the :guilabel:`Studio` app is still active)" msgstr "" #: ../../content/administration/upgrade.rst:235 msgid "" "customizations done by our consulting and developer services *if* they are " "covered by a ‘Maintenance of Customisations’ subscription" msgstr "" #: ../../content/administration/upgrade.rst:238 msgid "" "The Upgrade Service is limited to your database's technical conversion and " "adaptation (standard modules and data) to make it compatible with the " "targeted version." msgstr "" #: ../../content/administration/upgrade.rst:242 msgid "What upgrading does NOT cover" msgstr "" #: ../../content/administration/upgrade.rst:244 msgid "The cleaning of pre-existing data & configuration while upgrading" msgstr "" #: ../../content/administration/upgrade.rst:245 msgid "" "Any new developments and/or upgrades of your own :ref:`custom modules " "`" msgstr "" #: ../../content/administration/upgrade.rst:247 msgid "`Training `_ on the latest version" msgstr "" #: ../../content/administration/upgrade.rst:249 msgid "" "You can get more information about your Enterprise Licence on our :ref:`Odoo" " Enterprise Subscription Agreement ` page." msgstr "" #: ../../content/administration/upgrade.rst:255 msgid ":doc:`upgrade/faq`" msgstr "" #: ../../content/administration/upgrade.rst:256 msgid ":doc:`odoo_sh`" msgstr "" #: ../../content/administration/upgrade/faq.rst:8 msgid "FAQ" msgstr "FAQ" #: ../../content/administration/upgrade/faq.rst:13 msgid "Why upgrade" msgstr "" #: ../../content/administration/upgrade/faq.rst:15 msgid "" "You benefit from the latest features of the :ref:`new major version " "` released by Odoo." msgstr "" #: ../../content/administration/upgrade/faq.rst:17 msgid "" "If you are in an :ref:`unsupported version `, " "you get a new version with support." msgstr "" #: ../../content/administration/upgrade/faq.rst:23 msgid "When to upgrade" msgstr "" #: ../../content/administration/upgrade/faq.rst:25 msgid "" "Whenever you want. You can make your upgrade request as soon as a new " "version is released or when your version turns unsupported, and you still " "wish to enjoy support." msgstr "" #: ../../content/administration/upgrade/faq.rst:31 msgid "Availability of the new version" msgstr "" #: ../../content/administration/upgrade/faq.rst:33 msgid "" "As soon as Odoo announces the release of a new major version, you can create" " a test upgrade request to try the latest version. Please note that at this " "point, the upgrade scripts will only have been tested with demo data. Please" " report any issue you might encounter while testing via the `Odoo Support " "page `_ and make sure to be happy with your test " "version before requesting the upgrade of your database in production." msgstr "" #: ../../content/administration/upgrade/faq.rst:42 msgid "Duration of the upgrade" msgstr "" #: ../../content/administration/upgrade/faq.rst:44 msgid "It is impossible to give time estimates for every upgrade request." msgstr "" #: ../../content/administration/upgrade/faq.rst:46 msgid "" "In general, the \"smaller\" the database, the quickest the upgrade request " "is completed. 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/upgrade/faq.rst:50 msgid "" "You can expect the time it takes for the platform to upgrade the test " "database to be similar to the production upgrade." msgstr "" #: ../../content/administration/upgrade/faq.rst:56 msgid "Duration of the upgrade project" msgstr "" #: ../../content/administration/upgrade/faq.rst:58 msgid "" "It depends on the user involvement (the time spent on testing, reporting " "problems, etc.) and the issues encountered that might need to be addressed " "by our technical team." msgstr "" #: ../../content/administration/upgrade/faq.rst:61 msgid "So, in a nutshell, what can impact your upgrade lead time?" msgstr "" #: ../../content/administration/upgrade/faq.rst:63 msgid "Source & targeted versions" msgstr "" #: ../../content/administration/upgrade/faq.rst:64 msgid "Installed apps" msgstr "" #: ../../content/administration/upgrade/faq.rst:65 msgid "Volume of data" msgstr "" #: ../../content/administration/upgrade/faq.rst:66 msgid "" "Amount of customization (models, fields, methods, workflows, reports, " "website, etc.)" msgstr "" #: ../../content/administration/upgrade/faq.rst:67 msgid "" "Installation of new apps or configuration changes after the start of the " "test phase" msgstr "" #: ../../content/administration/upgrade/faq.rst:68 msgid "User commitment" msgstr "" #: ../../content/administration/upgrade/faq.rst:73 msgid "Upgrade of the custom modules" msgstr "" #: ../../content/administration/upgrade/faq.rst:75 msgid "" "As stated in our :doc:`/legal/terms/enterprise`, section " ":ref:`charges_standard`, this optional service is subject to additional " "fees." msgstr "" #: ../../content/administration/upgrade/faq.rst:78 msgid "" "Depending on your situation, the custom code could be upgraded by our " "services, by one of our partners, or you can do it yourself." msgstr "" #: ../../content/administration/upgrade/faq.rst:86 msgid "Upgrade or Migration" msgstr "" #: ../../content/administration/upgrade/faq.rst:88 msgid "" "An upgrade is switching to a newer version of Odoo, while a migration " "reflects the change of :ref:`editions ` or " "change of :ref:`hosting type `." msgstr "" #: ../../content/administration/upgrade/faq.rst:97 msgid "Editions change (from Community to Enterprise)" msgstr "" #: ../../content/administration/upgrade/faq.rst:99 msgid "" "The upgrade always returns an Enterprise edition of Odoo, whether the " "database you sent was a community or enterprise edition. It is required to " "have an enterprise subscription to upgrade." msgstr "" #: ../../content/administration/upgrade/faq.rst:103 msgid "" "If you need assistance on this matter, please contact us via the `Odoo " "Support page `_." msgstr "" #: ../../content/administration/upgrade/faq.rst:107 msgid "`Editions `_" msgstr "" #: ../../content/administration/upgrade/faq.rst:112 msgid "" "Switching the hosting types (Self-Hosting vs. Online Hosting - SaaS vs. " "Cloud Platform - Odoo.sh)" msgstr "" #: ../../content/administration/upgrade/faq.rst:114 msgid "" "An upgrade does not cover a change of `Hosting types " "`_." msgstr "" #: ../../content/administration/upgrade/faq.rst:116 msgid "" "Open the following link to get :doc:`more information about how to change " "your hosting type <../maintain/hosting_changes>`." msgstr "" #: ../../content/administration/upgrade/faq.rst:124 msgid "The Upgrade Report" msgstr "" #: ../../content/administration/upgrade/faq.rst:126 msgid "" "When an upgrade request completes successfully (test or production), you " "receive an email notification about it that includes an 'Upgrade Report'. " "This report is also sent to you via the Discuss app. It contains valuable " "information regarding changes that occurred during the upgrade. While it " "serves as a guide to possible issues to look out for, it is not an " "exhaustive list. It remains imperative that you test the upgraded database " "thoroughly and report any discrepancies you might find, before you decide to" " upgrade your production database." msgstr "" #: ../../content/administration/upgrade/faq.rst:136 msgid "Custom views" msgstr "" #: ../../content/administration/upgrade/faq.rst:138 msgid "" "During the upgrade, some custom views might get disabled for technical " "reasons. Therefore they might have to be fixed after the upgrade. The " ":ref:`Upgrade Report ` that is generated after " "the upgrade is available in the Discuss app, and lists all the custom views " "that might be impacted by this." msgstr "" #: ../../content/administration/upgrade/faq.rst:146 msgid "Release Notes by version" msgstr "" #: ../../content/administration/upgrade/faq.rst:148 msgid "" "Open our `Release Note `_ page to " "get a summary of the new features and improvements made in each version." msgstr "" #: ../../content/administration/upgrade/faq.rst:152 msgid "How long is my test available for" msgstr "" #: ../../content/administration/upgrade/faq.rst:154 msgid "" "An Odoo Online (SaaS) test database is available for one month by default. " "We can extend this trial period upon request. For Odoo.sh or on-premise, " "there is no restriction." msgstr "" #: ../../content/administration/upgrade/faq.rst:158 msgid "How many tests to perform before upgrading to production?" msgstr "" #: ../../content/administration/upgrade/faq.rst:160 msgid "" "As many as needed. When you are comfortable with the database, run a last " "test upgrade 48 hours before requesting your production upgrade and test " "your workflows one last time." msgstr "" #: ../../content/administration/upgrade/faq.rst:164 msgid "How to/Where to report upgrade issues?" msgstr "" #: ../../content/administration/upgrade/faq.rst:166 msgid "" "If you encounter issues during the upgrade process, please contact the Odoo " "Support through the `Odoo Support page `_." msgstr "" #: ../../content/administration/upgrade/faq.rst:169 msgid "" "To report an issue discovered during the testing phase, please select **An " "issue related to my upgrade (test phase)**." msgstr "" #: ../../content/administration/upgrade/faq.rst:171 msgid "" "To report an issue discovered post-upgrade, please select **An issue related" " to my upgrade (production)**." msgstr "" #: ../../content/administration/upgrade/faq.rst:175 msgid "Upgrading to production" msgstr "" #: ../../content/administration/upgrade/faq.rst:177 msgid "" "Once you have completed 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/upgrade/faq.rst:182 msgid "How is my data handled in the Upgrade Platform?" msgstr "" #: ../../content/administration/upgrade/faq.rst:184 msgid "" "The Odoo Upgrade platform uses the same Privacy Policy as the rest of " "Odoo.com services." msgstr "" #: ../../content/administration/upgrade/faq.rst:186 msgid "" "Your data is hosted on servers that follow our security guidelines, namely:" msgstr "" #: ../../content/administration/upgrade/faq.rst:188 msgid "" "SSL - All web connections to client instances are protected with 256-bit SSL" " encryption (HTTPS with a 2048-bit modulus SSL certificate), and running " "behind Grade A SSL stacks. All our certificate chains are using SHA-2 " "already." msgstr "" #: ../../content/administration/upgrade/faq.rst:191 msgid "" "Safe System - Our servers are running recent Linux distribution with up-to-" "date security patches, with firewall and intrusion countermeasures (not " "disclosed for obvious reasons)." msgstr "" #: ../../content/administration/upgrade/faq.rst:194 msgid "" "Servers are located at the same locations as our Cloud providers with the " "following services:" msgstr "" #: ../../content/administration/upgrade/faq.rst:196 msgid "" "Restricted perimeter, physically accessed by authorized data center " "employees only" msgstr "" #: ../../content/administration/upgrade/faq.rst:197 msgid "Physical access control with security badges or biometrical security" msgstr "" #: ../../content/administration/upgrade/faq.rst:198 msgid "Security cameras monitoring the data center locations 24/7" msgstr "" #: ../../content/administration/upgrade/faq.rst:199 msgid "Security personnel on-site 24/7" msgstr "" #: ../../content/administration/upgrade/faq.rst:201 msgid "" "The uploaded and migrated databases uploaded to the Upgrade platform are " "kept for up to 3 months and are permanently deleted following that period." msgstr "" #: ../../content/administration/upgrade/faq.rst:204 msgid "" "You can learn more about privacy and data handling at Odoo by visiting our " "`General Data Protection Regulation page `_." msgstr "" #: ../../content/administration/upgrade/faq.rst:208 msgid "Rolling Release (applicable to Odoo Online databases)" msgstr "" #: ../../content/administration/upgrade/faq.rst:210 msgid "" "This feature allows customers to upgrade their database directly from a " "message prompt sent to the database administrator as soon as the new version" " is released. Odoo first tests the upgrade to the next version. The rolling " "release upgrade option is displayed if the automated tests are successful. " "The message offers two options:" msgstr "" #: ../../content/administration/upgrade/faq.rst:215 msgid "" "To 'Upgrade Now', which immediately triggers the upgrade of your live " "production database." msgstr "" #: ../../content/administration/upgrade/faq.rst:217 msgid "" "To take you to your `database manager `_" " where you can `request an upgraded test database " "`_ and check the upgraded test database " "for any discrepancies." msgstr "" #: ../../content/administration/upgrade/faq.rst:221 msgid "" "When you choose to proceed with the production upgrade directly, make sure " "all users have saved their work and are logged out. The upgrade takes " "approximately 15 minutes. During this time your database is unreachable. If " "you notice any problem after the upgrade, please report it via the `Odoo " "Support page `_." msgstr "" #: ../../content/administration/upgrade/faq.rst:227 msgid "" "If you are using the Website or Studio app, we recommend you always do a " "test upgrade before upgrading your production instance." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:7 #: ../../content/administration/upgrade/on_premise.rst:6 msgid "Test upgrade request" msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:9 msgid "" "Download a dump of your database (from the :ref:`Builds view `), choose the **exact copy** and " "**without filestore** options. Upload the .sql.gz dump on " "https://upgrade.odoo.com/upload and select the testing purpose. Once it's " "processed, you'll get a dump of the database in return." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:15 msgid "" "To have the most up-to-date test version of your database, create a backup " "of your production database just before creating your request. Upload it in " "your staging branch, select **Exact dump** and **Without filestore**, and " "then click *start*." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:20 msgid "Test your upgraded database" msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:22 msgid "" "At the beginning of your upgrade project, make sure that you create a new " "staging branch for testing purposes by forking your main branch." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:25 msgid "" "Once the staging build is complete (it doesn't matter if it failed due to " "the version incompatibility), import your upgraded dump in the *Backups* tab" " of the branch." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:29 msgid "" "The platform automatically detects the version of the dump and changes the " "version of Odoo's source code to the corresponding version of the build." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:32 msgid "" "Test the upgraded database and make sure everything runs as it's supposed " "to." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:35 #: ../../content/administration/upgrade/on_premise.rst:41 msgid "Upgrade your production database" msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:37 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/upgrade/odoo_sh.rst:40 msgid "Make a new dump of your production database (as described in step 1)" msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:41 msgid "Upload it on upgrade.odoo.com and select the Production purpose" msgstr "" #: ../../content/administration/upgrade/odoo_sh.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/upgrade/odoo_sh.rst:45 msgid "Merge or commit the upgraded custom code in the production branch" msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:47 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/upgrade/odoo_sh.rst:53 #: ../../content/administration/upgrade/on_premise.rst:48 msgid "Custom modules (if applicable)" msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:55 msgid "" "The upgrade of a database that contains custom modules is a 2 step process." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:57 #: ../../content/administration/upgrade/on_premise.rst:52 msgid "The standard upgrade is done when your upgrade request is completed." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:58 #: ../../content/administration/upgrade/on_premise.rst:53 msgid "" "Your custom modules also need to be upgraded to keep them compatible with " "the new version." msgstr "" #: ../../content/administration/upgrade/odoo_sh.rst:60 msgid "" "Depending on your contract, the upgrade of your custom modules can be done -" " by yourself - by your Partner - by Odoo (if you hold a subscription to " "'Maintenance of Customizations')" msgstr "" #: ../../content/administration/upgrade/on_premise.rst:8 msgid "There are two ways to create your upgrade request." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:11 msgid "Upgrade request via command line" msgstr "" #: ../../content/administration/upgrade/on_premise.rst:13 msgid "" "For technically-advanced users and partners, the upgrade process can be " "initiated via the following command line on the server where the database is" " hosted:" msgstr "" #: ../../content/administration/upgrade/on_premise.rst:16 msgid "" ":command:`python <(curl -s https://upgrade.odoo.com/upgrade) test -d -t `" msgstr "" #: ../../content/administration/upgrade/on_premise.rst:19 msgid "" "The above command creates the database dump, sends it to the upgrade " "platform, and initiates the automated upgrade process. During the upgrade, " "you can follow the live logs on your screen. Once the upgrade process is " "completed successfully, the upgraded database is restored onto the server " "(as a duplicate test database)." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:25 msgid "Upgrade request via the Odoo Upgrade Portal" msgstr "" #: ../../content/administration/upgrade/on_premise.rst:27 msgid "" "Download a recent copy of your database and select the option " ":guilabel:`pg_dump custom format (without filestore)`." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:29 msgid "" "Upload this dump file at https://upgrade.odoo.com and select *Testing* as " "the aim. Odoo performs the automated upgrade process. Once it is completed, " "you receive an email with a link to download the upgrade database dump file." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:32 msgid "" "Import the upgraded database into your on-premise environment and manually " "test all processes and workflows." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:36 msgid "" "For security reasons, only the person who submitted the upgrade request is " "able to download it." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:37 msgid "" "Any problem found during testing should be reported via the `helpdesk " "`_." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:43 msgid "" "Once you have completed the testing successfully, you can proceed to upgrade" " your live database in production. Download your upgraded database from the " "link in the email and import it onto your live environment." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:50 msgid "" "The upgrade of a database that contains custom modules is a two-step " "process." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:55 msgid "" "Depending on your contract, the upgrade of your custom modules can be done" msgstr "" #: ../../content/administration/upgrade/on_premise.rst:57 msgid "by yourself." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:58 msgid "by your Partner." msgstr "" #: ../../content/administration/upgrade/on_premise.rst:59 msgid "" "by Odoo (if you hold a subscription to 'Maintenance of Customizations')." msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:3 msgid "Odoo Online (SaaS)" msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:6 msgid "Requesting a test upgrade" msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:8 msgid "Go to your `database manager `_" msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:9 msgid "Click on your profile icon and select *My Databases*." msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:14 msgid "" "Click on the action settings icon next to your main database and select the " "*Upgrade* option." msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:19 msgid "In the pop-up message that will appear, select Test Upgrade." msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:24 msgid "" "This triggers the automated upgrade process. A confirmation email is then " "sent to you with the the link to the upgraded database or to provide " "information if the upgrade failed." msgstr "" #: ../../content/administration/upgrade/online_hosting.rst:28 msgid "" "You can also see and access your test database from your *My Databases* " "page." msgstr ""