Backing Up and Restoring Changelogic
- Changelogic
- Backup And Restore
There are several components to be considered for backing up:
- Version Control System (CVS or Subversion) contents
- database contents
- web interface configuration file
- web interface standard files
- diff service file (optional)
It is important to ensure that the first two are backed up at roughly the same time as the database should always be kept in sync with the VCS contents, including after restoring from back-up. Similarly, when restoring a failed instance, both VCS and database should be restored from backup even if one of them did not fail.
VCS contents
VCS contains code of applications developed using Changelogic. Standard routine should be followed for backing up VCS:
Please note that VCS should be backed up along with database to ensure ability to restore synchronous state.
Database contents
Changelogic uses a My SQL? database for storing data managed via its web interface and additional metadata about code in VCS. Standard routine for backing up MySQL databases should be followed.
Please note that database should be backed up along with VCS to ensure ability to restore synchronous state.
Web interface configuration file
The web interface configuration file is resources/conf.php under Changelogic installation directory. This file is custom for every Changelogic instance and cannot be restored from Changelogic installation package. Therefore this file should be backed up even if installation package is relied upon for other files.
Web interface standard files
Web interface files are all under Changelogic installation directory. The whole tree (except configuration file, see above) can be restored from Changelogic installation package. Backing up / restoring the whole tree is okay, too.
Diff service file (optional)
If CVS is used as repository, a separate PHP file called get_viewcvs_diff.php may be customized and installed on the server hosting corresponding ViewVC. This file should also be backed up.