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

[MERGE] Forward-port of branch 12.0 to 13.0

Browse Source
This commit is contained in:
Antoine Vandevenne (anv) 2020-10-12 14:14:51 +02:00
commit 29bfb56d33
4 changed files with 29 additions and 23 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
accounting/others/adviser/budget.rst
View File

@ -153,6 +153,6 @@ purchase lines booked in the accounts and will display them in the
The theoretical amount represents the amount of money you theoretically could
have spend / should have received in function of the date. When your budget
is 1200 for 12 months (january to december), and today is 31 of january, the
theoretical amount will be 1000, since this is the actual amount that could
theoretical amount will be 100, since this is the actual amount that could
have been realised.

8
odoo_sh/advanced/containers.rst
View File

@ -12,9 +12,11 @@ Each build is isolated within its own container (Linux namespaced container).
The base is an Ubuntu 16.04 system, where all of Odoo's required dependencies,
as well as common useful packages, are installed.
The Odoo.sh team is open to install any system packages
as long as they are distributed in the official Ubuntu repositories.
`Leave us a feedback <https://www.odoo.sh/feedback>`_ if you would like a package not yet installed.
The Odoo.sh team is open to install system packages as long as they are
distributed in the official Ubuntu repositories and meets the platform's
`dependency requirements <https://www.odoo.sh/faq#install_dependencies>`_.
You can use `the feedback form <https://www.odoo.sh/feedback>`_ in order to
submit a package request to the Odoo.sh team.
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.

24
odoo_sh/getting_started/branches.rst
View File

@ -95,7 +95,8 @@ 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 in the :ref:`branch's settings <odoosh-gettingstarted-branches-tabs-mails>`.
disable the tests or allow specific tests to be run with custom tags in the :ref:`branch's settings
<odoosh-gettingstarted-branches-tabs-settings>`.
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.
@ -276,9 +277,30 @@ to manually set it up again on every commit. If you choose new build for a stagi
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'.
**Modules installation**
Choose the modules to install automatically for your development builds.
.. image:: ./media/interface-settings-modulesinstallation.png
:align: center
* *Install only my modules* will install the modules of the branch only. This is the default option.
The :ref:`submodules <odoosh-advanced-submodules>` are excluded.
* *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.
* *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.
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.
**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>`_.
**Odoo Version**

18
odoo_sh/getting_started/settings.rst
View File

@ -97,24 +97,6 @@ Production and staging builds are excluded, visitors can only see their status.
.. _odoosh-gettingstarted-settings-modules-installation:
Modules installation
====================
Choose the modules to install automatically for your development builds.
.. image:: ./media/interface-settings-modulesinstallation.png
:align: center
* *Install only my modules* will install the modules of the branch only.
The :ref:`submodules <odoosh-advanced-submodules>` are excluded.
* *Full installation (all modules)* will install the modules of the branch, the modules included in the submodules
and all standard modules of Odoo.
* *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.
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.
Custom domains
==============