System settings api

System Settings API
A look at a draft API for storing System Settings

There’s CODE!
That’s gold right?
project as it stands now:
http://github.com/tizzo/system_settings
mainly an alternative backend for variable_set and variable_get

The Mission
Expand on the great work on exportables by getting the system (or something similar)
Make everything exportable by default
Provide Drupal with a robust way to identify and replicate features

Hierarchy
Settings can be specified in
hooks
overridden in the database
overridden again by alter_hooks
finally overridden in settings.php

Features
Everything exportable and overrideable
Pluggable storage backend
Change management
Rich settings metadata

Metadata
Metadata is stored so that settings can be related to one another
We can identify all settings related to a content type or to a given module
Settings no longer build up in the database (settings no longer associated can be purged)

Metadata
Metadata can be specified simply by defining the unique key of the each entry (either simple or compex)

Metadata Structure
A single setting is atomic structured data and self contained
Contains all of its relations and its value

Metadata: An Individual Relation
Each relation has a unique key (simple or complex) and an arbitrary set of additional data

Change Monitoring
Each time the cache is rebuilt a version of each setting stored during the last cache build is compared to the version generated now
If a change is detected (whether because of code or database) callbacks can be triggered to respond to the change

System settings api

by htyson

Accessibility

Upload Details

Usage Rights

Statistics

System settings api Presentation Transcript