As you mentioned, you get the last update from the github repository for Odoo 13, So you need to update the Databases to apply all the new changes and you can do using command:
sudo service YourServiceName restart -u all -d YourDatabaseName
Here you are the process to update Odoo from github:
If you
installed Odoo from source by using the git repository. The main
benefit of this setting is being able to update the source code of Odoo using
git to get the latest bug fixes.
To update
your Odoo from source follow the below steps:
1.
Make a backup of all the
databases you care about in case something goes bad. (You can backup all DB
from odoo)
2.
Stop any instance currently
running with the Odoo source you are about to update. use the below
command:
$ Sudo service
[service-name] stop
3.
Then make a note of the
current version of the source you are running. (This is very important if
something going wrong with update so you can back to the version which you are
running) The best way is to create a lightweight tag using the following
command:
#cd to the odoo folder
$ git
checkout 13.0
$ git
tag 13.0-before-update-$(date --iso)
4.
To update the source code of
Odoo, use the following command:
$ git pull –-ff-only
This will fetch the latest version of the source
code committed to the current branch.
5. If the last step run successfully then, To update an instance running on
this code, run the below:
$ sudo service YourServiceName --stop-after-init -u base -d YourDBName
Updating the source code is done by
making sure we are on the correct branch using git checkout, and then
fetching the new revisions using git pull. The --ff-only option will cause
a failure if you have local commits not present in the remote repository. If
this happens and you want to keep your changes, you can use git pull (without --ff-only)
to merge the remote changes with yours; otherwise, use git reset --hard
origin/13.0 to force the update, discarding your local modifications.
The update command uses the following
options:
·
-c: specify the
configuration file
·
--stop-after-init: stop the
instance when the update is over
·
-u base or --update
base: requests the update of the base module.
When updating a module, Odoo does the
following:
·
It updates the database
structure for the models defined in the module for which the structure changes.
For updates on the stable branch of Odoo, there should be no such changes, but
this can happen for your own addons or third party addons.
·
It updates the database
records stored in data files of the module, most notably the views. It then
recursively updates the installed modules which have declared a dependency on
the module.
Since the base module is an implicit
dependency of all Odoo modules, updating it will trigger an update of all the
installed modules in your instance. To update all installed modules, the alias
all can be used instead of base.
If the update fails, don't panic, you
have backups:
1.
Read the error message
carefully. Save it to a file, as it will be useful to make a bug report later.
2.
If you cannot figure out what
the problem is, restore the service; restore the Odoo source code to the
previous version, which is known to work using the tag you set before updating
the source version:
$ git reset --hard 13.0-before-update-$(date
--iso)
3.
Drop the broken databases and
restore them from the backups you made.
