Installation - Upgrade: Difference between revisions

Jump to navigation Jump to search
m
Tag: 2017 source edit
Line 63: Line 63:


*Check that main root or admin user/password couple for the server is known and works correctly. If this root or admin user/password is not known because not yet defined, read following chapter. Otherwise go on next step:
*Check that main root or admin user/password couple for the server is known and works correctly. If this root or admin user/password is not known because not yet defined, read following chapter. Otherwise go on next step:
'''MySQL database :'''


For Linux users, if you have just installed a MySQL server, the admin user is''' root'''. If the root password has never been set yet, you must run the following command to initialize the password:
For Linux users, if you have just installed a MySQL server, the admin user is''' root'''. If the root password has never been set yet, you must run the following command to initialize the password:
Line 79: Line 81:
</source>
</source>
And type your password ''newrootpass'' then \q to quit if the connection has been successful.
And type your password ''newrootpass'' then \q to quit if the connection has been successful.
'''PostgreSQL database :'''


For Linux users, if you have just installed a PostgreSQL server, you must run the following command to initialize an admin user and password. For this, add the following line in file '''/etc/postgresql/x.x/main/pg_hba.conf''' (replace x.x with your postgres version)
For Linux users, if you have just installed a PostgreSQL server, you must run the following command to initialize an admin user and password. For this, add the following line in file '''/etc/postgresql/x.x/main/pg_hba.conf''' (replace x.x with your postgres version)
Line 109: Line 113:
And type your ''dolibarrownerpass'' as password and \q to quit if connection is ok.
And type your ''dolibarrownerpass'' as password and \q to quit if connection is ok.


'''web root :'''


*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)
Line 147: Line 153:
</source>
</source>


*Change permission and owner of the 'dolibarr' directory to that of the group under which the web server runs (assumed to be 'www-data' for debian, 'apache' for redhat, mandriva, fedora)
*Change permissions and owner of the 'dolibarr' directory to that of the group under which the web server runs (assumed to be 'www-data' for debian, 'apache' for redhat, mandriva, fedora)


<source lang="bash">
<source lang="bash">
Line 164: Line 170:
</source>
</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, apache on Mandriva, RedHat, Fedora 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 the web server user as owner (for instance www-data on Debian, apache on Mandriva, RedHat, Fedora or other distributions ...). This is required because the web server will have to write into this file during install process.


<source lang="bash">
<source lang="bash">
Line 236: Line 242:
  cd ./dolibarr
  cd ./dolibarr
  git checkout tags/<desiredrelease>
  git checkout tags/<desiredrelease>
cd build/docker
docker-compose up


Read the README carefully. As of version 12+ it recommends to use the built in docker files for development only, while an outside repo: https://hub.docker.com/r/tuxgasy/dolibarr  is recommended for production environments.
Read the README carefully. As of version 12+ it recommends to use the built in docker files for development only, while an outside repo: https://hub.docker.com/r/tuxgasy/dolibarr  is recommended for production environments.
Line 287: Line 300:
</source>
</source>


=== For installation that used the zip file ===
===For installation that used the zip file===
 
*Get archive of last version
*Get archive of last version


Line 316: Line 330:
and choose ''Update'' in suggested menu.
and choose ''Update'' in suggested menu.


=== 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">
4

edits

Navigation menu