2021-06-09 16:10:25 +07:00
|
|
|
:nosearch:
|
2021-06-30 16:21:32 +07:00
|
|
|
:show-content:
|
|
|
|
|
:hide-page-toc:
|
|
|
|
|
:show-toc:
|
2021-06-09 16:10:25 +07:00
|
|
|
|
2024-03-04 18:02:08 +07:00
|
|
|
===================
|
|
|
|
|
Database management
|
|
|
|
|
===================
|
2021-06-30 16:21:32 +07:00
|
|
|
|
|
|
|
|
These guides provide instructions on how to install, maintain and upgrade Odoo databases.
|
|
|
|
|
|
|
|
|
|
.. seealso::
|
2024-03-04 18:02:08 +07:00
|
|
|
:doc:`History of Versions <administration/supported_versions>`
|
|
|
|
|
|
|
|
|
|
Installation
|
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
Depending on the intended use case, there are multiple ways to install Odoo - or not install it at
|
|
|
|
|
all.
|
|
|
|
|
|
|
|
|
|
- :doc:`Online <administration/odoo_online>` is the easiest way to use Odoo in production or to try it.
|
|
|
|
|
|
|
|
|
|
- :doc:`Packaged installers <administration/on_premise/packages>` are suitable for testing Odoo and
|
|
|
|
|
developing modules. They can be used for long-term production with additional deployment and
|
|
|
|
|
maintenance work.
|
|
|
|
|
|
|
|
|
|
- :doc:`Source install <administration/on_premise/source>` provides greater flexibility, as it
|
|
|
|
|
allows, for example, running multiple Odoo versions on the same system. It is adequate to develop
|
|
|
|
|
modules and can be used as a base for production deployment.
|
|
|
|
|
|
|
|
|
|
- A `Docker <https://hub.docker.com/_/odoo/>`_ base image is available for development or
|
|
|
|
|
deployment.
|
|
|
|
|
|
|
|
|
|
.. _install/editions:
|
|
|
|
|
|
|
|
|
|
Editions
|
|
|
|
|
========
|
|
|
|
|
|
|
|
|
|
There are two different editions.
|
|
|
|
|
|
|
|
|
|
**Odoo Community** is the free and open-source version of the software, licensed under the `GNU
|
|
|
|
|
LGPLv3 <https://github.com/odoo/odoo/blob/master/LICENSE>`_. It is the core upon which Odoo
|
|
|
|
|
Enterprise is built.
|
|
|
|
|
|
|
|
|
|
**Odoo Enterprise** is the shared source version of the software, giving access to more
|
|
|
|
|
functionalities, including functional support, upgrades, and hosting. `Pricing
|
|
|
|
|
<https://www.odoo.com/pricing-plan>`_ starts from one app free.
|
|
|
|
|
|
|
|
|
|
.. tip::
|
|
|
|
|
:doc:`Switch from Community to Enterprise <administration/on_premise/community_to_enterprise>` at
|
|
|
|
|
any time (except for the source install).
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
|
|
|
|
|
|
|
|
|
|
.. toctree::
|
2021-06-30 16:21:32 +07:00
|
|
|
:titlesonly:
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
|
2024-03-04 18:02:08 +07:00
|
|
|
administration/hosting
|
|
|
|
|
administration/odoo_online
|
[REF][MOV] documentation apocalypse
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
2021-04-30 17:40:29 +07:00
|
|
|
administration/odoo_sh
|
2024-03-04 18:02:08 +07:00
|
|
|
administration/on_premise
|
|
|
|
|
administration/upgrade
|
|
|
|
|
administration/neutralized_database
|
|
|
|
|
administration/supported_versions
|
2024-03-27 23:28:11 +07:00
|
|
|
administration/mobile
|
2024-03-04 18:02:08 +07:00
|
|
|
administration/odoo_accounts
|