Found 171 results for "api repository branch"

The search executed in 0.0 seconds

API Keys

API Keys For information on API Keys, please visit the Cloud CMS - API Keys Developer Page.

Score: 33.54238

API

API The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish

Score: 30.650894

Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 22.863642

Branches

Branches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git or Mercurial and provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changsets. Transactions span multiple documents

Score: 19.54145

API / Data Types / Branch

Branch Type branch Datastore Type repository Supports authorities, permissions, transfer You can have as many branches as you want. Each branch is a completely isolated workspace. Thus, you can create your own branch for your own projects. You can work on those projects and when you're happy with it, you can share it with the rest of the team. Or, you can create a branch and invite a bunch of people to work with you. They're your own workspaces. You can play with them however you want. Changeset

Score: 19.47353

Docker / Maintenance / Repository Compression

Repository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif

Score: 15.872936

API / Data Types / Repository

Repository Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents y

Score: 15.858789

API / Tree

Tree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl

Score: 13.66618

Docker / Configuration / API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is

Score: 12.009474

Deployment / Deployment Handlers / Branch Deployment Handler

Branch Deployment Handler Handles the deployment of one or more Deployment Packages to a Branch on the current platform. The contents of the Deployment Packages will be deployed transactionally to the target Branch. If any of the content within the Deployment Packages fails to copy, the transaction will be rolled back and the target Branch will be restored to its previous state. Configuration { "branchRef": "{branchReference}" } Where branchReference looks like branch://{platformId}/{reposit

Score: 11.261848

Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Score: 11.048869

Application Server / URL Addressability / Node URLs

Node URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye

Score: 9.022584

API / Data Types / Changeset

Changeset Type changeset Datastore Type repository Supports authorities, permissions, transfer In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the branch ends). Everything in-between constitutes the changeset history of the branch. This portion of the API therefore is largely for advanced users. The Cloud CMS API lets you dig in and poke around at the changeset history of branches to do things like

Score: 8.842393

General / Auditing

Auditing Cloud CMS provides a built-in audit system that track interactions between users and content objects within your content repository. The audit system produces an audit trail consisting of audit records that document the interaction between a particular user, a content object and a service. Audit records are created automatically if they are enabled for your tenant and for the repository against which the operation occurs. Enabling Auditing To enable audit records, the tenant for the cur

Score: 7.9505305

Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto

Score: 7.339958

User Interface / Projects / Deleted Items

Deleted Items Cloud CMS provides a "copy on write" mechanism for any creates, updates or deletes to the content in a branch. This means that whenever you delete something, you're actually masking it as deleted. The content itself is never destroyed or removed permanently. As such, it is always possible walk backwards in time and discover content that was deleted - all the way back to the moment when your branch or repository was created. To make things easier, Cloud CMS provides a "deletions" in

Score: 7.031745

API / Data Types / Node

Node Type node Datastore Type repository Supports authorities, permissions, transfer Configuration The node configuration contains system and custom properties. You can write your own properties as you see fit. However, system properties should be left alone as they are read-only. The following table presents you the system properties. Node Properties Property Type Default Read-Only Description _features object Read-Only This object contains all of the configuration for features which have been

Score: 6.9251814

Actions / Move Node

Move Node ID: moveNode Moves a source association into a new location in the content graph. The association is unlinked from its source node and linked to the target parent node. The association type and properties are preserved. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source association. branchId text true The ID of the branch of the source association. nodeId text true The ID of the source association. targetRepositoryId t

Score: 6.600614

Actions / Copy Multiple Nodes

Copy Multiple Nodes ID: copyMultipleNodes Copies multiple nodes and any of their owned children to a new location in the content graph. 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. nodeIds array true An array of node IDs to be copied (soure nodes) targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID

Score: 6.520594

Actions / Copy Node

Copy Node ID: copyNode Makes a copy of a node and any of its owned children to a new location in the content graph. 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 of the source node. targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID of the branch of the target parent node. t

Score: 6.520594

Chaining vs. Promises

The Cloud CMS JavaScript driver provides it's own internal chaining library that makes it easier to manage callbacks in asynchronous JS applications. The chaining library is powerful and bears some similarity to modern promise libraries. But it is important to bear in mind that it is distinct apart from having some similar method signatures. One similarity in structure in that both promises and chaining have a then() method to resolve the callback. However, the chaining library's chained methods

Score: 6.5039587

How to unpublish content

Cloud CMS provides a range of options for making content available to your presentation tier. The most common scenarios are: 1) Use an attribute on your Type Quick and easy to implement. Just add an attribute to mark instances as published by defining within the type's JSON: “published”: {  "type": "boolean",  "title": "Published?”  } You can then filter out items where this value is False. 2) Create a Feature for consistency Of course, if you have several content Types, you'll want to avoid re

Score: 6.5022674

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

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

Workflow / Workflow Handlers / Copy Node

Copy Node Type: copyNode This handler copies nodes that are part of a workflow's payload to a target folder. The target folder can be identified either by a node ID or a node path. The config for this handler is as follows: { "targetNodeId": "", "targetOffsetPath": "" } If targetOffsetPath is specified, then targetNodeId is the root node to calculate the offset against. If targetNodeId is not provided, the default repository root is used. Here is an example w

Score: 6.448547