31,026
edits
Installation - Upgrade: Difference between revisions
Jump to navigation
Jump to search
m
→With Dolibarr (standard .tgz package)
| Line 54: | Line 54: | ||
* Go into the directory where to install Dolibarr (the web root directory defined for your web server) | * Go into the directory where to install Dolibarr (the web root directory defined for your web server) | ||
<source lang="bash"> | |||
$ cd /var/www | |||
</source> | |||
# For Debian and Ubuntu families, it is generally: /var/www | # For Debian and Ubuntu families, it is generally: /var/www | ||
# For Mandriva: /var/www/html | # For Mandriva: /var/www/html | ||
| Line 61: | Line 63: | ||
* Get the application archive of last stable version | * Get the application archive of last stable version | ||
<source lang="bash"> | |||
$ wget http://www.dolibarr.org/files/dolibarr.tgz | |||
</source> | |||
* Uncompress archive | * Uncompress archive | ||
<source lang="bash"> | |||
$ tar xvfz dolibarr.tgz | |||
</source> | |||
* Rename directory dolibarr-x.y.z into dolibarr to have a directory name that does not depends on version (replace x.y.z with source version) | * Rename directory dolibarr-x.y.z into dolibarr to have a directory name that does not depends on version (replace x.y.z with source version) | ||
<source lang="bash"> | |||
$ mv dolibarr-x.y.z dolibarr | |||
</source> | |||
* As a root user, create, into directory dolibarr/htdocs/conf, an empty configuration file called conf.php and set, as owner, the web server user (example www-data on Debian, nobody on old RedHat, apache on Mandriva, recent RedHat or other distributions ...). This is required because the web server will have to write into this file during install process. | * As a root user, create, into directory dolibarr/htdocs/conf, an empty configuration file called conf.php and set, as owner, the web server user (example www-data on Debian, nobody on old RedHat, apache on Mandriva, recent RedHat or other distributions ...). This is required because the web server will have to write into this file during install process. | ||
<source lang="bash"> | |||
$ cd dolibarr ; touch htdocs/conf/conf.php ; chown www-data htdocs/conf/conf.php | |||
</source> | |||
* Always as a root user, create a directory that will serve to save all generated and stocked by Dolibarr (PDf invoices, uploaded images, ...), and attribute to this directory a owner that must be the web server (example www-data on Debian, nobody on old RedHat, apache on Mandriva or recent RedHat, ...). The web server must have write permission into this directory. | * Always as a root user, create a directory that will serve to save all generated and stocked by Dolibarr (PDf invoices, uploaded images, ...), and attribute to this directory a owner that must be the web server (example www-data on Debian, nobody on old RedHat, apache on Mandriva or recent RedHat, ...). The web server must have write permission into this directory. | ||
<source lang="bash"> | |||
$ mkdir documents ; chown www-data documents | |||
</source> | |||
* Now call your browser to point to the main page | * Now call your browser to point to the main page | ||
| Line 82: | Line 92: | ||
* For security reason, we recommend, once setup is finished, to create a file install.lock into Dolibarr installed directory that only root user can delete. This will lock the call of the install process again (you will have to remove it for upgrades). | * For security reason, we recommend, once setup is finished, to create a file install.lock into Dolibarr installed directory that only root user can delete. This will lock the call of the install process again (you will have to remove it for upgrades). | ||
If this is not done, Dolibarr will show you a warning one logged by an administrator user. | If this is not done, Dolibarr will show you a warning one logged by an administrator user. | ||
<source lang="bash"> | |||
$ touch /var/www/dolibarr/install.lock; chmod go-w /var/www/dolibarr; | |||
</source> | |||
= Upgrade Dolibarr = | = Upgrade Dolibarr = | ||