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
63 lines
3.9 KiB
ReStructuredText
63 lines
3.9 KiB
ReStructuredText
|
|
.. _db_management/hosting_changes:
|
|
|
|
===============
|
|
Hosting Changes
|
|
===============
|
|
|
|
You may want to move your Odoo database from one hosting solution to another.
|
|
Depending on the platforms, you have to do it by yourself or contact our support team first.
|
|
|
|
From on-premises to Odoo Online
|
|
===============================
|
|
|
|
.. warning:: Odoo Online is not compatible with **non-standard apps**.
|
|
|
|
1. Create a :ref:`duplicate <duplicate_premise>` of your database: in this duplicate, uninstall all the **non-standard apps**.
|
|
2. Grab a "dump with filestore" of your database by using the Database Manager.
|
|
3. **If you have time constraints, contact us earlier to schedule the transfer.**
|
|
4. `Create a support ticket <https://www.odoo.com/help>`_ and attach the dump (if the file is too large, use any file transfer service and attach the link to your ticket). Also include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com).
|
|
5. We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you.
|
|
6. It's done!
|
|
|
|
From on-premises to Odoo.sh
|
|
===========================
|
|
|
|
1. Follow the :ref:`Import your database section of the Odoo.sh documentation <odoo_sh_import_your_database>`.
|
|
2. ...and voilà!
|
|
|
|
From Odoo Online to on-premises
|
|
===============================
|
|
|
|
1. Log into `your Odoo Online user portal <https://accounts.odoo.com/my/databases/manage>`_ and look for the version number of your database.
|
|
2. If your database does not run a :ref:`major version <supported_versions>` of Odoo, you cannot host it on-premises yet, you have to upgrade it first to a new major version. (*e.g.: If your database runs Odoo 12.3 which is not a major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)
|
|
3. Download a backup of your database by clicking on the "Gear" icon next to your database name then :menuselection:`Download` (if the download fails due to your backup file being too large, contact `our support <https://www.odoo.com/help>`_)
|
|
4. Restore it from the database manager on your local server.
|
|
|
|
From Odoo Online to Odoo.sh
|
|
===========================
|
|
|
|
1. Log into `your Odoo Online user portal <https://accounts.odoo.com/my/databases/manage>`_ and look for the version number of your database.
|
|
2. If your database does not run a :ref:`major version <supported_versions>` of Odoo, you cannot host it on Odoo.sh yet, you have to upgrade it first to a new major version. (*e.g.: If your database runs Odoo 12.3 which is not a major version, you have to upgrade it first to Odoo 13.0 or 14.0.*)
|
|
3. Download a backup of your database by clicking on the "Gear" icon next to your database name then :menuselection:`Download` (if the download fails due to your backup file being too large, contact `our support <https://www.odoo.com/help>`_)
|
|
4. Follow the :ref:`Import your database section of the Odoo.sh documentation <odoo_sh_import_your_database>`.
|
|
|
|
From Odoo.sh to Odoo Online
|
|
===========================
|
|
|
|
.. warning:: Odoo Online is not compatible with **non-standard apps**.
|
|
|
|
1. Uninstall all the **non-standard apps**: test it in a staging build first, then do it in your production build.
|
|
2. **If you have time constraints, contact us earlier to schedule the transfer.**
|
|
3. `Create a support ticket <https://www.odoo.com/help>`_ and attach the dump (if the file is too large, use any file transfer service and attach the link to your ticket). Also include your subscription number and the URL you want to use for your database (e.g.: my-company.odoo.com).
|
|
4. We will make sure your database is compatible and upload it to our cloud. In case of technical issues, we will get in touch with you.
|
|
5. It's done!
|
|
|
|
From Odoo.sh to on-premises
|
|
===========================
|
|
|
|
1. Grab a :ref:`backup of your Odoo.sh production database <odoo_sh_branches_backups>`.
|
|
2. Restore it from the database manager on your local server.
|
|
|
|
|