Found 479 results for "docs api templates"

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

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.78973705

Gitana / 4.0 / Data Engine / Behaviors / Actions / Web Hook

Web Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca

Score: 0.78973705

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.78973705

Gitana / 3.2 / Guide / Guide / UI Developers Guide

UI Developers Guide The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature-complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired editorial

Score: 0.78100884

Gitana / 4.0 / Developers / User Interface Customization / Overview

UI Developers Guide The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature-complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired editorial

Score: 0.78100884

Gitana / 3.2 / Guide / Guide / Bulk Import / Nodes

Nodes The Cloud CMS Bulk Import tool makes it easy to import content from structured data files stored on disk. The Packager API provides several methods which can read content from directories and bulk import that content all in one fell-swoop. This includes content types, content instances and relational information between content items. This is useful for many scenarios including those where you may wish to store a master copy of your foundation content types and content instances for new pr

Score: 0.77206206

Gitana / 3.2 / Guide / Guide / Features / Container

Container QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl

Score: 0.77206206

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.73

3.2.73 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.73. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op

Score: 0.77206206

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.74

3.2.74 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.74. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op

Score: 0.77206206

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.76

3.2.76 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.76. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op

Score: 0.77206206

Gitana / 4.0 / Data Engine / Aspects / Container

Container QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl

Score: 0.77206206

Gitana / 4.0 / Data Engine / Bulk Import / Nodes

Nodes The Cloud CMS Bulk Import tool makes it easy to import content from structured data files stored on disk. The Packager API provides several methods which can read content from directories and bulk import that content all in one fell-swoop. This includes content types, content instances and relational information between content items. This is useful for many scenarios including those where you may wish to store a master copy of your foundation content types and content instances for new pr

Score: 0.77206206

How do I search for nested content?

Cloud CMS maintains two indexes that are of interest for finding things. The primary index is the MongoDB index - against which you can run any query you can dream up using the MongoDB DSL. The secondary index is the Elastic Search index - against which you can run any search you can dream up using the Elastic Search DSL. For information all kinds of really powerful stuff you can do with this, see: https://www.cloudcms.com/documentation/content-services/query.html https://www.cloudcms.com/docume

Score: 0.77206206

Programmatically create content in a folder?

The Cloud CMS content API lets you work with JSON to create any kind of content you'd like. It supports any JSON structure you desire and also supports a number of special properties that you can use to make life easier for you. These special properties are: _rootNodeId - The mount node ID of the root against which relatives path are computed. By default, this is the root of the repository. In general, it isn't necessary to use this property unless you have multiple mount nodes configured. And m

Score: 0.7468054

How we use Docker at Cloud CMS

At Cloud CMS, we use Docker to provision our cloud infrastructure servers on top of Amazon Web Services. Our stack consists of five different clusters: Cloud CMS API Cloud CMS UI Cloud CMS App Server for Dynamic Hosting Elastic Search MongoDB With the exception of MongoDB, all of these clusters are allocated using elastic load balancing and are architected in such a way that we can spin up new servers and tear down old ones with elastic demand. That is to say, they are fully elastic in design. T

Score: 0.7386329

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts

Contexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi

Score: 0.72578335

Gitana / 4.0 / Developers / User Interface Customization / Contexts

Contexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi

Score: 0.72578335

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.77

3.2.77 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.77. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.77 Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support fo

Score: 0.72314894

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.78

3.2.78 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.78. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.78 Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support fo

Score: 0.72314894

Gitana / 3.2 / Guide / Guide / API / System Metadata

System Metadata Cloud CMS automatically tracks system metadata for all of the objects that you create within it. System metadata consists of non-data values that describe things like who created an object and when it was modified. System Metadata This system metadata is tracked under the special _system key at the root of your objects. This system metadata is read-only in so far as it is tracked by Cloud CMS automatically. It is available for any object returned by any of the Cloud CMS APIs by s

Score: 0.7154833

Gitana / 4.0 / Data Engine / API / System Metadata

System Metadata Cloud CMS automatically tracks system metadata for all of the objects that you create within it. System metadata consists of non-data values that describe things like who created an object and when it was modified. System Metadata This system metadata is tracked under the special _system key at the root of your objects. This system metadata is read-only in so far as it is tracked by Cloud CMS automatically. It is available for any object returned by any of the Cloud CMS APIs by s

Score: 0.7154833

Gitana / 3.2 / Guide / Guide / Docker / Configuration / Antivirus Server

Antivirus Server The Cloud CMS Antivirus Server is a Node.js application that exposes a HTTP interface to allow an application to remotely scan files by submitting them via HTTP. Submitted files are passed through TCP to a ClamAV daemon process. API GET / If the server is online, this will always return: { "ok": true } POST /status This checks the status of the daemon process and returns whether the Antivirus service is working nominally. If everything is working well, you will get back som

Score: 0.70094514

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.75

3.2.75 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.75. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op

Score: 0.70094514

Gitana / 4.0 / Self Managed / Configuration / Antivirus Server

Antivirus Server The Cloud CMS Antivirus Server is a Node.js application that exposes a HTTP interface to allow an application to remotely scan files by submitting them via HTTP. Submitted files are passed through TCP to a ClamAV daemon process. API GET / If the server is online, this will always return: { "ok": true } POST /status This checks the status of the daemon process and returns whether the Antivirus service is working nominally. If everything is working well, you will get back som

Score: 0.70094514

Contact Us - Gitana

Contact Us - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and curate

Score: 0.70094514