| | |
|---|
| | | - mbstring, fileinfo, mcrypt (optional) |
|---|
| | | * PEAR packages distributed with Roundcube or external: |
|---|
| | | - MDB2 2.5.0 or newer |
|---|
| | | - Mail_Mime 1.6.0 or newer |
|---|
| | | - Net_SMTP 1.4.1 or newer |
|---|
| | | - Mail_Mime 1.7.0 or newer |
|---|
| | | - Net_SMTP 1.4.2 or newer |
|---|
| | | * php.ini options (see .htaccess file): |
|---|
| | | - error_reporting E_ALL & ~E_NOTICE (or lower) |
|---|
| | | - memory_limit > 16MB (increase as suitable to support large attachments) |
|---|
| | |
|---|
| | | CONFIGURATION HINTS |
|---|
| | | =================== |
|---|
| | | |
|---|
| | | RoundCube writes internal errors to the 'errors' log file located in the logs |
|---|
| | | Roundcube writes internal errors to the 'errors' log file located in the logs |
|---|
| | | directory which can be configured in config/main.inc.php. If you want ordinary |
|---|
| | | PHP errors to be logged there as well, enable the 'php_value error_log' line |
|---|
| | | in the .htaccess file and set the path to the log file accordingly. |
|---|
| | |
|---|
| | | DATABASE SETUP |
|---|
| | | ============== |
|---|
| | | |
|---|
| | | Note: Database for RoundCube must use UTF-8 character set. |
|---|
| | | Note: Database for Roundcube must use UTF-8 character set. |
|---|
| | | |
|---|
| | | * MySQL |
|---|
| | | ------- |
|---|
| | |
|---|
| | | |
|---|
| | | * PostgreSQL |
|---|
| | | ------------ |
|---|
| | | To use RoundCube with PostgreSQL support you have to follow these |
|---|
| | | To use Roundcube with PostgreSQL support you have to follow these |
|---|
| | | simple steps, which have to be done as the postgres system user (or |
|---|
| | | which ever is the database superuser): |
|---|
| | | |
|---|
| | |
|---|
| | | All this has been tested with PostgreSQL 8.x and 7.4.x. Older |
|---|
| | | versions don't have a -O option for the createdb, so if you are |
|---|
| | | using that version you'll have to change ownership of the DB later. |
|---|
| | | |
|---|
| | | |
|---|
| | | Database cleaning |
|---|
| | | ----------------- |
|---|
| | | Do keep your database slick and clean we recommend to periodically execute |
|---|
| | | bin/cleandb.php which finally removes all records that are marked as deleted. |
|---|
| | | Best solution is to install a cronjob running this script daily. |
|---|
| | | |
|---|
| | | |
|---|
| | | |
|---|
| | | MANUAL CONFIGURATION |
|---|
| | |
|---|
| | | UPGRADING |
|---|
| | | ========= |
|---|
| | | |
|---|
| | | If you already have a previous version of RoundCube installed, |
|---|
| | | If you already have a previous version of Roundcube installed, |
|---|
| | | please refer to the instructions in UPGRADING guide. |
|---|
| | | |
|---|
| | | |
|---|
| | |
|---|
| | | ========== |
|---|
| | | |
|---|
| | | There are two forms of optimisation here, compression and caching, both aimed |
|---|
| | | at increasing an end user's experience using RoundCube Webmail. Compression |
|---|
| | | at increasing an end user's experience using Roundcube Webmail. Compression |
|---|
| | | allows the static web pages to be delivered with less bandwidth. The index.php |
|---|
| | | of RoundCube Webmail already enables compression on its output. The settings |
|---|
| | | of Roundcube Webmail already enables compression on its output. The settings |
|---|
| | | below allow compression to occur for all static files. Caching sets HTTP |
|---|
| | | response headers that enable a user's web client to understand what is static |
|---|
| | | and how to cache it. |
|---|
