This document contains information about a future release and not the current stable version (3.1).

Be aware that information on this page may change and API's may not be stable for production use.

Configuration in SilverStripe

Introduction

SilverStripe 3 comes with a comprehensive code based configuration system. It primarily relies on declarative YAML files, and falls back to procedural PHP code, as well as PHP static variables.

Configuration can be seen as separate from other forms of variables (such as per-member or per-site settings) in the SilverStripe system due to three properties:

  • Configuration is per class, not per instance
  • Configuration is normally set once during initialisation and then not changed
  • Configuration is normally set by a knowledgeable technical user, such as a developer, not the end user

In SilverStripe 3, each class has it's configuration specified as set of named properties and associated values. The values at any given time are calculated by merging several sources using rules explained below. These sources are as follows (in highest -> lowest priority order):

  • Values set via a call to Config::update()
  • Values taken from YAML files in specially named directories
  • Statics set on an "extra config source" class (such as an extension) named the same as the name of the property (optionally)
  • Statics set on the class named the same as the name of the property
  • The parent of the class (optionally)

Like statics, configuration values may only contain a literal or constant; neither objects nor expressions are allowed.

Finding Configuration

Since configuration settings are just static properties on any SilverStripe class, there's no exhaustive list. All configurable statics are marked with a @config docblock though, so you can search for them in the codebase. The same docblock will also contain a description of the configuration setting.

Customizing Configuration (through merging)

Each named class configuration property can contain either an array or a non-array value. If the value is an array, each value in the array may also be one of those three types

As mentioned, the value of any specific class configuration property comes from several sources. These sources do not override each other (except in one specific circumstance) - instead the values from each source are merged together to give the final configuration value, using these rules:

  • If the value is an array, each array is added to the beginning of the composite array in ascending priority order. If a higher priority item has a non-integer key which is the same as a lower priority item, the value of those items is merged using these same rules, and the result of the merge is located in the same location the higher priority item would be if there was no key clash. Other than in this key-clash situation, within the particular array, order is preserved.
  • If the value is not an array, the highest priority value is used without any attempt to merge

It is an error to have mixed types of the same named property in different locations (but an error will not necessarily be raised due to optimisations in the lookup code).

The exception to this is "false-ish" values - empty arrays, empty strings, etc. When merging a non-false-ish value with a false-ish value, the result will be the non-false-ish value regardless of priority. When merging two false-ish values the result will be the higher priority false-ish value.

The locations that configuration values are taken from in highest -> lowest priority order are:

  • Any values set via a call to Config#update
  • The configuration values taken from the YAML files in _config/ directories (internally sorted in before / after order, where the item that is latest is highest priority)
  • Any static set on an "additional static source" class (such as an extension) named the same as the name of the property
  • Any static set on the class named the same as the name of the property
  • The composite configuration value of the parent class of this class

At some of these levels you can also set masks. These remove values from the composite value at their priority point rather than add. They are much simpler. They consist of a list of key / value pairs. When applied against the current composite value - If the composite value is a sequential array, any member of that array that matches any value in the mask is removed - If the composite value is an associative array, any member of that array that matches both the key and value of any pair in the mask is removed - If the composite value is not an array, if that value matches any value in the mask it is removed

Reading and updating via the Config class

The Config class is both the primary manner of getting configuration values and one of the locations you can set configuration values.

Note: There is no way currently to restrict read or write access to any configuration property, or influence/check the values being read or written.

Global access

The first thing you need to do to use the Config class is to get the singleton instance of that class. This can be done by calling the static method Config::inst(), like so:

$config = Config::inst();

There are then three public methods available on the instance so obtained:

  • Config#get() returns the value of a specified classes' property
  • Config#remove() removes information from the value of a specified classes' property. To remove all values, use the Config::anything() placeholder.
  • Config#update() adds additional information into the value of a specified classes' property

Note that there is no "set" method. Because of the merge, it is not possible to completely set the value of a classes' property (unless you're setting it to a true-ish literal). Update adds new values that are treated as the highest priority in the merge, and remove adds a merge mask that filters out values.

Short-hand access

Within any subclass of Object you can call the config() instance method to get an instance of a proxy object which accesses the Config class with the class parameter already set.

For instance, instead of writing:

Config::inst()->get($this->class, 'my_property');
Config::inst()->update($this->class, 'my_other_property', 2);

You can write:

$this->config()->get('my_property');
$this->config()->update('my_other_property', 2);

Or even shorter:

$this->config()->my_property; // getter
$this->config()->my_other_property = 2; // setter

This also works statically:

MyClass::config()->my_property; // getter
MyClass::config()->my_property = 2; // setter

Setting configuration via YAML files

Each module can (in fact, should - see below for why) have a directory immediately underneath the main module directory called _config/.

Inside this directory you can add yaml files that contain values for the configuration system.

The structure of each yaml file is a series of headers and values separated by YAML document separators. If there is only one set of values the header can be omitted.

The header

Each value section of a YAML file has:

  • A reference path, made up of the module name, the config file name, and a fragment identifier
  • A set of rules for the value section's priority relative to other value sections
  • A set of rules that might exclude the value section from being used

The fragment identifier component of the reference path and the two sets of rules are specified for each value section in the header section that immediately preceeds the value section.

Reference paths and fragment identifiers

Each value section has a reference path. Each path looks a little like a URL, and is of this form: module/file#fragment.

  • "module" is the name of the module this YAML file is in.
  • "file" is the name of this YAML file, stripped of the extension (so for routes.yml, it would be routes).
  • "fragment" is a specified identifier. It is specified by putting a Name: {fragment} key / value pair into the header. section. If you don't specify a name, a random one will be assigned.

This reference path has no affect on the value section itself, but is how other header sections refer to this value section in their priority chain rules.

Priorities

Values for a specific class property can be specified in several value sections across several modules. These values are merged together using the same rules as the configuration system as a whole.

However unlike the configuration system itself, there is no inherent priority amongst the various value sections.

Instead, each value section can have rules that indicate priority. Each rule states that this value section must come before (lower priority than) or after (higher priority than) some other value section.

To specify these rules you add an "After" and/or "Before" key to the relevant header section. The value for these keys is a list of reference paths to other value sections. A basic example:

---
Name: adminroutes
After:
  - '#rootroutes'
  - '#coreroutes'
---
Director:
  rules:
    'admin': 'AdminRootController'
---

You do not have to specify all portions of a reference path. Any portion may be replaced with a wildcard "*", or left out all together. Either has the same affect - that portion will be ignored when checking a value section's reference path, and will always match. You may even specify just "*", which means "all value sections".

When a particular value section matches both a Before and an After rule, this may be a problem. Clearly one value section can not be both before and after another. However when you have used wildcards, if there was a difference in how many wildcards were used, the one with the least wildcards will be kept and the other one ignored.

A more complex example, taken from framework/_config/routes.yml:

---
Name: adminroutes
Before: '*'
After:
  - '#rootroutes'
  - '#coreroutes'
  - '#modelascontrollerroutes'
---
Director:
  rules:
    'admin': 'AdminRootController'
---

The value section above has two rules:

  • It must be merged in before (lower priority than) all other value sections

  • It must be merged in after (higher priority than) any value section with a fragment name of "rootroutes"

In this case there would appear to be a problem - adminroutes can not be both before all other value sections and after value sections with a name of rootroutes. However because \* has three wildcards (it is the equivalent of \*/\*#\*) but #rootroutes only has two (it is the equivalent of \*/\*#rootroutes). In this case \* means "every value section except ones that have a fragment name of rootroutes".

One important thing to note: it is possible to create chains that are unsolvable. For instance, A must be before B, B must be before C, C must be before A. In this case you will get an error when accessing your site.

Exclusionary rules

Some value sections might only make sense under certain environmental conditions - a class exists, a module is installed, an environment variable or constant is set, or SilverStripe is running in a certain environment mode (live, dev, etc).

To accommodate this, value sections can be filtered to only be used when either a rule matches or doesn't match the current environment.

To achieve this you add a key to the related header section, either "Only" when the value section should be included only when all the rules contained match, or "Except" when the value section should be included except when all of the rules contained match.

You then list any of the following rules as sub-keys, with informational values as either a single value or a list.

  • 'classexists', in which case the value(s) should be classes that must exist
  • 'moduleexists', in which case the value(s) should be modules that must exist
  • 'environment', in which case the value(s) should be one of "live", "test" or "dev" to indicate the SilverStripe mode the site must be in
  • 'envvarset', in which case the value(s) should be environment variables that must be set
  • 'constantdefined', in which case the value(s) should be constants that must be defined

For instance, to add a property to "foo" when a module exists, and "bar" otherwise, you could do this:

---
Only:
  moduleexists: 'MyFineModule'
---
MyClass:
  property: 'foo'
---
Except:
  moduleexists: 'MyFineModule'
---
MyClass:
  property: 'bar'
---

Note than when you have more than one rule for a nested fragment, they're joined like

FRAGMENT_INCLUDED = (ONLY && ONLY) && !(EXCEPT && EXCEPT)

That is, the fragment will be included if all Only rules match, except if all Except rules match.

Also, due to YAML limitations, having multiple conditions of the same kind (say, two EnvVarSet in one "Only" block) will result in only the latter coming through.

The values

The values section of a YAML configuration file is quite simple - it is simply a nested key / value pair structure where the top level key is the class name to set the property on, and the sub key / value pairs are the properties and values themselves (where values, of course, can themselves be nested hashes).

A simple example setting a property called "foo" to the scalar "bar" on class "MyClass", and a property called "baz" to a nested array on class "MyOtherClass":

MyClass:
  foo: 'bar'
MyOtherClass:
  baz:
    a: 1
    b: 2

Notice that we can leave out the header in this case because there is only a single value section within the file.

Setting configuration via statics

The final location that a property can get it's value from is a static set on the associated class. Statics should be considered immutable, and therefore the majority of statics in SilverStripe are marked private.

They should primarily be used to set the initial or default value for any given configuration property. It's also a handy place to hand a docblock to indicate what a property is for. However, it's worth noting that you do not have to define a static for a property to be valid.

Configuration as a module marker

Configuration files also have a secondary sub-role. Modules are identified by the ManifestBuilder by the presence of a _config/ directory (or a _config.php file) as a top level item in the module directory.

Although your module may choose not to set any configuration, it must still have a _config directory to be recognised as a module by the ManifestBuilder, which is required for features such as autoloading of classes and template detection to work.

Complex configuration through _config.php

In addition to the configuration system described above, each module can provide a file called _config.php immediately within the module top level directory.

These _config.php files will be included at initialisation, and are a useful way to set legacy configuration or set configuration based on rules that are more complex than can be encoded in YAML files.

However they should generally be avoided when possible, as they slow initialisation.

Please note that this is the only place where you can put in procedural code - all other functionality is wrapped in classes (see common-problems).

Configuration through the CMS

SilverStripe framework does not provide a method to set configuration via a web panel.

This lack of a configuration-GUI is on purpose, as we'd like to keep developer-level options where they belong (into code), without cluttering up the interface. See this core forum discussion "The role of the CMS" for further reasoning.

The GUI-based configuation is limited to the following:

  • Author-level configuration like interface language or date/time formats can be performed in the CMS "My Profile" section
  • Group-related configuration like HTMLEditorField settings can be found in the "Security" section
  • Site-wide settings like page titles can be set (and extended) on the root tree element in the CMS "Content" section (through the siteconfig API).
  • Any configuration interfaces added by custom code, for example through getCMSFields()

Constants and the _ss_environment.php File

See environment-management.

User preferences in the Member class

All user-related preferences are stored as a property of the Member-class (and as a database-column in the Member-table). You can "mix in" your custom preferences by using DataObject for details.

Permissions

See security and permission

Resource Usage (Memory and CPU)

SilverStripe tries to keep its resource usage within the documented limits (see our server requirements). These limits are defined through memory_limit and max_execution_time in the PHP configuration. They can be overwritten through ini_set(), unless PHP is running with the Suhoshin Patches or in "safe mode". Most shared hosting providers will have maximum values that can't be altered.

For certain tasks like synchronizing a large assets/ folder with all file and folder entries in the database, more resources are required temporarily. In general, we recommend running resource intensive tasks through the commandline, where configuration defaults for these settings are higher or even unlimited.

SilverStripe can request more resources through increase_memory_limit_to() and increase_time_limit_to(). If you are concerned about resource usage on a dedicated server (without restrictions imposed through shared hosting providers), you can set a hard limit to these increases through set_increase_memory_limit_max() and set_increase_time_limit_max(). These values will just be used for specific scripts (e.g. Filesystem::sync()), to raise the limits for all executed scripts please use ini_set('memory_limit', <value>) and ini_set('max_execution_time', <value>) in your own _config.php.

Comments

Comment policy: Please use comments for tips and corrections about the described functionality.
Comments are moderated, we reserve the right to remove comments that are inappropriate or are no longer relevant. Use the Silverstripe Forum to ask questions.

blog comments powered by Disqus