Changes

Jump to navigation Jump to search
m
Line 7: Line 7:  
If you have already a working installation, backup your file '''htdocs/conf/conf.php''' and your documents directory. It's more secure if you make a mistake later.
 
If you have already a working installation, backup your file '''htdocs/conf/conf.php''' and your documents directory. It's more secure if you make a mistake later.
   −
'''Get last version of sources using a CVS anonymous access'''
+
===Get last version of sources using a CVS anonymous access===
    
With no Savannah CVS write access, you can still get files with a CVS client ([http://www.wincvs.org WinCVS] or [http://www.tortoisecvs.org TortoiseCVS] for example with Windows, or the CVS client in Eclipse).
 
With no Savannah CVS write access, you can still get files with a CVS client ([http://www.wincvs.org WinCVS] or [http://www.tortoisecvs.org TortoiseCVS] for example with Windows, or the CVS client in Eclipse).
Line 20: Line 20:  
HEAD means we want last version of files (so last development files).
 
HEAD means we want last version of files (so last development files).
   −
'''Get last version of sources using a full CVS access'''
+
===Get last version of sources using a full CVS access===
    
Another way to get last CVS version is to use CVS tools. You need a Savannah write CVS access to CVS repository and a CVS client (CVS command line tool with Linux, WinCVS or TortoiseCVS for example with Windows, or the CVS client in Eclipse).
 
Another way to get last CVS version is to use CVS tools. You need a Savannah write CVS access to CVS repository and a CVS client (CVS command line tool with Linux, WinCVS or TortoiseCVS for example with Windows, or the CVS client in Eclipse).
Line 32: Line 32:  
HEAD means we want last version of files (so last development files).
 
HEAD means we want last version of files (so last development files).
   −
'''Update your repository'''
+
===Update your repository===
    
The command to update files that was caught with previous CVS command:
 
The command to update files that was caught with previous CVS command:
Line 57: Line 57:  
May be, you will have to change permissions on directories or files after to make then readable by users of your Dolibarr web server.
 
May be, you will have to change permissions on directories or files after to make then readable by users of your Dolibarr web server.
   −
'''Get files for a particular CVS branch'''
+
===Get files for a particular CVS branch===
    
If you want to work on a particular version (with its patches), you must follow same process but you must replace HEAD by name of the branch.
 
If you want to work on a particular version (with its patches), you must follow same process but you must replace HEAD by name of the branch.
 
For example DOLIBARR_2_2_BRANCH for branch 2.2 or DOLIBARR_2_4_BRANCH for branch 2.4.
 
For example DOLIBARR_2_2_BRANCH for branch 2.2 or DOLIBARR_2_4_BRANCH for branch 2.4.
   −
'''Get last version of sources by download'''
+
===Other repositories===
 +
 
 +
A CVS repository for rare modules is also available into module dolibarrmod
 +
<source lang="bash">
 +
:ext:yoursavannahlogin@cvs.savannah.nongnu.org:/cvsroot/dolibarr
 +
export CVSROOT
 +
cvs -q checkout -r HEAD dolibarrmod
 +
</source>
 +
 
 +
===Get last version of sources by download===
    
This method allows you to get CVS version of main development branch (called HEAD). This operation consist to get last version of Dolibarr files that are packaged each night into a zip file.
 
This method allows you to get CVS version of main development branch (called HEAD). This operation consist to get last version of Dolibarr files that are packaged each night into a zip file.
Line 69: Line 78:  
New files will overwrite old ones.
 
New files will overwrite old ones.
   −
'''Make configuration'''
+
===Make configuration===
    
Restore configuration file (./htdocs/conf/conf.php) with backup made previously if file has been erased/removed (should not) or make your web server to point to Dolibarr ./htdocs directory and run the install process.
 
Restore configuration file (./htdocs/conf/conf.php) with backup made previously if file has been erased/removed (should not) or make your web server to point to Dolibarr ./htdocs directory and run the install process.
   −
'''Update database'''
+
===Update database===
    
If you make an update of sources, the next step is to upgrade your database. For this, all you have to do is call page
 
If you make an update of sources, the next step is to upgrade your database. For this, all you have to do is call page
Line 80: Line 89:     
This process was built to work whatever is start step and can be run and rerun several times with no risks.
 
This process was built to work whatever is start step and can be run and rerun several times with no risks.
  −
'''Other repositories'''
  −
  −
A CVS repository for non officials modules is also available on Sourceforge:
  −
:ext:youlogin@dolibarr.cvs.sourceforge.net:/cvsroot/dolibarr
  −
export CVSROOT
  −
cvs -q checkout -r HEAD dolibarrmod
      
= Start a development =
 
= Start a development =

Navigation menu