[IMP] odoo_sh doc update
closes odoo/documentation#1607
X-original-commit: 6c48f90739
Signed-off-by: Antoine Vandevenne (anv) <anv@odoo.com>
This commit is contained in:
@@ -74,8 +74,8 @@ The neutralization includes:
|
||||
* Setting payment acquirers and shipping providers in test mode.
|
||||
* Disabling IAP services
|
||||
|
||||
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.
|
||||
The latest database will be kept alive for one year after which you will be expected to rebuild the branch.
|
||||
Older ones from the same branch may get garbage collected to make room for new ones.
|
||||
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.
|
||||
|
||||
@@ -384,7 +384,7 @@ we are considering the feature if there is enough demand.
|
||||
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
|
||||
The configuration steps are explained in the documentation about :ref:`SPF
|
||||
<email_communication/spf_compliant>` and :ref:`DKIM <email_communication/dkim_compliant>`.
|
||||
|
||||
|
||||
|
||||
@@ -79,7 +79,9 @@ Import your database
|
||||
====================
|
||||
|
||||
You can import your database in your Odoo.sh project as long as it is in a :doc:`supported version
|
||||
</administration/maintain/supported_versions>` of Odoo.
|
||||
</administration/maintain/supported_versions>` of Odoo. The branch automatically switches to the
|
||||
Odoo version of the database.
|
||||
|
||||
|
||||
Push your modules in production
|
||||
-------------------------------
|
||||
|
||||
@@ -151,14 +151,13 @@ This section shows the storage size used by your project.
|
||||
.. image:: ./media/interface-settings-storage.png
|
||||
:align: center
|
||||
|
||||
Storage size is computed as follows:
|
||||
Storage size of a build is computed as follows:
|
||||
|
||||
* the size of the PostgreSQL database
|
||||
|
||||
* the size of the disk files available in your container: database filestore, sessions storage directory...
|
||||
|
||||
.. Warning::
|
||||
In case you want to analyze disk usage, you can run the tool `ncdu <https://dev.yorhel.nl/ncdu/man>`_ in your Web Shell.
|
||||
The total storage accounts for the production database, the staging branches, and three backups.
|
||||
|
||||
Should your production database size grow to exceed what's provisioned in your subscription, it
|
||||
will automatically be synchronized with it.
|
||||
|
||||
Reference in New Issue
Block a user