Location: PHPKode > projects > Druid Defect Control > defectcontrol_0.9.4/doc/reference.html
<html>
<head>
<title>Defect Control System</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link rel="stylesheet" href="style.css">
</head>
<?include 'header.php' ?>
<body bgcolor="#FFFFFF">
<p>&nbsp;</p>
<h1 align="center">Reference manual</h1>
<p align="center">&nbsp;</p>
<p align="left">This document is written to explain the technical aspects of the 
  system not covered by the user and administration tutorials. </p>
<p align="left">Administration details</p>
<h2 align="left">Backup / restore procedure </h2>
<p><font size="2">For more details on the backup procedure, see the postgreSQL 
  administration guide. A database called "tts" will contain all the data used 
  by the tracking system. Normally you want to issue a command like: </font> 
<p><font size="2"><font face="Courier New, Courier, mono">pg_dump -b -u -fdatabase.backup 
  -Fc ttstest</font></font> 
<p><font size="2">It will prompt for username and password. Specify the owner 
  of the database. A backup feature will be provided soon in the administer menu, 
  for getting the backup file through the web interface. However, this option 
  is only meant for non regular first backups. Once the system is in production, 
  it should be backed up regularly through the postgres commands described above. 
  </font>
<p><font size="2">Another insteresting command for dumping the database in form 
  of SQL statements is the following: </font>
<p><font face="Courier New, Courier, mono">pg_dump -D ttstest -u &gt;database.sql.backup</font></p>
<p>It will also prompt for username and password, and then dump database schema 
  and data to the specified file. Very useful for testing and migrating to other 
  databases. </p>
<p>&nbsp; 
<h2>Other features</h2>
<p>User default project 
<p>User directory
<h2>Advanced topics</h2>
<p>Running several instances of the system (and specifying a database server)
<p><font size="2">SCM integration</font> 
<p align="center"><img src="images/SCMintegration1.gif"></p>
<p align="center">&nbsp;</p>
<p align="center">&nbsp;</p>
<p align="center"><img src="images/SCMintegration2.gif"></p>
<h2>Security issues</h2>
<p>Passwords travel in clear text over the network at login time. If this is a 
  concern for you, use SSL in the web server. </p>
<p>A bigger concern about security comes from the fact that the database password 
  is stored plain in the config.php file. There is no easy workaround this problem, 
  as the web server has to be able to see it. Reduce the access to this file (and 
  can be a good idea to do the same for the whole application) to the apache user, 
  even if this is not a real protection. </p>
<p>That file contains the password to alter or delete records in the defect database, 
  so be sure to provide the appropiate environment.</p>
<p>&nbsp;</p>
</body>
</html>
Return current item: Druid Defect Control