It's expected that you have basic knowledge about running PHP and MySQL applications. Thus the following installation instructions will not provide in-depth coverage of these topics.
Unzip the downloaded cccp-pastebin-<version>-<status>.zip to any temporary directory.
1. Edit config.php and set the following to match your MySQL servers hostname, database name and credentials:
Replace myDB, myUser, myPassword (and possibly localhost) with your actual values.
2. Copy all PHP files and directories to a directory of your choice on your webserver.
3. Run the SQL statments in tables.sql on your MySQL database as you specified in step 1.
4. Point your browser to your newly created website.
Toggle paste history
By default, the end users can only see a list of his own recent pastes, but it is possible to
allow the end user to see all recent pastes. This can be toggled in config.php.
Disallow users to view all recent pastes: (default):
$ALLOW_PUBLIC = false;
Allow users to view all recent pastes:
$ALLOW_PUBLIC = true;
By default, the end users are forced to enter a security code (also known as a captcha),
when they submit a paste. This is enforced to prevent unwanted pastes from spam robots.
It can be toggled in config.php.
Force users to use a security code: (default):
$FORCE_CAPTCHA = true;
Allow users paste without a security code:
$FORCE_CAPTCHA = false;
Enable RSS feed of paste history
You must toggle paste history (see the above chapter) to allow users to view all recent pastes. Afterwards you can point your preferred RSS reader to http://<hostname>/<path>/rss.php
Upgrading from a previous release
You need to overwrite all Pastebin PHP files with the ones supplied in the latest release. The only exception from this rule is config.php. You can keep your old config.php, but your are urged to compare it with the latest version of config.php to ensure you don't miss out any new configuration parameters. The file config.php is pretty small, so this an easy task. When upgrading your are not required to make any changes in your MySQL tables, unless explicity informed to do so in the changelog.txt