Last updated February 17, 2015. Created on July 2, 2012.
Edited by sidharrell, mtift, nedjo, webchick. Log in to edit this page.

The configuration API provides a central place for modules to store configuration data. This data can be simple configuration like your site name, or more complex information managed with configuration entities, such as views and content types.

Configuration is a place to store information that you would want to synchronize from development to production. This information is often created during site building and is not typically generated by regular users during normal site operation. The configuration API comes in two flavours - the (simple) Config API and the Configuration Entity API. The key difference is that the Config API is the singleton usecase. A singleton is where there can be only a single instance of this configuration. A good example would be the site's name. The Configuration Entity API should be used to store multiple sets of configuration - for example node types, views, vocabularies, and fields.

More information

Managing configuration in Drupal 8

Looking for support? Visit the Drupal.org forums, or join #drupal-support in IRC.

Comments

cosmicdreams’s picture

On this page we should provide a true overview (The Overview section is really a technical overview) that provides the reader a description of each section. Explain what the reader will gain if they read this documentation and why all the pieces of it are there.