You are here

Home » API reference » Configuration Management 7

README.txt in Configuration Management 7

Same filename and directory in other branches
  1. 7.2 README.txt
CONTENTS OF THIS FILE
---------------------

 * Introduction
 * Installation
 * Definitions
 * Usage
 * Design Decisions


INTRODUCTION
------------

The configuration management module enables the ability to keep track of
specific configurations on a Drupal site, provides the ability to move these
configurations between different environments (local, dev, qa, prod), and also
move configurations between completely different sites (migrate configurations)

This module is a rewrite of the features module without the features part of it.
The module also uses some concepts from the configuration management initiative,
specifically the concept of the "activestore" and "datastore" architecture.

The configuration module isn't a replacement for features. The vision is that 
they could work together. Features currently serves two purposes, 1) to group
configuration together to satisfy a certain use-case, and 2) the actual export
and management of configuration into a "feature" module. Features module is an
awesome module when using it for what it was built for, creating KIT compliant
features. The reality is most people that use features probably haven't even
read the KIT specification.


INSTALLATION
------------

After downloading the configuration module and uncompressing it, copy the whole 
configuration directory to your modules directory and activate the module.

DEFINITIONS
-----------
                                   
 * activestore
   
   The activestore is where configuration is read from by Drupal. The
   configuration module imports all exportables into the database.  All
   exportables effectively become faux-exportables, configuration is not read 
   from exported code.
   
 * datastore
 
   The datastore is configuration data stored on-disk using ctools exportable 
   files and configuration api exports.  This configuration is not read and
   accessed by Drupal for page construction. Configuration from the datastore
   is activated (imported) into the activestore. Drupal accesses configuration
   from the activestore.
   
 * config.export
 
   Documentation needs to be written.
 
 * migration
 
   Documentation needs to be written.
  

USAGE
-----

 * Tracking configuration
 
   Add documentation on how to track configuration.
 
 * Un-tracking configuration
 
   Add documentation on how to stop tracking configuration.
 
 * Migrate configuration to another site.
 
   Add documentation on how to migrate to another site.
 
 * General settings
 
   Describe what each setting does.


DESIGN DECISIONS
----------------

File

README.txt
View source 
  1. CONTENTS OF THIS FILE

  2. ---------------------

  3. 

  4.  * Introduction

  5.  * Installation

  6.  * Definitions

  7.  * Usage

  8.  * Design Decisions

  9. 

  10. 

  11. INTRODUCTION

  12. ------------

  13. 

  14. The configuration management module enables the ability to keep track of

  15. specific configurations on a Drupal site, provides the ability to move these

  16. configurations between different environments (local, dev, qa, prod), and also

  17. move configurations between completely different sites (migrate configurations)

  18. 

  19. This module is a rewrite of the features module without the features part of it.

  20. The module also uses some concepts from the configuration management initiative,

  21. specifically the concept of the "activestore" and "datastore" architecture.

  22. 

  23. The configuration module isn't a replacement for features. The vision is that 

  24. they could work together. Features currently serves two purposes, 1) to group

  25. configuration together to satisfy a certain use-case, and 2) the actual export

  26. and management of configuration into a "feature" module. Features module is an

  27. awesome module when using it for what it was built for, creating KIT compliant

  28. features. The reality is most people that use features probably haven't even

  29. read the KIT specification.

  30. 

  31. 

  32. INSTALLATION

  33. ------------

  34. 

  35. After downloading the configuration module and uncompressing it, copy the whole 

  36. configuration directory to your modules directory and activate the module.

  37. 

  38. DEFINITIONS

  39. -----------

  40.                                    

  41.  * activestore

  42.    

  43.    The activestore is where configuration is read from by Drupal. The

  44.    configuration module imports all exportables into the database.  All

  45.    exportables effectively become faux-exportables, configuration is not read 

  46.    from exported code.

  47.    

  48.  * datastore

  49.  

  50.    The datastore is configuration data stored on-disk using ctools exportable 

  51.    files and configuration api exports.  This configuration is not read and

  52.    accessed by Drupal for page construction. Configuration from the datastore

  53.    is activated (imported) into the activestore. Drupal accesses configuration

  54.    from the activestore.

  55.    

  56.  * config.export

  57.  

  58.    Documentation needs to be written.

  59.  

  60.  * migration

  61.  

  62.    Documentation needs to be written.

  63.   

  64. 

  65. USAGE

  66. -----

  67. 

  68.  * Tracking configuration

  69.  

  70.    Add documentation on how to track configuration.

  71.  

  72.  * Un-tracking configuration

  73.  

  74.    Add documentation on how to stop tracking configuration.

  75.  

  76.  * Migrate configuration to another site.

  77.  

  78.    Add documentation on how to migrate to another site.

  79.  

  80.  * General settings

  81.  

  82.    Describe what each setting does.

  83. 

  84. 

  85. DESIGN DECISIONS

  86. ----------------