Found 611 results for "docker configuration encrypting-properties"
The search executed in 0.002053956 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Branches / ActionsActions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat
Score: 0.64501894
|
||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Features / Non-CyclicNon-Cyclic QName: f:non-cyclic Marks an association as one that does not allow cyclical chains in the graph. Cloud CMS does not assume that cyclical chains are invalid. In fact, for modeling some content, they may be encouraged. This feature gives you a way to indicate that some associations should not support them. An example of a valid cyclic graph might be one where you have multiple friends - Joe, Diane and Pete. An association might be modeled called "is best friends with". In this graph, w
Score: 0.64501894
|
||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 4.0 / Data Engine / Aspects / Non-CyclicNon-Cyclic QName: f:non-cyclic Marks an association as one that does not allow cyclical chains in the graph. Cloud CMS does not assume that cyclical chains are invalid. In fact, for modeling some content, they may be encouraged. This feature gives you a way to indicate that some associations should not support them. An example of a valid cyclic graph might be one where you have multiple friends - Joe, Diane and Pete. An association might be modeled called "is best friends with". In this graph, w
Score: 0.64501894
|
||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 4.0 / Data Engine / Branches / ActionsActions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat
Score: 0.64501894
|
||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 4.0 / Developers / Application Server / ClusteringClustering The Cloud CMS Application Server supports running on a single Node process as well as multiple Node processes. Node processes can run on a single server instance or can be spread across multiple server instances behind a load balancer. By default, the Application Server starts up and allocates itself to a single CPU. This is known as single mode. Even if you have a server with more than one CPU on it, the Application Server will still only bind to 1 of those CPUs. When the Application
Score: 0.6380322
|
||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Features / MultilingualMultilingual QName: f:multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale. Marking a node as f:multilingual does not automatically produce translations for you. However, once marke
Score: 0.632877
|
||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Features / Translation
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Multilingual QName: f:multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale. Marking a node as f:multilingual does not automatically produce translations for you. However, once marke
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Domain Group Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Configuration Domain Groups maintain a configuration that you can adjust or consult as you create, update and query for them. The following table pr
Domain Group Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Configuration Domain Groups maintain a configuration that you can adjust or consult as you create, update and query for them. The following table pr
Send Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All
Send Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All
Node Picker ID: node-picker The node-picker field type renders a modal picker for a node. The modal picker allows you to filter nodes as well as paginate, sort and inspect nodes. The picker supports single node and multi-node selection depending on how the field is configured. Sample configuration: {
"type": "node-picker"
}
The node picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the latter is used for selectio
Events Alpaca allows you to bind event handlers to containers and individual fields that are triggered either directly or via propagation. Event handlers can be registered in the following ways: Configuration driven by specifying functions within Alpaca options Using the postRender method and calling on() for individual fields By extending Alpaca Field implementation classes This document covers how to set these up. Event Types In general, event handlers are invoked with the this reference set t
Node Picker ID: node-picker The node-picker field type renders a modal picker for a node. The modal picker allows you to filter nodes as well as paginate, sort and inspect nodes. The picker supports single node and multi-node selection depending on how the field is configured. Sample configuration: {
"type": "node-picker"
}
The node picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the latter is used for selectio
Clustering The Cloud CMS Application Server supports running on a single Node process as well as multiple Node processes. Node processes can run on a single server instance or can be spread across multiple server instances behind a load balancer. By default, the Application Server starts up and allocates itself to a single CPU. This is known as single mode. Even if you have a server with more than one CPU on it, the Application Server will still only bind to 1 of those CPUs. When the Application
Web Content Management The Application Server provides the runtime for the Cloud CMS Web Content Management solution. Web Content Management is a term that enterprise vendors have been using for years to distinguish between the role that a CMS (content management system) plays for an organization - it may be used to collaborate around your internal documents, legal records, digital assets and many other content items in addition to your web and mobile content. Cloud CMS provides a Web Content Ma
Authentication Grant Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au
Changeset Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the
Web Content Management The Application Server provides the runtime for the Cloud CMS Web Content Management solution. Web Content Management is a term that enterprise vendors have been using for years to distinguish between the role that a CMS (content management system) plays for an organization - it may be used to collaborate around your internal documents, legal records, digital assets and many other content items in addition to your web and mobile content. Cloud CMS provides a Web Content Ma
Authentication Grant Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au
Changeset Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the
Copy Multiple Nodes ID: copyMultipleNodes Copies multiple nodes and any of their owned children to a new location in the content graph. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeIds array true An array of node IDs to be copied (soure nodes) targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID
Copy Node ID: copyNode Makes a copy of a node and any of its owned children to a new location in the content graph. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeId text true The ID of the source node. targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID of the branch of the target parent node. t
|