Found 744 results for "docker configuration support"
The search executed in 0.002264236 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Policies / Node PoliciesNode Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has
Score: 0.89992255
|
||||||||||||
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Node PoliciesNode Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has
Score: 0.89992255
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / FormsForms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des
Score: 0.89649576
|
||||||||||||
|
|
Gitana / 4.0 / Forms / API / DependenciesDependencies JSON Schema provides support for dependencies as a means for describing dependencies between fields. Using dependencies, you can establish that property2 should be supplied when property1 is supplied. Alpaca supports both JSON Schema v3 and v4 syntax for declaring dependencies. We recommend using JSON Schema v4 syntax. In JSON Schema v4, a single dependencies block within the container object stores key/values which consist of the ID of the property (key) and an array of property ID
Score: 0.89649576
|
||||||||||||
|
|
Gitana / 4.0 / Forms / CMS / OverviewForms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des
Score: 0.89649576
|
||||||||||||
|
Does Cloud CMS support Single Sign On (SSO)?Yes, Cloud CMS supports SSO (Single Sign On) with a variety of authentication providers. Many of these providers are offered out-of-the-box -- including providers for Keycloak, Google, CAS and more. In addition, we allow you to implement your own SSO providers and customize the authentication handshake. To learn more about how Cloud CMS authentication providers work, check out the following documentation: https://www.cloudcms.com/documentation/appserver/services/auth.html Custom Authenticators a
Score: 0.89649576
|
||||||||||||
|
|
Gitana / 4.0 / Developers / Application Server / Services / Broadcast
Broadcast The Broadcast service is responsible for relaying messages to members of the application server cluster. It provides an essential publish and subscription service so that application server members can broadcast messages, receive messages and subscribe to topics and events that occur throughout the system. Essential Configuration {
"broadcast": {
"enabled":
Score: 0.89204544
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Authenticators / DefaultDefault The Default Authenticator supports the storage of the user object onto the request. The user variable on the request is set on login() and removed on logout(). Its presence is used to determine whether a user is authenticated or not. In addition, the Passport.js logIn and logout functions are supported. If they are available on the request, they will be invoked. Finally, req.session is supported. If req.session is available, its save() method will be called to persist session state after
Score: 0.88947415
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Authenticators / SessionSession The Session Authenticator supports the storage of the user object on the session. The user variable on the request is set on login() and removed on logout(). Its presence is used to determine whether a user is authenticated or not. In addition, the Passport.js logIn and logout functions are supported. If they are available on the request, they will be invoked. Finally, req.session is supported. If req.session is available, its save() method will be called to persist session state after l
Score: 0.88947415
|
||||||||||||
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Authenticators / DefaultDefault The Default Authenticator supports the storage of the user object onto the request. The user variable on the request is set on login() and removed on logout(). Its presence is used to determine whether a user is authenticated or not. In addition, the Passport.js logIn and logout functions are supported. If they are available on the request, they will be invoked. Finally, req.session is supported. If req.session is available, its save() method will be called to persist session state after
Score: 0.88947415
|
||||||||||||
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Authenticators / SessionSession The Session Authenticator supports the storage of the user object on the session. The user variable on the request is set on login() and removed on logout(). Its presence is used to determine whether a user is authenticated or not. In addition, the Passport.js logIn and logout functions are supported. If they are available on the request, they will be invoked. Finally, req.session is supported. If req.session is available, its save() method will be called to persist session state after l
Score: 0.88947415
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Single Sign On (SSO) / Google GSuiteGoogle GSuite This page provides a walkthrough of how to configure Cloud CMS Single Sign On (SSO) for Google GSuite. Google GSuite provides support for SSO (single-sign-on) to allow users to authenticate to Cloud CMS using their Google accounts. Google plays the role of the Identity Provider and uses SAML 2.0 to assert authentication to Cloud CMS. You can learn more about Google GSuite here: https://gsuite.google.com/ Create a SAML App To configure Cloud CMS to use Google GSuite, you must first
Score: 0.8867429
|
||||||||||||
|
|
Gitana / 4.0 / Data Engine / Authentication / Single Sign On (SSO) / Google GSuiteGoogle GSuite This page provides a walkthrough of how to configure Cloud CMS Single Sign On (SSO) for Google GSuite. Google GSuite provides support for SSO (single-sign-on) to allow users to authenticate to Cloud CMS using their Google accounts. Google plays the role of the Identity Provider and uses SAML 2.0 to assert authentication to Cloud CMS. You can learn more about Google GSuite here: https://gsuite.google.com/ Create a SAML App To configure Cloud CMS to use Google GSuite, you must first
Score: 0.8867429
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / EmailEmail Type: email This handler sends an email to a recipient. It fires the sendEmail action and accepts a standard configuration object for that action type. The config for this handler can be as simple as: { "templateKey": "abc" } Where abc is the key of an Email Template content node in your repository. This will work just as shown above for workflows that are launched with the runtime globals for repositoryId and branchId specified. Otherwise, you will have to provide them, something lik
Score: 0.8842341
|
||||||||||||
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / EmailEmail Type: email This handler sends an email to a recipient. It fires the sendEmail action and accepts a standard configuration object for that action type. The config for this handler can be as simple as: { "templateKey": "abc" } Where abc is the key of an Email Template content node in your repository. This will work just as shown above for workflows that are launched with the runtime globals for repositoryId and branchId specified. Otherwise, you will have to provide them, something lik
Score: 0.8842341
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Add Features
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 0.8721881
|
||||||||||||
|
|
Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Add Features
Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: {
"features": [{
"qname": "
Score: 0.8721881
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Adapters / DefaultDefault The default request adapter parses simple header and cookie information. It is generic adapter that can be used to interrogate the most common elements in an HTTP request. Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "default", "config": { "header": "{headerName}", "cookie": "{cookieName}", "trusted": false } } } } T
Score: 0.86901474
|
||||||||||||
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Adapters / DefaultDefault The default request adapter parses simple header and cookie information. It is generic adapter that can be used to interrogate the most common elements in an HTTP request. Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "default", "config": { "header": "{headerName}", "cookie": "{cookieName}", "trusted": false } } } } T
Score: 0.86901474
|
||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @fragment@fragment Used to identify a section of output that can be cached based on the presently known request-time dependencies or any dependencies resolved by nested elements or nested @dependency tags. Parameters There are no parameters for this tag. Examples Example #1: Restaurant List Here is a template block that lists restaurants: {@fragment} {@query sort="title" skip="2" limit="7" type="custom:restaurant"}
|