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
107 lines
3.2 KiB
ReStructuredText
107 lines
3.2 KiB
ReStructuredText
|
|
.. _setup/enterprise:
|
|
|
|
============================
|
|
From Community to Enterprise
|
|
============================
|
|
|
|
Depending on your current installation, there are multiple ways to upgrade
|
|
your community version.
|
|
In any case the basic guidelines are:
|
|
|
|
* Backup your community database
|
|
|
|
.. image:: enterprise/db_manager.png
|
|
:class: img-fluid
|
|
|
|
* Shutdown your server
|
|
|
|
* Install the web_enterprise module
|
|
|
|
* Restart your server
|
|
|
|
* Enter your Odoo Enterprise Subscription code
|
|
|
|
.. image:: enterprise/enterprise_code.png
|
|
:class: img-fluid
|
|
|
|
On Linux, using an installer
|
|
============================
|
|
|
|
* Backup your community database
|
|
|
|
* Stop the odoo service
|
|
|
|
.. code-block:: console
|
|
|
|
$ sudo service odoo stop
|
|
|
|
* Install the enterprise .deb (it should install over the community package)
|
|
|
|
.. code-block:: console
|
|
|
|
$ sudo dpkg -i <path_to_enterprise_deb>
|
|
|
|
* Update your database to the enterprise packages using
|
|
|
|
.. code-block:: console
|
|
|
|
$ python3 /usr/bin/odoo-bin -d <database_name> -i web_enterprise --stop-after-init
|
|
|
|
* You should be able to connect to your Odoo Enterprise instance using your usual mean of identification.
|
|
You can then link your database with your Odoo Enterprise Subscription by entering the code you received
|
|
by e-mail in the form input
|
|
|
|
|
|
On Linux, using the source code
|
|
===============================
|
|
|
|
There are many ways to launch your server when using sources, and you probably
|
|
have your own favourite. You may need to adapt sections to your usual workflow.
|
|
|
|
* Shutdown your server
|
|
* Backup your community database
|
|
* Update the ``--addons-path`` parameter of your launch command (see :ref:`setup/install/source`)
|
|
* Install the web_enterprise module by using
|
|
|
|
.. code-block:: console
|
|
|
|
$ -d <database_name> -i web_enterprise --stop-after-init
|
|
|
|
Depending on the size of your database, this may take some time.
|
|
|
|
* Restart your server with the updated addons path of point 3.
|
|
You should be able to connect to your instance. You can then link your database with your
|
|
Odoo Enterprise Subscription by entering the code you received by e-mail in the form input
|
|
|
|
On Windows
|
|
==========
|
|
|
|
* Backup your community database
|
|
|
|
* Uninstall Odoo Community (using the Uninstall executable in the installation folder) -
|
|
PostgreSQL will remain installed
|
|
|
|
.. image:: enterprise/windows_uninstall.png
|
|
:class: img-fluid
|
|
|
|
* Launch the Odoo Enterprise Installer and follow the steps normally. When choosing
|
|
the installation path, you can set the folder of the Community installation
|
|
(this folder still contains the PostgreSQL installation).
|
|
Uncheck ``Start Odoo`` at the end of the installation
|
|
|
|
.. image:: enterprise/windows_setup.png
|
|
:class: img-fluid
|
|
|
|
* Using a command window, update your Odoo Database using this command (from the Odoo
|
|
installation path, in the server subfolder)
|
|
|
|
.. code-block:: console
|
|
|
|
$ odoo.exe -d <database_name> -i web_enterprise --stop-after-init
|
|
|
|
* No need to manually launch the server, the service is running.
|
|
You should be able to connect to your Odoo Enterprise instance using your usual
|
|
mean of identification. You can then link your database with your Odoo Enterprise
|
|
Subscription by entering the code you received by e-mail in the form input
|