6366c20ffa
This commit updates the documentation for neutralized databases to
include information about how search engine indexing is prevented for
these databases.
task-3895772
closes odoo/documentation#9708
X-original-commit: c770eb5618
Signed-off-by: Serge Bayet (seba) <seba@odoo.com>
37 lines
1.2 KiB
ReStructuredText
37 lines
1.2 KiB
ReStructuredText
====================
|
|
Neutralized database
|
|
====================
|
|
|
|
A neutralized database is a non-production database on which several parameters are deactivated.
|
|
This enables one to carry out tests without the risk of launching specific automated processes that
|
|
could impact production data (e.g., sending emails to customers). Live access is removed and
|
|
turned into a testing environment.
|
|
|
|
.. note::
|
|
**Any testing database created is a neutralized database:**
|
|
|
|
- testing backup databases
|
|
- duplicate databases
|
|
- for Odoo.sh: staging and development databases
|
|
|
|
.. important::
|
|
A database can also be neutralized when upgrading, as it is vital to do some tests before
|
|
switching to a new version.
|
|
|
|
Deactivated features
|
|
====================
|
|
|
|
Here is a non-exhaustive list of the deactivated features:
|
|
|
|
- all planned actions (e.g., automatic invoicing of subscriptions, mass mailing, etc.)
|
|
- outgoing emails
|
|
- bank synchronization
|
|
- payment providers
|
|
- delivery methods
|
|
- :abbr:`IAP (In-App Purchase)` tokens
|
|
- website visibility (prevent search engines from indexing your site)
|
|
|
|
.. note::
|
|
**A red banner at the top of the screen is displayed on the neutralized database so that it can
|
|
be seen immediately.**
|