<?php

[0] Fix | Delete

/*

[1] Fix | Delete

[2] Fix | Delete

This file holds the configuration for letting Phorum connect to your

[3] Fix | Delete

database server. If you are running your site with a hosting provider

[4] Fix | Delete

and you do not know what to fill in here, please contact your hosting

[5] Fix | Delete

provider for advice.

[6] Fix | Delete

[7] Fix | Delete

*/

[8] Fix | Delete

[9] Fix | Delete

if (!defined('PHORUM')) return;

[10] Fix | Delete

[11] Fix | Delete

$PHORUM['DBCONFIG']=array(

[12] Fix | Delete

[13] Fix | Delete

// Database connection. See the end of this file for a detailed

[14] Fix | Delete

// description of the configuration options.

[15] Fix | Delete

'type' => 'mysql',

[16] Fix | Delete

'name' => '[[softdb]]',

[17] Fix | Delete

'server' => '[[softdbhost]]',

[18] Fix | Delete

'user' => '[[softdbuser]]',

[19] Fix | Delete

'password' => '[[softdbpass]]',

[20] Fix | Delete

'table_prefix' => '[[dbprefix]]',

[21] Fix | Delete

'port' => '3306',

[22] Fix | Delete

'socket' => NULL,

[23] Fix | Delete

[24] Fix | Delete

// An optional URL to redirect the user to when the database is down.

[25] Fix | Delete

// If you want to use this option, then remove the "//" in front of it.

[26] Fix | Delete

//'down_page' => 'http://www.example.com/phorum/down.html',

[27] Fix | Delete

[28] Fix | Delete

// An optional URL to redirect the user to when the database has to be

[29] Fix | Delete

// upgraded. If you want to use this option, then remove the "//"

[30] Fix | Delete

// in front of it.

[31] Fix | Delete

//'upgrade_page' => 'http://www.example.com/phorum/upgrade.html',

[32] Fix | Delete

[33] Fix | Delete

[34] Fix | Delete

// Specific options for the "mysql" database layer type.

[35] Fix | Delete

// -----------------------------------------------------------------

[36] Fix | Delete

[37] Fix | Delete

// Use which MySQL PHP extension? Either NULL, "mysql", "mysqli" or

[38] Fix | Delete

// "mysqli_replication" for master/slave setups.

[39] Fix | Delete

// If NULL, Phorum will autodetect the extension to use.

[40] Fix | Delete

// See the end of this file for a detailed description of this option.

[41] Fix | Delete

'mysql_php_extension' => NULL,

[42] Fix | Delete

[43] Fix | Delete

// Full text searching? 1=enabled, 0=disabled

[44] Fix | Delete

// This option determines whether Phorum will use MySQL's full text

[45] Fix | Delete

// algorithm for searching postings. If enabled, searching for postings

[46] Fix | Delete

// will be much faster. You will have to disable this feature in case

[47] Fix | Delete

// you are running a database version prior to MySQL 4.0.18.

[48] Fix | Delete

'mysql_use_ft' => '1',

[49] Fix | Delete

[50] Fix | Delete

// Don't populate the search table for mysql fulltext search

[51] Fix | Delete

// (useful if you use a alternate search backend which doesn't use

[52] Fix | Delete

// the search-table).

[53] Fix | Delete

'empty_search_table' => '0',

[54] Fix | Delete

[55] Fix | Delete

// Specifies the charset used for the "CREATE TABLE" statements and

[56] Fix | Delete

// the connection later on. For a list of valid MySQL charsets, see

[57] Fix | Delete

// http://dev.mysql.com/doc/refman/5.0/en/charset-charsets.html

[58] Fix | Delete

// or run the MySQL query "SHOW CHARACTER SET".

[59] Fix | Delete

// Beware: the charset names are different from the ones that are

[60] Fix | Delete

// used for specifying web site charsets. For example "utf-8" is not

[61] Fix | Delete

// a valid charset.

[62] Fix | Delete

'charset' => 'utf8',

[63] Fix | Delete

[64] Fix | Delete

// For master/slave setup (if the "mysql_php_extension" option is set to

[65] Fix | Delete

// "mysqli_replication") you need to specify the slave servers to use.

[66] Fix | Delete

// If you do not do this, all queries will go to the master server anyway.

[67] Fix | Delete

// See the end of this file for a detailed description of this option.

[68] Fix | Delete

'slaves' => array(),

[69] Fix | Delete

[70] Fix | Delete

);

[71] Fix | Delete

[72] Fix | Delete

/*

[73] Fix | Delete

[74] Fix | Delete

DETAILED CONFIGURATION FIELD DESCRIPTION

[75] Fix | Delete

----------------------------------------

[76] Fix | Delete

[77] Fix | Delete

* type:

[78] Fix | Delete

[79] Fix | Delete

The type of database. Typically 'mysql' (the only database type which

[80] Fix | Delete

is officially supported by the Phorum distribution). If your PHP version

[81] Fix | Delete

supports the "mysqli" extension, then do not change this field to "mysqli".

[82] Fix | Delete

Instead use the "mysql_php_extension" option.

[83] Fix | Delete

[84] Fix | Delete

* name:

[85] Fix | Delete

[86] Fix | Delete

The name of the database.

[87] Fix | Delete

[88] Fix | Delete

* server:

[89] Fix | Delete

[90] Fix | Delete

The hostname or IP-address of the database server. You only need to

[91] Fix | Delete

change this if the database server is running on a different system.

[92] Fix | Delete

[93] Fix | Delete

* user:

[94] Fix | Delete

[95] Fix | Delete

The username which is used for accessing the database server. The

[96] Fix | Delete

user must have full access rights to the database, for creating and

[97] Fix | Delete

maintaining the needed tables.

[98] Fix | Delete

[99] Fix | Delete

* password:

[100] Fix | Delete

[101] Fix | Delete

The password for the database user.

[102] Fix | Delete

[103] Fix | Delete

* table_prefix:

[104] Fix | Delete

[105] Fix | Delete

This table prefix will be at the front of all table names that are

[106] Fix | Delete

created and used by Phorum. You only need to change this in case you

[107] Fix | Delete

are using the same database for multiple Phorum installations.

[108] Fix | Delete

By changing the table prefix you can prevent the tables from the

[109] Fix | Delete

installations from colliding. E.g. set the table prefix for one

[110] Fix | Delete

installation to "phorum1" and the other to "phorum2".

[111] Fix | Delete

Important: never change the table prefix for a running system.

[112] Fix | Delete

[113] Fix | Delete

* port:

[114] Fix | Delete

[115] Fix | Delete

The mysql (network) port to use. 3306 is the MySQL default.

[116] Fix | Delete

[117] Fix | Delete

* socket

[118] Fix | Delete

[119] Fix | Delete

The UNIX socket file path to use for the connection. If this one

[120] Fix | Delete

is set to a value other than NULL and the server is set to

[121] Fix | Delete

"localhost", then Phorum will connect to the MySQL server

[122] Fix | Delete

through the provided socket path.

[123] Fix | Delete

[124] Fix | Delete

* mysql_php_extension (MySQL-only option):

[125] Fix | Delete

[126] Fix | Delete

The MySQL database layer has multiple extesions for supporting

[127] Fix | Delete

various MySQL connection types. Options are:

[128] Fix | Delete

NULL : Automatically detect the extension to use.

[129] Fix | Delete

"mysql" : Use the PHP mysql extension (php.ini needs a line like

[130] Fix | Delete

"extension=mysql.so" for this to work).

[131] Fix | Delete

"mysqli" : Use the PHP mysqli extension (php.ini needs a line like

[132] Fix | Delete

"extension=mysqli.so" for this to work).

[133] Fix | Delete

"mysqli_replication" : Use the PHP mysqli extension and enable

[134] Fix | Delete

master/slave functionality (see below with "slaves")

[135] Fix | Delete

[136] Fix | Delete

* slaves (for the mysql_php_extension option "mysqli_replication-only"):

[137] Fix | Delete

[138] Fix | Delete

This array can hold a number of slave-servers to use in master/slave mode.

[139] Fix | Delete

All write queries will go to the default server above, which is the master-

[140] Fix | Delete

server in this setup and read-load will be split randomly over the slave-

[141] Fix | Delete

servers specified in this array. If you want your master-server to get read-

[142] Fix | Delete

load as well you need to specify it here too.

[143] Fix | Delete

Some read-queries will go to the master-server anyway in case they are

[144] Fix | Delete

vulnerable to replication-lag.

[145] Fix | Delete

[146] Fix | Delete

Example:

[147] Fix | Delete

'slaves'=>array(

[148] Fix | Delete

array( // Database connection 1.

[149] Fix | Delete

'name' => 'phorum5',

[150] Fix | Delete

'server' => '192.168.1.5',

[151] Fix | Delete

'user' => 'phorum5',

[152] Fix | Delete

'password' => 'phorum5',

[153] Fix | Delete

'port' => '3306',

[154] Fix | Delete

'socket' => NULL),

[155] Fix | Delete

array( // Database connection 2.

[156] Fix | Delete

'name' => 'phorum5',

[157] Fix | Delete

'server' => '192.168.1.6',

[158] Fix | Delete

'user' => 'phorum5',

[159] Fix | Delete

'password' => 'phorum5',

[160] Fix | Delete

'port' => '3306',

[161] Fix | Delete

'socket' => NULL),

[162] Fix | Delete

array( // Database connection 3.

[163] Fix | Delete

'name' => 'phorum5',

[164] Fix | Delete

'server' => '192.168.1.7',

[165] Fix | Delete

'user' => 'phorum5',

[166] Fix | Delete

'password' => 'phorum5',

[167] Fix | Delete

'port' => '3306',

[168] Fix | Delete

'socket' => NULL)

[169] Fix | Delete

)

[170] Fix | Delete

[171] Fix | Delete

*/

[172] Fix | Delete

?>

[173] Fix | Delete

[174] Fix | Delete