NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

[MERGE] Forward-port of branch 12.0 to 13.0

Browse Source
This commit is contained in:
Victor Feyens
2021-05-17 18:29:11 +02:00
parent 9e77998bc1 ba72b396a4
commit 87ab494b42
80 changed files with 173 additions and 173 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/administration/odoo_sh/getting_started/branches.rst
+12 -12
View File
@@ -42,7 +42,7 @@ instance will be held temporarily unavailable for maintenance reason.
This method is equivalent to perform an upgrade of the module through the Apps menu,
or through the :code:`-u` switch of
`the command line <https://www.odoo.com/documentation/13.0/reference/cmdline.html>`_.
:doc:`the command line </developer/reference/cmdline>`.
In the case the changes in the commit prevent the server to restart,
or if the modules update fails,
@@ -257,16 +257,16 @@ This server only keeps one month of backups: 7 daily and 4 weekly backups.
Dedicated backup servers keep the same backups, as well as 3 additional monthly backups.
To restore or download one of these monthly backups, please `contact us <https://www.odoo.com/help>`_.
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
as either the container will be changed by the installation of new pip packages, either the database itself will be
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
If you merge a commit updating the version of one or several modules (in :file:`__manifest__.py`), or their linked python
dependencies (in :file:`requirements.txt`), then Odoo.sh performs a backup automatically (flagged with type Update in the list),
as either the container will be changed by the installation of new pip packages, either the database itself will be
changed with the module update triggered afterwards. In these two cases, we are doing a backup as it may potentially
break things.
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
If you merge a commit that only changes some code without the above-mentioned modifications, then no backup is done
by Odoo.sh, as neither the container nor the database is modified so the platform considers this safe enough. Of course,
as an extra precaution, you can make a backup manually before making big changes in your production sources in case
something goes wrong (those manual backups are available for about one week). To avoid abuse, we limit manual backups
to 5 per day.
The *import database* feature accepts database archives in the format provided by:
@@ -318,15 +318,15 @@ Staging builds duplicate the production build and the production build only inst
**Test suite**
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 `test tags
<https://www.odoo.com/documentation/12.0/reference/testing.html#test-selection>`_.
When the test suite is enabled, you can restrict them by specifying test tags :ref:`test tags
<developer/reference/testing/selection>`.
**Odoo Version**
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.
In addition, for each version you have two options regarding the code update.
In addition, for each version you have two options regarding the code update.
* 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.
content/administration/odoo_sh/getting_started/create.rst
+2 -3
View File
@@ -108,8 +108,7 @@ Access the URL :file:`/web/database/manager` of your on-premise database and dow
.. Warning::
If you cannot access the database manager, it may have been disabled by your system administrator.
See the `database manager security documentation
<https://www.odoo.com/documentation/13.0/setup/deploy.html#database-manager-security>`_.
See the :ref:`database manager security documentation <db_manager_security>`.
You will need the master password of your database server. If you do not have it, contact your system administrator.
@@ -152,7 +151,7 @@ Check your outgoing email servers
There is a default mail server provided with Odoo.sh.
To use it, there must be no enabled outgoing mail server configured in your database in
:menuselection:`Settings --> Technical --> Outgoing Mail Servers`
(:doc:`Developer mode <../../../../applications/general/developer_mode/activate>` must be activated).
(:doc:`Developer mode </applications/general/developer_mode/activate>` must be activated).
After the import of your database,
all outgoing email servers are disabled so you use the Odoo.sh email server provided by default.
content/administration/odoo_sh/getting_started/first_module.rst
+3 -4
View File
@@ -88,8 +88,7 @@ From the Odoo.sh editor, in a terminal:
$ odoo-bin scaffold my_module ~/src/user/
Or, from your computer, if you have an `installation of Odoo
<https://www.odoo.com/documentation/13.0/setup/install.html#source-install>`_:
Or, from your computer, if you have an :ref:`installation of Odoo <setup/install/source>`:
.. code-block:: bash
@@ -150,7 +149,7 @@ Manually
--------
If you want to create your module structure manually,
you can follow `Build an Odoo module <https://www.odoo.com/documentation/13.0/howtos/backend.html>`_ to understand
you can follow :doc:`Build an Odoo module </developer/howtos/backend>` to understand
the structure of a module and the content of each file.
Push the development branch
@@ -264,7 +263,7 @@ and on your production you would not like your module to be installed automatica
Your module may not appear directly in your apps to install either, you need to update your apps list first:
* activate the :doc:`Developer mode <../../../applications/general/developer_mode/activate>`
* activate the :doc:`Developer mode </applications/general/developer_mode/activate>`
* in the apps menu, click the *Update Apps List* button,
* in the dialog that appears, click the *Update* button.