1 Config values that can only be set in config/local.config.php
2 ==========================================================
6 Friendica's configuration is done in two places: in PHP array configuration files and in the `config` database table.
7 Database config values overwrite the same file config values.
11 The configuration format for file configuration is an array returned from a PHP file.
12 This prevents your webserver from displaying your private configuration. It interprets the configuration files and displays nothing.
14 A typical configuration file looks like this:
29 'array' => ['value0', 'value1', 'value2'],
34 ### Configuration location
36 The `config` directory holds key configuration files:
38 - `defaults.config.php` holds the default values for all the configuration keys that can only be set in `local.config.php`.
39 - `settings.config.php` holds the default values for some configuration keys that are set through the admin settings page.
40 - `local.config.php` holds the current node custom configuration.
41 - `addon.config.php` is optional and holds the custom configuration for specific addons.
43 Addons can define their own default configuration values in `addon/[addon]/config/[addon].config.php` which is loaded when the addon is activated.
45 #### Migrating from .htconfig.php to config/local.config.php
47 The legacy `.htconfig.php` configuration file is still supported, but is deprecated and will be removed in a subsequent Friendica release.
49 The migration is pretty straightforward:
50 If you had any addon-specific configuration in your `.htconfig.php`, just copy `config/addon-sample.config.php` to `config/addon.config.php` and move your configuration values.
51 Afterwards, copy `config/local-sample.config.php` to `config/local.config.php`, move the remaining configuration values to it according to the following conversion chart, then rename your `.htconfig.php` to check your node is working as expected before deleting it.
56 background-color: #f9f9f9;
57 border: 1px solid #aaa;
58 border-collapse: collapse;
63 table.config > tr > th,
64 table.config > tr > td,
65 table.config > * > tr > th,
66 table.config > * > tr > td {
67 border: 1px solid #aaa;
71 table.config > tr > th,
72 table.config > * > tr > th {
73 background-color: #f2f2f2;
79 <table class="config">
82 <th>.htconfig.php</th>
83 <th>config/local.config.php</th>
89 $db_host = 'localhost';
90 $db_user = 'mysqlusername';
91 $db_pass = 'mysqlpassword';
92 $db_data = 'mysqldatabasename';
93 $a->config["system"]["db_charset"] = 'utf8mb4';
97 'hostname' => 'localhost',
98 'username' => 'mysqlusername',
99 'password' => 'mysqlpassword',
100 'database' => 'database',
101 'charset' => 'utf8mb4',
107 $a->config["section"]["key"] = "value";
117 $a->config["section"]["key"] = array(
125 'key' => ['value1', 'value2', 'value3'],
131 $a->config["key"] = "value";
141 $a->config['register_policy'] = REGISTER_CLOSED;
145 'register_policty' => REGISTER_CLOSED,
155 'urlpath' => 'value',
161 $default_timezone = "value";
165 'default_timezone' => 'value',
175 'pidfile' => 'value',
185 'language' => 'value',
192 #### Migrating from config/local.ini.php to config/local.config.php
194 The legacy `config/local.ini.php` configuration file is still supported, but is deprecated and will be removed in a subsequent Friendica release.
196 The migration is pretty straightforward:
197 If you had any addon-specific configuration in your `config/addon.ini.php`, just copy `config/addon-sample.config.php` to `config/addon.config.php` and move your configuration values.
198 Afterwards, copy `config/local-sample.config.php` to `config/local.config.php`, move the remaining configuration values to it according to the following conversion chart, then rename your `config/local.ini.php` file to check your node is working as expected before deleting it.
200 <table class="config">
203 <th>config/local.ini.php</th>
204 <th>config/local.config.php</th>
212 username = mysqlusername
213 password = mysqlpassword
214 database = mysqldatabasename
219 'hostname' => 'localhost',
220 'username' => 'mysqlusername',
221 'password' => 'mysqlpassword',
222 'database' => 'database',
223 'charset' => 'utf8mb4',
241 register_policty = REGISTER_CLOSED
245 'register_policty' => REGISTER_CLOSED,
258 'key' => ['value1', 'value2', 'value3'],
267 ### Database Settings
269 The configuration variables database.hostname, database.username, database.password, database.database and database.charset are holding your credentials for the database connection.
270 If you need to specify a port to access the database, you can do so by appending ":portnumber" to the database.hostname variable.
273 'hostname' => 'your.mysqlhost.com:123456',
276 If all of the following environment variables are set, Friendica will use them instead of the previously configured variables for the db:
284 ## Config values that can only be set in config/local.config.php
286 There are some config values that haven't found their way into the administration page.
287 This has several reasons.
288 Maybe they are part of a current development that isn't considered stable and will be added later in the administration page when it is considered safe.
289 Or it triggers something that isn't expected to be of public interest.
290 Or it is for testing purposes only.
292 **Attention:** Please be warned that you shouldn't use one of these values without the knowledge what it could trigger.
293 Especially don't do that with undocumented values.
295 These configurations keys and their default value are listed in `config/defaults.config.php` and should be overwritten in `config/local.config.php`.
297 ## Administrator Options
299 Enabling the admin panel for an account, and thus making the account holder admin of the node, is done by setting the variable
302 'admin_email' => 'someone@example.com',
306 Where you have to match the email address used for the account with the one you enter to the `config/local.config.php` file.
307 If more then one account should be able to access the admin panel, separate the email addresses with a comma.
310 'admin_email' => 'someone@example.com,someoneelse@example.com',
313 If you want to have a more personalized closing line for the notification emails you can set a variable for the `admin_name`.
316 'admin_name' => 'Marvin',