Found 744 results for "docker configuration support"
The search executed in 0.002520456 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
Score: 0.7451864
|
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Remove Features
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 0.7451864
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment TargetDeployment Target A Deployment Target contains the configuration for a Deployment Handler. It informs the handler about how to connect or what settings should be used when executing. Deployment Targets are configured for Deployment Strategies as well as for Deployment Receivers. When content is changed within Cloud CMS, a Deployment Strategy may decide to package up that modified content and deployment it to one or more Deployment Targets. Similarly, content may be deployed to a Deployment Recei
Score: 0.7451864
|
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / IDID This section describes features that are coming in 4.0 The id condition allows you to constrain a policy statement so that it applies to entities that match a given ID. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "id", "config": { "id": "{value regex}" } } Samples This policy document grants the Consumer role to a specific piece of content with the ID 46ba5e0d79b83aac97e
Score: 0.7451864
|
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Type QNameType QName This section describes features that are coming in 4.0 The type-qname condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a principal to read content
Score: 0.7451864
|
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Remove Features
Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 0.7451864
|
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / DirectoryDirectory A directory is a data store that maintains identity objects and credentials. This consists of user passwords and authentication tokens for connectivity to third party "social" systems like Twitter, Facebook, LinkedIn and more. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and ret
Score: 0.7406537
|
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / DomainDomain A domain is a data store where you can store users, groups and memberships. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the be
Score: 0.7406537
|
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / RegistrarRegistrar A registrar is a data store where you store tenants and plans. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and
Score: 0.7406537
|
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / VaultVault A vault is a data store where you store backups, replications and exports of your data. A vault contains archives which are packages of your data. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others
Score: 0.7406537
|
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / Web HostWeb Host A web host is a data store where you store tenants and plans. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and c
Score: 0.7406537
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / DirectoryDirectory A directory is a data store that maintains identity objects and credentials. This consists of user passwords and authentication tokens for connectivity to third party "social" systems like Twitter, Facebook, LinkedIn and more. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and ret
Score: 0.7406537
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / DomainDomain A domain is a data store where you can store users, groups and memberships. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the be
Score: 0.7406537
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / RegistrarRegistrar A registrar is a data store where you store tenants and plans. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and
Score: 0.7406537
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / VaultVault A vault is a data store where you store backups, replications and exports of your data. A vault contains archives which are packages of your data. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others
Score: 0.7406537
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / Web HostWeb Host A web host is a data store where you store tenants and plans. ## Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and c
Score: 0.7406537
|
|
|
Gitana / 3.2 / Guide / Guide / Features / RelatedRelated QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For
Score: 0.7370279
|
|
|
Gitana / 3.2 / Guide / Guide / Features / Word CountWord Count QName: f:word-count Indicates that a node should track the number of words in each text property. Configuration Word Count Example Suppose we have a content type (my:article) that looks like this: { "_qname": "my:article", "_type": "d:type", "type": "object", "properties":{ "title": { "type": "string" }, "body": { "type": "string" } }, "mandatoryFeatures": { "f:word-count": {} } } Now we create
Score: 0.7370279
|
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / PropertyProperty This section describes features that are coming in 4.0 The property condition allows you to constrain a policy statement so that it applies to entities where a specific property matches a value. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "property", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu
Score: 0.7370279
|
|
|
Gitana / 3.2 / Guide / Guide / Text Analysis / Text Analysis Providers / AWS ComprehendAWS Comprehend Handles the Text Analysis processing of elements in a textual payload using the Amazon Web Service Comprehend Service. The AWS Comprehend Service is described by: accessKey secretKey region Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Comprehend within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given S3 bucket (identified by buck
Score: 0.7370279
|
|
|
Gitana / 4.0 / Data Engine / Aspects / RelatedRelated QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For
Score: 0.7370279
|
|
|
Gitana / 4.0 / Data Engine / Aspects / Word CountWord Count QName: f:word-count Indicates that a node should track the number of words in each text property. Configuration Word Count Example Suppose we have a content type (my:article) that looks like this: { "_qname": "my:article", "_type": "d:type", "type": "object", "properties":{ "title": { "type": "string" }, "body": { "type": "string" } }, "mandatoryFeatures": { "f:word-count": {} } } Now we create
Score: 0.7370279
|
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / PropertyProperty This section describes features that are coming in 4.0 The property condition allows you to constrain a policy statement so that it applies to entities where a specific property matches a value. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "property", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu
Score: 0.7370279
|
|
|
Gitana / 4.0 / Data Engine / Services / Text Analysis / Text Analysis Providers / AWS ComprehendAWS Comprehend Handles the Text Analysis processing of elements in a textual payload using the Amazon Web Service Comprehend Service. The AWS Comprehend Service is described by: accessKey secretKey region Where the accessKey and secretKey are used to identify an IAM principal who has sufficient authority to invoke AWS Comprehend within the given region. In addition, the IAM principal needs sufficient authorities to read, write and delete an S3 object from the given S3 bucket (identified by buck
Score: 0.7370279
|
|
|
Gitana / 3.2 / Guide / Guide / Features / PreviewablePreviewable QName: f:previewable Automates the creation and updating of "preview" attachments for one or more attachments on this node. Preview attachments are secondary binary attachments that are the result of one or more transformation operations to the original attachment. As an example, you might apply the f:previewable feature to a node that holds a PDF. The preview configuration lets you split the PDF into multiple pages and store snapshots of those pages as image/jpeg attachments on the
Score: 0.7342502
|