Loading...
 
Skip to main content
Type of page »  Feature page
5
Page actions
PDF Print

System Configuration

Ideal situation for system configuration text file

The data should be unreadable in case it is put in a web accessible directory

  1. It's rare but there are cases we we do not have a web a non web-accessible directory.
  2. Also, some users can make a mistake and move the file and expose data. This file can contain passwords or API keys to external systems


So the file should be named something like prefs.ini.php (so it's interpreted as a PHP file) and contain an initial block like:

Copy to clipboard
<?php
// Keep this block to avoid the content to be read from the internet.
if (strpos($_SERVER['SCRIPT_NAME'], basename(__FILE__)) !== false) {
	header('location: index.php');
	exit;
}
?>
[tikiwiki]
preference.theme = "amelia"

A file can be shared by multiple Tiki instances

For cases where an overview of all overrides is useful. The identifier in brackets is what is used in db/local.php ($system_configuration_identifier = 'production';)

Copy to clipboard
[production]
preference.unified_engine = "manticore"
preference.unified_manticore_index_prefix = "production_"

[acceptance]
preference.scheduler_delay = "100"
preference.unified_engine = "manticore"
preference.unified_manticore_index_prefix = "acceptance_"
preference.metatag_robots = "noindex, nofollow"
preference.zend_mail_handler = "file"
preference.sitesubtitle = "Acceptance instance"

[testing]
preference.scheduler_delay = "200"
preference.unified_engine = "manticore"
preference.unified_manticore_index_prefix = "acceptance_"
preference.metatag_robots = "noindex, nofollow"
preference.zend_mail_handler = "file"
preference.sitesubtitle = "Testing instance"
preference.theme = "amelia"

History Source Comments