227
edits
mNo edit summary Tag: 2017 source edit |
(translate use your sata to test last version) Tag: 2017 source edit |
||
| Line 9: | Line 9: | ||
{{ToTranslate}} | {{ToTranslate}} | ||
The testers among you will certainly want to test the latest updates at some point in order to check the status of certain bugs or commit to a new version. | |||
In order to use your data with peace of mind, here is a procedure to follow to avoid losses ... | |||
''' | '''Warning!''' This documentation is based on examples taken from a Dolibarr installation with the following configuration | ||
* Linux Debian Etch | * Linux Debian Etch | ||
* MySQL 4.1 | * MySQL 4.1 | ||
* Apache2 | * Apache2 | ||
If you use another type of machine, please make the usual modifications. | |||
= | = Copy = | ||
As your data is of great value, it would be a shame to lose it. In order to test an update, why not copy your data elsewhere? | |||
== | == Directory == | ||
Since, most likely, your entire Dolibarr installation resides in a single directory, copying will be easy. | |||
<source lang="bash"> | <source lang="bash"> | ||
cp -ra /var/www/dolibarr /var/www/dolibarrtest | cp -ra /var/www/dolibarr /var/www/dolibarrtest | ||
</source> | </source> | ||
This command will copy your Dolibarr directory (supposed to be in /var/www/dolibarr here) in a second dolibarrtest directory on which you will run your tests. | |||
The ''-ra'' means ''recursive'' and ''retains files permission''. This last option will allow you not to worry about file rights issues after copying. | |||
== | == Database == | ||
* | * Backup your database: | ||
<source lang="bash"> | <source lang="bash"> | ||
mysqldump -u utilisateur -p --result-file=dolibarr.date.sql base_de_donnees | mysqldump -u utilisateur -p --result-file=dolibarr.date.sql base_de_donnees | ||