DL installation

• Copy the htdocs directory contained in the archive to a directory of choice under your web server.

• Configure the parameters inside include/config.php as needed. This usually means changing the URL and E-Mail of the service.

• Ensure the include and style/include directories are not directly accessible externally. Type http://dl.example.com/include/config.php and verify that you correctly get an "Access Denied" error.

  If you use Apache, the provided .htaccess files should be already sufficient; consult your web server documentation otherwise.

• Create a spool directory that will be used by the service to store the files, user and ticket information. This directory should be outside of the document root of your web server. Fix the permissions so that PHP has read/write access to it.

  In the provided include/config.php this is configured as /var/spool/dl. If you web server runs as "nobody:nogroup", issue:

  mkdir -p -m770 /var/spool/dl
  chgrp nogroup /var/spool/dl
  

  to create correctly this directory.

Database setup

DL needs a database to store the ticket and user information. By default, DL will use an embedded "sqlite" database stored within the spool directory, but some manual setup is still required.

To create the database, you need the sqlite or sqlite3 command, and execute the provided SQL batch for sqlite with the same user as your web server (by using su or sudo if necessary):

cd /var/spool/dl/
sqlite data.sdb < /your-installation-directory/include/scripts/sqlite.sql
chmod 660 data.sdb

If you want to change the database path, or use a real database server, you need to properly configure the $dsn parameter in include/config.php according to your setup.

PHP setup

The following parameters are required to be set in your php.ini (these values are defaults since PHP 5.0, but they might be different in your setup):

• magic_quotes_gpc: must be "Off".
• magic_quotes_runtime: must be "Off".
• date.timezone: must be set to your system preference.

The maximal upload limit is determined by several PHP configuration parameters. Check your php.ini for:

• file_uploads: must be "On".
• upload_tmp_dir: ensure enough space is available.
• upload_max_filesize: change as needed.
• post_max_size: must be at least 1M larger than upload_max_filesize.
• apc.rfc1867: must be "On" for the upload progress-bar to work.

The upload limit as shown in the submission form is determined automatically from the upload_max_filesize parameter.

Any upload beyond post_max_size will be completely ignored: users will get a blank page instead of an error message. You should raise post_max_size above upload_max_filesize to get an acceptable "error window".

If you are allowed to do so, you can also set these parameters with "ini_set()" directly inside include/config.php (so that it only affects dl). If PHP was built as an Apache module you can also set them through .htaccess (see http://www.php.net/manual/en/configuration.changes.php).

The upload progress-bar is only available when the PHP APC module in installed, and the apc.rfc1867 setting is explicitly enabled. The PHP APC module is only reported to work on mod_php currently.

User setup

DL can use both an internal and an external user database, by trusting the authentication credentials provided by your web server.

dl supports both "normal" users and "administrators". A normal user can only see and manage tickets created by himself. Administrators can see/manage all the tickets.

cd /your-installation-directory/include/scripts
php useradmin.php add "admin" "true" "change me"

Apache/mod_php

With internal authentication:

<Directory /your-installation-directory>
  AllowOverride Limit
  Options -Indexes
</Directory>

With external authentication:

<Directory /your-installation-directory>
  AllowOverride Limit
  Options -Indexes
  <Files admin.php>
    AuthType Basic
    AuthName "Restricted Area"
    ...
    Require valid-user
  </Files>
</Directory>

With LDAP or ActiveDirectory authentication:

<Directory /your-installation-directory>
  AllowOverride Limit
  Options -Indexes
  <Files admin.php>
    AuthType Basic
    AuthName "Restricted Area"
    AuthBasicProvider ldap
    AuthzLDAPAuthoritative off
    AuthLDAPURL ldap://XXXXXX:XXXX/ou=XXXX,dc=XXXX,dc=XXX?sAMAccountName?sub?(objectClass=*)
    AuthLDAPBindDN "cn=XXXX,ou=XXXXX,dc=XXX,dc=XXX"
    AuthLDAPBindPassword "XXXXX"
    ...
    Require valid-user
    Satisfy any
  </Files>
</Directory>

Apache/FastCGI

FastCGI support in Apache up to 2.2.x is severely lacking with all the available modules: mod_fcgi, mod_fcgid (now merged officially into Apache's mod_fcgi) and mod_fastcgi.

• mod_fcgi and mod_fcgid buffer the entire request in memory before handing-off the request to PHP, meaning that the maximal upload limit is bound to your available memory at the time of the request, independently of how PHP is setup. This is a known, old bug that's still present in both mod_fcgi 2.2.14 and mod_fcgid 2.3.4. There is no known work-around: either use mod_php or use a different server.
• mod_fastcgi has been proved to be slow (and sometimes unstable) in most configurations. It is not advisable to use PHP with mod_fastcgi.

For HTTP/External authentication to work, mod_rewrite needs to be enabled, and a different setup is required, as shown:

<Directory /your-installation-directory>
  AllowOverride Limit
  Options -Indexes
  <Files admin.php>
    RewriteEngine on
    RewriteCond %{HTTP:Authorization} ^(.*)
    RewriteRule ^(.*) - [E=HTTP_AUTHORIZATION:%1]
    AuthType Basic
    AuthName "Restricted Area"
    ...
    Require valid-user
  </Files>
</Directory>

Lighttpd

PHP/FastCGI works fine with Lighttpd 1.4.x without any special setup. The following configuration is required to protect the include directories:

$HTTP["url"] =~ "^/dl(?:/|/.*/)include/" {
  url.access-deny = ( "" )
}

You can also enable external authentication with the following:

auth.require   += ( "/dl/admin.php" => (
    "method"   => "basic",
    "realm"    => "Restricted Area",
    "require"  => "valid-user"
) )

Internal method

Expiration is usually performed aggressively at every page request. You can control this behavior (thus reducing the DB pressure) by tuning the ''$gcProbability'' and ''$gcLimit'' parameters.

If you notice too much load on your DB, start by lowering ''$gcProbability'' to 0.5 and set ''$gcLimit'' to roughly the number of active tickets currently present in your DB.

Continue to lower ''$gcProbability'' even further until the load becomes acceptable. When the load is acceptable, but queries take too long, reduce ''$gcLimit''.

External method

Simply call include/scripts/expire.php within a cron job, which should be executed with the same user as the web server. Executing the script once a day is sufficient for low traffic websites, but can be executed as often as needed. ''$gcLimit'' still controls how many tickets are expired for each run to limit the execution time.