Found 620 results for "gitana 4.0 developers api resources branch post-repositories-repositoryid-b-query"

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

Gitana 3.2 / Guide / Guide / Workflow

Learn all about workflow models, tasks, events, and more for creating efficient business processes on Cloud CMS. Explore step-by-step examples and best practices.

Score: 2.1867576

Gitana 4.0 / Content Engine / Workflow

Explore workflow models, instances, tasks, and more. Understand how content is routed, tracked, and completed efficiently.

Score: 2.1867576

Gitana 3.2 / Guide / Guide / Features / Locked

Learn about the node locking functionality with the f:locked QName to efficiently manage edit permissions and control access.

Score: 2.1864548

Gitana 4.0 / Content Engine / Aspects / Locked

Learn about the node locking functionality with the f:locked QName to efficiently manage edit permissions and control access.

Score: 2.1864548

Pagination options

You can specify pagination options in an optional second argument to the queryNodes function, basically like this: Chain(branch).queryNodes({  "_type": "video:essentials"  }, {  "sort": {  "title": -1  },  "limit": 10,  "skip": 30  }).then(function() {  ...  }); In this example, the results will start at index 30 in the record set and will contain the next 10 entries. The record set is sorted by "title" in a descending order ahead of being returned. If pagination sort isn't provided, then the o

Score: 2.1864548

How to get a content definition JSON from the Cloud CMS API?

There are a couple of ways to do this. The first is simply use the node GET call and pass in the qname like this: GET /repositories/{repositoryId}/branches/{branchId}/nodes/{qname} http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId This will give you back the JSON for the definition. Another way is to use this variation: GET /repositories/{repositoryId}/branches/{branchId}/definitions/{qname} http://api.cloudcms.com/docs#!/branch/get_repositories_rep

Score: 2.1661923

Gitana 4.0 / Reference / Types / Changeset

Explore Changeset API for Cloud CMS to manage your branch content with ease. Enhance content curation and authoring with advanced features.

Score: 2.15724

Difference between an Application and a Project

A Project is a logical separation for work within Cloud CMS. It could be a site, a sub-site, a department, a web project or anything else you'd like. Projects let you organize teams, invite members and provide a place for you to collaborate on content. An Application is something that you create to provision resources and services dedicated to your web site or web/mobile application. Each Application provides storage and services that your app can access for things like user registration, passwo

Score: 2.1313467

Gitana 3.2 / Guide / Guide / Docker / Container Services

Discover how to set up the Gitana platform on container services with examples for Amazon ECS and Kubernetes frameworks.

Score: 2.0878143

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

Effortlessly deploy packages to custom HTTP endpoints for advanced data management and integration with this powerful handler.

Score: 2.0840929

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

Deploy and manage custom packages to HTTP endpoints efficiently. Integrate with databases, CDNs, and more using basic authentication.

Score: 2.0840929

Gitana 3.2 / Guide / Guide / Application Server / Installation / Docker Installation

Get started with Cloud CMS Application Server using Docker. Learn installation, configuration, and setup for seamless integration across platforms.

Score: 2.0811095

Gitana 4.0 / Developers / Application Server / Installation / Docker Installation

Easily install and configure Cloud CMS on Docker with our step-by-step guide. Learn to build, run, and connect using Docker and Git tools.

Score: 2.0811095

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: 2.080889

Gitana 3.2 / Guide / Guide / UI Developers Guide / Contexts / project-context

Discover tools for managing projects, exploring content models, and more with developer and manager permissions on our versatile project platform.

Score: 2.0561128

Gitana 4.0 / Developers / User Interface Customization / Contexts / project-context

Discover tools for managing projects, exploring content models, and more with developer and manager permissions on our versatile project platform.

Score: 2.0561128

Query Performance

Application queries Application code which consumes Cloud CMS content typically runs query API calls. These queries can be optimized in the following ways: Request only the properties needed When an application requires only a few properties from a set of nodes you should use “_fields” to limit the properties returned. This can drastically reduce the size of the payload and therefore the response time. In this example, we only need “_doc”, “title” and “_type” so these are the only fields that wi

Score: 2.0520892

How do I retrieve the folder path for my content?

In Cloud CMS, you may choose to associate nodes with folders. This allows the content to be worked with by editorial teams such that they can navigate to content within folders, move content between folders and generally organize their content as they wish. It also allows for content to be retrieved by path via the API, if you wish. Technically speaking, Cloud CMS does not require folders or paths. In fact, plenty of customers use Cloud CMS in such a way that they don't require folders at all. C

Score: 2.0465832

Gitana 4.0 / Developers / Drivers / JavaScript / Node

Connect Node apps to Gitana with our JavaScript 2.0 driver, supporting ECMAScript promises for seamless integration with popular frameworks.

Score: 2.0320857

Gitana 3.2 / Guide / Guide / Docker

Optimize your Cloud CMS deployment with Docker for scalable, production-ready environments—perfect for on-premise or virtual private clouds.

Score: 2.0243454

Gitana 3.2 / Guide / Guide / Bulk Import / Nodes

Easily import content with Cloud CMS Bulk Import tool from structured files on disk, supporting articles and authors like Daenerys and Jon.

Score: 2.0228524

Gitana 4.0 / Content Engine / Bulk Import / Nodes

Efficiently import and manage content with Cloud CMS Bulk Import tool using structured data files, perfect for organizing projects with ease.

Score: 2.0228524

Gitana 4.0 / Self Managed / Docker

Optimize Cloud CMS deployment with Docker for seamless on-premise and virtual private cloud management solutions. Efficiently manage services with Docker's microservices.

Score: 2.0130286

Gitana 3.2 / Guide / Guide / Authentication / OAuth 2.0

Securely authenticate clients and users with Cloud CMS's OAuth2 support, industry-standard authorization, and explore its robust features through our comprehensive guide.

Score: 2.0059655

Gitana 4.0 / Developers / Authentication / OAuth 2.0

Securely authenticate clients and users with Cloud CMS's OAuth2 support, industry-standard authorization, and explore its robust features through our comprehensive guide.

Score: 2.0059655