Found 563 results for "ui-dev configuration"
The search executed in 0.001663178 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Application Server / Services / Locks
Locks The Locks Service is used internally by the Application Server to coordinate access to shared cluster resources. The Locks Service is automatically configured to use Redis when the server is running in "cluster" mode. A configuration block is only required if you do not use environment variables to define redis server configuration. Configuration {
"locks": {
"enabled": true,
"type": "redis",
"config": {
"url": "
Score: 0.9246378
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Adapters / SessionSession The session adapter checks the session to find user profile information. Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "session" } } } The value {adapterId} can be any unique ID across the adapters. This is the ID that you reference from within your strategy configuration. Usage To grab authenticated user profile from the session, you might do: { "adapters": { "{adapterId}": {
Score: 0.90740246
|
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Adapters / SessionSession The session adapter checks the session to find user profile information. Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "session" } } } The value {adapterId} can be any unique ID across the adapters. This is the ID that you reference from within your strategy configuration. Usage To grab authenticated user profile from the session, you might do: { "adapters": { "{adapterId}": {
Score: 0.90740246
|
|
|
Gitana / 3.2 / Guide / Guide / 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.8998889
|
|
|
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.8997514
|
|
|
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.8997514
|
|
|
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.89193106
|
|
|
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.8893991
|
|
|
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.8893991
|
|
|
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.8893991
|
|
|
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.8893991
|
|
|
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.8841127
|
|
|
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.8841127
|
|
More Ways to Run Cloud CMS On-PremiseWe just released Cloud CMS version 3.1.315 which includes more sample configurations to help customers and prospects get started with on-premise Docker deployments. Our Docker distribution includes several “kits” that contain pre-built Docker Compose configurations that help customers to get up and running right away. These configurations can either be used as is or they may serve as a reference for building out new configurations that meet a customer’s exact needs. Cloud CMS offers Docker as an
Score: 0.87814754
|
|
|
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.87209624
|
|
|
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.87209624
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Services / AwarenessAwareness The Awareness Service is responsible for tracking the location of users within a client-side application. As users navigate within a client-side application, they are seamlessly joined and removed from channels (or rooms). As users enter and leave a channel, event handling is triggered, allowing the client-side application to learn of other users who are in a channel or when other users enter or leave a channel. The Awareness Service uses Socket.IO under the hood to provide support for
Score: 0.87008667
|
|
|
Gitana / 4.0 / Developers / Application Server / Services / AwarenessAwareness The Awareness Service is responsible for tracking the location of users within a client-side application. As users navigate within a client-side application, they are seamlessly joined and removed from channels (or rooms). As users enter and leave a channel, event handling is triggered, allowing the client-side application to learn of other users who are in a channel or when other users enter or leave a channel. The Awareness Service uses Socket.IO under the hood to provide support for
Score: 0.87008667
|
|
|
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.86888015
|
|
|
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.86888015
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / GitHubGitHub Cloud CMS provides integrated authentication and single-sign-on (SSO) with GitHub. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against GitHub. For more information on Authentication within the App Server, see App Server Authentication / SSO. GitHub API Keys You will need to configure a GitHub application and have the following infor
Score: 0.86647725
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / GoogleGoogle Cloud CMS provides integrated authentication and single-sign-on (SSO) with Google. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against Google. For more information on Authentication within the App Server, see App Server Authentication / SSO. Google API Keys You will need to configure a Google application and have the following infor
Score: 0.86647725
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / LinkedInLinkedIn Cloud CMS provides integrated authentication and single-sign-on (SSO) with LinkedIn. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against LinkedIn. For more information on Authentication within the App Server, see App Server Authentication / SSO. LinkedIn API Keys You will need to configure a LinkedIn application and have the follo
Score: 0.86647725
|
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Providers / TwitterTwitter Cloud CMS provides integrated authentication and single-sign-on (SSO) with Twitter. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against Twitter. For more information on Authentication within the App Server, see App Server Authentication / SSO. Twitter API Keys You will need to configure a Twitter application and have the following
Score: 0.86647725
|
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / GitHubGitHub Cloud CMS provides integrated authentication and single-sign-on (SSO) with GitHub. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against GitHub. For more information on Authentication within the App Server, see App Server Authentication / SSO. GitHub API Keys You will need to configure a GitHub application and have the following infor
Score: 0.86647725
|