91
edits
Installation - Upgrade: Difference between revisions
Jump to navigation
Jump to search
m
Improvements to text and formatting
m (Improved formatting) |
m (Improvements to text and formatting) |
||
| Line 250: | Line 250: | ||
Note | '''Note''' (optional but recommended): | ||
It's better to delete old scripts (and programms if included in the downloaded file) before installing new ones: old files can remain, causing bug and malfunctions. | It's better to delete old scripts (and programms if included in the downloaded file) before installing new ones: old files can remain, causing bug and malfunctions. | ||
| Line 269: | Line 269: | ||
*At the end of the execution, your browser is launched with a page to ask you to run upgrade of your database. Choose the upgrade according to your case. | *At the end of the execution, your browser is launched with a page to ask you to run upgrade of your database. Choose the upgrade according to your case. | ||
If there is more than one version late, the page in your browser will loop to start again the upgrade wizard as often as required to run upgrade process, version by version, until your reach the new installed version. | * If there is more than one version late, the page in your browser will loop to start again the upgrade wizard as often as required to run upgrade process, version by version, until your reach the new installed version. | ||
| Line 277: | Line 277: | ||
*Process to upgrade using Debian/Ubuntu package is the same as the install process (see previous chapters), so it is as easy as installing a package. | *Process to upgrade using Debian/Ubuntu package is the same as the install process (see previous chapters), so it is as easy as installing a package. | ||
You can also read page [[Dolibarr for Ubuntu or Debian]]. | * You can also read page [[Dolibarr for Ubuntu or Debian]]. | ||
<br /> | <br /> | ||
| Line 318: | Line 318: | ||
===For installation that used GIT=== | ===For installation that used GIT=== | ||
* If you already cloned the repo simply upgrade by checking out a version tag like so: | *If you already cloned the repo simply upgrade by checking out a version tag like so:<source lang="bash"> | ||
<source lang="bash"> | |||
$ git checkout 13.0 | $ git checkout 13.0 | ||
$ git pull origin 13.0 | $ git pull origin 13.0 | ||
| Line 326: | Line 325: | ||
*Now open your Dolibarr in your browser. It should open automatically the install/ and choose ''Update'' in suggested menu. | *Now open your Dolibarr in your browser. It should open automatically the install/ and choose ''Update'' in suggested menu. | ||
== Notes on the Upgrade == | |||
* If you have a message that tell the install process is locked by a file, remove the file install.lock stored in Dolibarr root directory. | |||
*'''For security reasons''', once setup is finished, you should create a file install.lock into Dolibarr documents directory. This will lock the call of the install process again (you will have to remove this file for future upgrades). If this is not done, Dolibarr will show you a warning once logged with an administrator user.<source lang="bash"> | |||
$ echo > documents/install.lock | |||
$ chmod 444 documents/install.lock | |||
</source> | |||
If you want to script the database upgrade process (to avoid the upgrade process from web browser), you can run the 3 upgrade processes from command line: | * If you want to script the database upgrade process (to avoid the upgrade process from web browser), you can run the 3 upgrade processes from command line: | ||
<source lang="bash"> | <source lang="bash"> | ||
$ cd htdocs/install | $ cd htdocs/install | ||
| Line 336: | Line 340: | ||
$ php upgrade2.php oldx.oldy.oldz x.y.z > output2.html | $ php upgrade2.php oldx.oldy.oldz x.y.z > output2.html | ||
$ php step5.php oldx.oldy.oldz x.y.z > output3.html | $ php step5.php oldx.oldy.oldz x.y.z > output3.html | ||
</source> | </source> Note: z must be "0" because only major versions have a migration script to run. Return code will be 0 if success, 1 if error (if this happens, see file output.html, output2.html or output3.html). | ||
Note: z must be "0" because only major versions have a migration script to run. | |||
<br /> | |||
< | |||