NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[FIX] odoo_sh: typos and improvements

Browse Source
This commit is contained in:
Denis Ledoux 2018-03-27 12:16:14 +02:00
parent 77ec0bbcd6
commit 66accc86e9
3 changed files with 56 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
odoo_sh/getting_started/builds.rst
View File

@ -66,10 +66,12 @@ and try to load this duplicate with the revisions of the staging branches.
Each time you push a new revision on a staging branch, the build created uses a new copy of the production database.
The databases are not re-used between builds of the same branch. This ensures:
* staging builds use databases that are closed to what the production looks like,
so you do not make your tests with outdated data,
* staging builds use databases that are close to what the production looks like,
so you do not make your tests with outdated data,
* you can play around as much as you want in the same staging database,
and you can then ask for a rebuild when you want to restart with a new copy of the production.
and you can then ask for a rebuild when you want to restart with a new copy of the production.
Nevertheless, this means that if you make configuration changes in staging databases
and do not apply them in the production,
@ -97,7 +99,7 @@ and then the other branches are ordered by last build created. You can filter ou
.. image:: ./media/interface-builds-branches.png
:align: center
For each branch, you can access the last build database using the *Connect* link and jump to the branch code using
For each branch, you can access the last build's database using the *Connect* link and jump to the branch code using
the *Github* link. For other branches than the production, you can create a new build which will use the latest revision
of the branch using the link *rebuild*. This last link is not available when there is already a build in progress for
the branch.
@ -106,7 +108,7 @@ the branch.
:align: center
For each build, you can access the revision changes using the button with the Github icon.
You can access the build database as the administrator using the *Connect* button.
You can access the build's database as the administrator using the *Connect* button.
Also, you can access the database with another user using the *Connect as* button,
in the dropdown menu of the *Connect* button.
@ -115,4 +117,4 @@ in the dropdown menu of the *Connect* button.
In the dropdown menu of the build, you can access the same features than in :ref:`the branches view <odoosh-gettingstarted-branches-tabs>`:
*Logs*, *Web Shell*, *Outgoing e-mails*.
You also have the possibility to *Download a dump* of the build database.
You also have the possibility to *Download a dump* of the build's database.

49
odoo_sh/getting_started/create.rst
View File

@ -9,7 +9,7 @@ Create your project
Deploy your platform
====================
Go to `Odoo.sh <https://www.odoo.sh/>`_ and hit the button *Deploy your platform*.
Go to `Odoo.sh <https://www.odoo.sh/>`_ and hit the *Deploy your platform* button.
.. image:: ./media/deploy.png
:align: center
@ -17,7 +17,7 @@ Go to `Odoo.sh <https://www.odoo.sh/>`_ and hit the button *Deploy your platform
Sign in with Github
===================
Sign in with your Github account. If you do not have an account yet, hit the link *Create an account*.
Sign in with your Github account. If you do not have an account yet, hit the *Create an account* link.
.. image:: ./media/github-signin.png
:align: center
@ -25,7 +25,7 @@ Sign in with your Github account. If you do not have an account yet, hit the lin
Authorize Odoo.sh
=================
Grant Odoo.sh the required accesses to your account by clicking the button *Authorize*.
Grant Odoo.sh the required accesses to your account by clicking the *Authorize* button.
.. image:: ./media/github-authorize.png
:align: center
@ -52,14 +52,17 @@ Enter your *subscription code*. This is also called *subscription referral* or *
For partners, Odoo.sh is free. If the free offer changes in the future, we guarantee that any project created under this offer will remain free for the same set of features.
For customers, your Enterprise subscription needs to include Odoo.sh.
Contact your sales representative or account manager in order to get it.
After submitting the form, if you are notified your subscription is not valid, it either means:
When submitting the form, if you are notified your subscription is not valid, it either means:
* it is not an existing subscription,
* it is not a partnership subscription,
* it is an enterprise subscription, but which does not include Odoo.sh,
* it is neither a partnership subscription or an enterprise subscription (e.g. an online subscription).
In case of doubt with your subscription, please contact the `Odoo support <https://www.odoo.com/help>`_.
.. image:: ./media/deploy-form.png
:align: center
@ -87,7 +90,7 @@ You can structure your modules as you wish, Odoo.sh will automatically detect th
For instance, you can put all your modules folder in the root directory of your repository,
or group the modules in folders by categories that you define (accounting, project, ...).
For community modules availabe in public Git repositories,
For community modules available in public Git repositories,
you can also consider to add them using :ref:`Submodules <odoosh-advanced-submodules>`.
Then, either :ref:`make this branch the production branch <odoosh-gettingstarted-branches-stages>`,
@ -101,6 +104,12 @@ On-premise databases
Access the URL :file:`/web/database/manager` of your on-premise database and download a backup.
.. Warning::
If you cannot access the database manager, it may have been disabled by your system administrator.
See the `database manager security documentation
<https://www.odoo.com/documentation/11.0/setup/deploy.html#database-manager-security>`_.
You will need the master password of your database server. If you do not have it, contact your system administrator.
.. image:: ./media/create-import-onpremise-backup.png
@ -140,9 +149,37 @@ Check your outgoing email servers
---------------------------------
There is a default mail server provided with Odoo.sh.
If you want to use it, just delete or disable all your outgoing mail servers configured in your database in
To use it, there must be no enabled outgoing mail server configured in your database in
:menuselection:`Settings --> Technical --> Outgoing Mail Servers` (Developer mode must be activated).
After the import of your database,
all outgoing email servers are disabled so you use the Odoo.sh email server provided by default.
.. Warning::
Ports 25, 465 and 587 are blocked. If you want to use your own email servers, they must be configured on other ports.
Check your scheduled actions
----------------------------
All scheduled actions are disabled after the import.
This is to prevent your newly imported database to perform actions that could impact your running production,
such as sending the mails remaining in the queue, processing mass mailings, or third-party services synchronization
(Calendars, files hosting, ...).
If you plan to make the imported database your production, enable the scheduled actions you need.
You can check what is enabled in the origin database and enable the same actions in the imported database.
Scheduled actions are located under :menuselection:`Settings --> Technical --> Automation --> Scheduled Actions`.
Register your subscription
--------------------------
Your subscription is unlinked after the import.
The imported database is considered a duplicate by default and the enterprise subscription is therefore removed,
as you can only have one database linked by subscription.
If you plan to make it your production,
unlink your former database from the subscription, and register the newly imported database.
Read the :ref:`database registration documentation <db_premise>` for instructions.

10
odoo_sh/getting_started/settings.rst
View File

@ -20,9 +20,9 @@ The name of your project.
.. image:: ./media/interface-settings-projectname.png
:align: center
This is the domain that will be used to access your production database.
This defines the address that will be used to access your production database.
The domain to access your staging and development builds will contain this name as well.
Addresses of your staging and development builds are derived from this name and assigned automatically.
However, when you change your project name, only future builds will use the new name.
Collaborators
@ -96,7 +96,7 @@ Choose the modules to install automatically for your development builds.
:align: center
* *Install only my modules* will install the modules of the branch only.
The ` submodules <https://git-scm.com/book/en/v2/Git-Tools-Submodules>`_ are excluded.
The :ref:`submodules <odoosh-advanced-submodules>` are excluded.
* *Full installation (all modules)* will install the modules of the branch, the modules included in the submodules
and all standard modules of Odoo.
* *Install a list of modules* will install the modules specified in the input just below this option.
@ -132,7 +132,7 @@ Bare domains (e.g. *mycompany.com*) are not accepted:
* they can only be configured using A records,
* A records only accept IP addresses as value,
* the IP address of your database can change, following an upgrade, an hardware failure or
* the IP address of your database can change, following an upgrade, a hardware failure or
your wish to host your database in another country or continent.
Therefore, bare domains could suddenly no longer work because of this change of IP address.
@ -142,7 +142,7 @@ having the first redirecting to the second is amongst the
`SEO best practices <https://support.google.com/webmasters/answer/7451184?hl=en>`_
(See *Provide one version of a URL to reach a document*)
in order to have one dominant URL. You can therefore just configure *mycompany.com* to redirect to *www.mycompany.com*.
Most domains managers have the feature to configure this redirection. This is commonly called a web redirection.
Most domain managers have the feature to configure this redirection. This is commonly called a web redirection.
HTTPS/SSL
---------