1 # vim:fileencoding=UTF-8
2 # $ Revision: 1.4 $, $ Date: 2008/10/20 7:55:09 p.m. $
4 Previous buildlogs engine was inefficient, especially for advanced search. This
5 engine uses the sqlite3 database (php-pdo-sqlite) and is quite fast.
7 First you must initialize a database using a script migration.php.
8 This script requires php-program. Please run it again. Execution time
9 depends on the number of files and file system. This may take several minutes.
11 Then put the index.php, and powpld.png buildlogs.inc web server.
12 The script also requires php-gettext.
14 Each new buildlog (for new or old spec) should be
15 added to the database using the script addlog.php (using php-cli and php-pdo-sqlite).
16 Depending on whether the spec is new or not, the database will be updated
17 or added a new record. Addlog.php parameter for the absolute path
19 eg addlog.php /home/services/ftp/pub/pld-buildlogs/ac/i686/OK/kernel.bz2
21 Scripts index.php migration.php addlog.php and use the variable $database.
22 This variable should be identical in all three scripts.
23 Its current value is 'sqlite:/home/services/ftp/buildlogs.db'.
24 It must be set to a value that the database file and directory in which it is situated
25 was writable by scripts and addlog.php migration.php and impossible to read!
28 Configuration script is saved in a file buildlogs.inc.
29 After each change in this file, make sure that passes are correct
30 and rebuild the database by running migration.php.