Found 563 results for "ui-dev configuration"

The search executed in 0.001489911 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / IBM COS Deployment Handler

IBM COS Deployment Handler Handles the deployment of one or more Deployment Packages to an IBM Cloud Object Store (COS) bucket. The IBM Cloud Object Store bucket is described by: apiKey serviceInstanceId endpointUrl location bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proce

Score: 0.59904736

Gitana / 3.2 / Guide / Guide / Docker / Kits / MongoDB Replica Set

MongoDB Replica Set The MongoDB Replica Set kit defines an environment with a 3 node MongoDB replica set and two Cloud CMS environments running against it The configuration files for this kit can be found in the Gitana SDK Running Start the mongo servers first and then initialize the cluster: docker login --username {docker-username} --password '{docker-password}' docker-compose up -d mongodb1 mongodb2 mongodb3 Initialize the replic set. only have to do this once since the mongo servers persist

Score: 0.59904736

Gitana / 4.0 / Data Engine / Behaviors / Actions / Sync Multiple Nodes

Sync Multiple Nodes ID: syncMultipleNodes Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. 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. node

Score: 0.59904736

Gitana / 4.0 / Data Engine / Behaviors / Actions / Sync Node

Sync Node ID: syncNode Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. 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

Score: 0.59904736

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / IBM COS Deployment Handler

IBM COS Deployment Handler Handles the deployment of one or more Deployment Packages to an IBM Cloud Object Store (COS) bucket. The IBM Cloud Object Store bucket is described by: apiKey serviceInstanceId endpointUrl location bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proce

Score: 0.59904736

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 0.58856046

Gitana / 3.2 / Guide / Guide / Features / Knowledge Sharing

Knowledge Sharing QName: f:knowledge-sharing Used to tag an association as to indicate that it "shares knowledge" between a source node and a target node. The source node is a node is a "knowledge space" and the target node is a "knowledge recipient". An association marked with f:sharing-knowledge will be considered to be an association that knowledge properties may propagate down when changes are made to a knowledge space node. By default, the a:child association which is used to mark relations

Score: 0.58856046

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Azure Blob Storage Deployment Handler

Azure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configurat

Score: 0.58856046

Gitana / 4.0 / Developers / Drivers / PHP

PHP Connect your PHP applications to Gitana Latest Version Version undefined Date The Gitana PHP driver is a client library used to facilitate connections to the Gitana API. The driver handles OAuth authentication and token management, HTTPS calls, and provides convenient methods and classes with which to perform content operations. It works against Gitana instances on our SaaS platform as well as on-premise installations. Installation To install, run: composer require cloudcms/cloudcms Example

Score: 0.58856046

Gitana / 4.0 / Data Engine / Aspects / Knowledge Sharing

Knowledge Sharing QName: f:knowledge-sharing Used to tag an association as to indicate that it "shares knowledge" between a source node and a target node. The source node is a node is a "knowledge space" and the target node is a "knowledge recipient". An association marked with f:sharing-knowledge will be considered to be an association that knowledge properties may propagate down when changes are made to a knowledge space node. By default, the a:child association which is used to mark relations

Score: 0.58856046

Gitana / 4.0 / Data Engine / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 0.58856046

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Azure Blob Storage Deployment Handler

Azure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configurat

Score: 0.58856046

Gitana / 3.2 / Guide / Guide / API / Data Types / Email

Email 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 The following table presents you the configuration properties. Property Type Default Read-Only Description to text The email addresses of the

Score: 0.58165586

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / HTTP Deployment Handler

HTTP Deployment Handler Handles the deployment of one or more Deployment Packages to a custom HTTP endpoint. The custom HTTP endpoint is described by: url statusUrl username password Custom HTTP endpoints are useful for a large variety of purposes, including writing data into custom databases, synchronizing content from Cloud CMS with existing Content Management products, hooking into custom logic for CDN or cache invalidation and much more. Configuration { "url": "{url}", "statusUrl": "

Score: 0.58165586

Gitana / 4.0 / Data Engine / API / Data Types / Email

Email 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 The following table presents you the configuration properties. Property Type Default Read-Only Description to text The email addresses of the

Score: 0.58165586

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / HTTP Deployment Handler

HTTP Deployment Handler Handles the deployment of one or more Deployment Packages to a custom HTTP endpoint. The custom HTTP endpoint is described by: url statusUrl username password Custom HTTP endpoints are useful for a large variety of purposes, including writing data into custom databases, synchronizing content from Cloud CMS with existing Content Management products, hooking into custom logic for CDN or cache invalidation and much more. Configuration { "url": "{url}", "statusUrl": "

Score: 0.58165586

Content Entry Forms Example

Cloud CMS lets you easily design and deploy forms for your web applications and content contributors. In this blog entry, we’ll walk through how you can do this within the Cloud CMS user interface. In this example, we’ll create a form that allows editors to create City Guide information. Note: in the Cloud CMS Trial there is a City Guide Content definition which can be used as a starting point or as a reference for this example. Add a Definition The Content Definitions can be found in the Cloud

Score: 0.58165586

Gitana / 3.2 / Guide / Guide / Auditing

Auditing Cloud CMS provides a built-in audit system that automatically logs the activity between users and content through API service methods. The audit system produces an audit trail consisting of audit records that document the access of every user, content object and service method. Audit records are created automatically if they are enabled for your tenant and for the repository against which the operation occurs. Auditing is only available for on-premise, Docker customers. How to Enable Au

Score: 0.5793903

Gitana / 3.2 / Guide / Guide / API / Data Types / Client

Client 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 Clients maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you t

Score: 0.5793903

Gitana / 4.0 / Data Engine / API / Data Types / Client

Client 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 Clients maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you t

Score: 0.5793903

Gitana / 4.0 / Data Engine / Platform / Auditing

Auditing Cloud CMS provides a built-in audit system that automatically logs the activity between users and content through API service methods. The audit system produces an audit trail consisting of audit records that document the access of every user, content object and service method. Audit records are created automatically if they are enabled for your tenant and for the repository against which the operation occurs. Auditing is only available for on-premise, Docker customers. How to Enable Au

Score: 0.5793903

Gitana / 4.0 / Self Managed / Docker / Overview

Docker Cloud CMS offers the option to run development and production installations of its software on-premise or within a virtual private cloud. This option is available to subscription customers and can be utilized in both a development and production capacity. The actual installation and management of the various services involved in a full-scale production-ready Cloud CMS deployment is facilitated greatly through the use of Docker. Docker provides a way for all of the various tiers to be enca

Score: 0.5793903

Gitana / 3.2 / Guide / Guide / API / Data Types / Registration

Registration 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}} The minimum registration flow looks like this: The application collects the user's email The application creates an Registration object. It stores t

Score: 0.57759035

Gitana / 4.0 / Data Engine / API / Data Types / Registration

Registration 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}} The minimum registration flow looks like this: The application collects the user's email The application creates an Registration object. It stores t

Score: 0.57759035

Gitana / 3.2 / Guide / Guide / Features / Behavior Binding

Behavior Binding QName: f:behavior-binding Marks an association as pointing to the implementation of a behavior for a policy on the source node. Valid target nodes include script nodes and rules. By applying this feature, you indicate that the target node script or rule should execute when the policy triggers. The target node (script or rule) must implement the f:behavior feature. For example, you might upload a JavaScript file that provides an implementation of a method to handle the afterNodeU

Score: 0.56865084