e3fee2cf46
Prior to this commit, the Odoo documentation was mainly split between
two repositories: odoo/odoo/doc and odoo/documentation-user. Some bits
of documentation were also hosted elsewhere (e.g., wiki, upgrade, ...).
This was causing several problems among which:
- The theme, config, Makefile, and similar technical resources had to
be duplicated. This resulted in inconsistent layout, features, and
build environments from one documentation to another.
- Some pages did not fit either documentation as they were relevant
for both users and developers. Some were relevant to neither of the
two (e.g., DB management).
- Cross-doc references had to be absolute links and they broke often.
- Merging large image files in the developer documentation would bloat
the odoo/odoo repository. Some contributions had to be lightened to
avoid merging too many images (e.g., Odoo development tutorials).
- Long-time contributors to the user documentation were chilly about
going through the merging process of the developer documentation
because of the runbot, mergebot, `odoo-dev` repository, etc.
- Some contributors would look for the developer documentation in the
`odoo/documentation-user` repository.
- Community issues about the user documentation were submitted on the
`odoo/odoo` repository and vice-versa.
Merging all documentations in one repository will allow us to have one
place, one theme, one work process, and one set of tools (build
environment, ...) for all of the Odoo docs.
As this is a good opportunity to revamp the layout of the documentation,
a brand new theme replaces the old one. It features a new way to
navigate the documentation, centered on the idea of always letting the
reader know what is the context (enclosing section, child pages, page
structure ...) of the page they are reading. The previous theme would
quickly confuse readers as they navigated the documentation and followed
cross-application links.
The chance is also taken to get rid of all the technical dangling parts,
performance issues, and left-overs. Except for some page-specific JS
scripts, the Odoo theme Sphinx extension is re-written from scratch
based on the latest Sphinx release to benefit from the improvements and
ease future contributions.
task-2351938
task-2352371
task-2205684
task-2352544
Closes #945
32 lines
1.4 KiB
ReStructuredText
32 lines
1.4 KiB
ReStructuredText
|
|
.. _odoosh-advanced-frequent_technical_questions:
|
|
|
|
==================================
|
|
Frequent Technical Questions
|
|
==================================
|
|
|
|
"Scheduled actions do not run at the exact time they were expected"
|
|
-------------------------------------------------------------------
|
|
|
|
On the Odoo.sh platform, we cannot guarantee an exact running time for scheduled actions.
|
|
|
|
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.
|
|
|
|
.. warning::
|
|
Do not expect any scheduled action to be run more often than every 5 min.
|
|
|
|
Are there "best practices" regarding scheduled actions?
|
|
-------------------------------------------------------
|
|
|
|
**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.
|
|
|
|
We advise that:
|
|
|
|
- Your scheduled actions should work on small batches of records.
|
|
- 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.
|
|
- Your scheduled actions should be
|
|
`idempotent <https://stackoverflow.com/a/1077421/3332416>`_: they must not
|
|
cause side-effects if they are started more often than expected.
|