Stages Documentation

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
Next revisionBoth sides next revision
74:cms_configuration [2019/10/16 10:18] – [Common Configuration] tssr74:cms_configuration [2019/10/16 10:26] – [CMS Configuration] tssr
Line 1: Line 1:
 ====== CMS Configuration ====== ====== CMS Configuration ======
  
-Stages can interact with configuration management systems (CMS) to work with remotely stored files. The configuration for these systems is done in two simple steps:+Stages can interact with configuration management systems to work with remotely stored files. The configuration for these systems is done in two simple steps:
  
-  - Add the XML snippet explained in [[:74:cms_configuration#common_configuration|this section]] to your Stages configuration for each configuration management system you want to work with+  - Add the xml snippet explained in [[:74:cms_configuration#common_configuration|this section]] to your Stages configuration for each configuration management system you want to work with
   - Adjust this snippet for the specific configuration management system according to the explanations below   - Adjust this snippet for the specific configuration management system according to the explanations below
  
Line 45: Line 45:
 > cms > cms
  
-  * Description: This element holds all configuration data for content management systems.+  * __Description__: This element holds all configuration data for content management systems.
  
 > cms-type | Attributes: name > cms-type | Attributes: name
  
-  * Description: The cms-type element represents the configuration for a single content management system you want to support in your Stages application. +  * __Description__: The cms-type element represents the configuration for a single content management system you want to support in your Stages application. 
-  * Attributes:+  * __Attributes__:
     * //name//: The attribute name of each cms-type is crucial for the system to work. Every cms implementation has its own and unique name.     * //name//: The attribute name of each cms-type is crucial for the system to work. Every cms implementation has its own and unique name.
  
 > cms-property | Attributes: name, value | //<!-- Global Properties -->// > cms-property | Attributes: name, value | //<!-- Global Properties -->//
  
-  * Description: Inside the cms-type element you can define multiple cms-property elements, which affect the entire cms type. These properties are called global properties. +  * __Description__: Inside the cms-type element you can define multiple cms-property elements, which affect the entire cms type. These properties are called global properties. 
-  * Attributes:+  * __Attributes__:
     * //name//: The attribute name identifies the property by its key.     * //name//: The attribute name identifies the property by its key.
     *//value//: The value attribute defines the value for that property.     *//value//: The value attribute defines the value for that property.
Line 62: Line 62:
 > cms-host | Attributes: ident, name, displayName > cms-host | Attributes: ident, name, displayName
  
-  * Description: Every cms-type element can have several cms-host elements. Each cms-host represents an endpoint, Stages can establish a connection and exchange data. +  * __Description__: Every cms-type element can have several cms-host elements. Each cms-host represents an endpoint, Stages can establish a connection and exchange data. 
-  * Attributes:+  * __Attributes__:
     * //ident//: The ident of a cms-host is a simple string but has to be unique for the Stages server.     * //ident//: The ident of a cms-host is a simple string but has to be unique for the Stages server.
     * //name//: The name attribute identifies the server by the url of the content management system. Please note that this url must contain the **protocol**, the server's **host name** (not its IP address), optionally a port number, and **NO**  path elements (e.g. <nowiki>https://myhost:10443</nowiki><del>/some/path</del>).     * //name//: The name attribute identifies the server by the url of the content management system. Please note that this url must contain the **protocol**, the server's **host name** (not its IP address), optionally a port number, and **NO**  path elements (e.g. <nowiki>https://myhost:10443</nowiki><del>/some/path</del>).
Line 70: Line 70:
 > cms-property | Attributes: name, value | //<!-- Host Properties -->// > cms-property | Attributes: name, value | //<!-- Host Properties -->//
  
-  * Description: Inside a cms-host element you can define cms-property elements, which affect only the specific host. These properties are called host properties. +  * __Description__: Inside a cms-host element you can define cms-property elements, which affect only the specific host. These properties are called host properties. 
-  * Attributes:+  * __Attributes__:
     * //name//: The attribute name identifies the property by its key.     * //name//: The attribute name identifies the property by its key.
     * //value//: The value attribute defines the value for that property.     * //value//: The value attribute defines the value for that property.