Found 154 results for "api api deployment overview"

The search executed in 0.001 seconds

API Keys

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

Score: 67.08476

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

Getting Started

Getting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa

Score: 31.84287

Deployment

Deployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may

Score: 26.719437

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

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

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

Application Server / Services / Overview

Overview For more information on configuration of the Cloud CMS application server, please visit Cloud CMS App Server on GitHub. { "name": "Cloud CMS Application Server", "setup": "single", // single, cluster, sticky-cluster "socketFunctions": [], "routeFunctions": [], "configureFunctions": {}, "beforeFunctions": [], "afterFunctions": [], "viewEngine": "handlebars", "storeEngines": { "app": { "type": "fs", "config": {

Score: 18.26513

Deployment / Deployment Receivers

Deployment Receivers A Deployment Receiver acts as an endpoint for local and remote Deployment Handlers that seek to ship their Deployment Packages to a destination. These are frequently used to move content between data centers or across different parts of the world to solve for latency issues (or to simply move content to the correct side of a DMZ for security reasons or runtime-performance reasons). Cloud CMS lets you create Deployment Receivers from within its user interface. You can create

Score: 17.820164

Publishing

Publishing Content Types Example Publishing Setup Lifecycle States Preview Servers Publications Workflow

Score: 17.239367

Deployment / Deployment Handlers

Deployment Handlers A Deployment Handler provides the deployment implementation for a Deployment Target. When Deployment Packages are routed to a Deployment Target, the Deployment Target's "handler" is instantiated to handle the actual connectivity, copy and delivery of the Deployment Package's content. The following Deployment Handlers are available: Branch Deployment Handler File System Deployment Handler FTP Deployment Handler HTTP Deployment Handler Local Deployment Handler Remote Deployment

Score: 15.940813

Deployment / Deployment Handlers / Remote Deployment Handler

Remote Deployment Handler Handles the deployment of one or more Deployment Packages to a remote Deployment Receiver. Where: url is the URL of the target Cloud CMS API server receiverId is the ID of the receiver on the target Cloud CMS API server In addition, you should provide the API keys of the user who the Remote Deployment Handler will authenticate as. clientKey clientSecret username password Configuration { "url": "{url}", "clientKey": "{clientKey}", "clientSecret": "{clientSecr

Score: 14.986839

Deployment / Deployment Target

Deployment Target A Deployment Target contains the configuration for a Deployment Handler. It informs the handler about how to connect or what settings should be used when executing. Deployment Targets are configured for Deployment Strategies as well as for Deployment Receivers. When content is changed within Cloud CMS, a Deployment Strategy may decide to package up that modified content and deployment it to one or more Deployment Targets. Similarly, content may be deployed to a Deployment Recei

Score: 14.681667

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

Deployment / Deployment Handlers / Local Deployment Handler

Local Deployment Handler Handles the deployment of one or more Deployment Packages to a local Deployment Receiver. The deployment receiver must exist on the same Cloud CMS platform. It is identified by the receiverId property. The Deployment Packages will be handed to the Deployment Receiver and then processed from there. The Deployment Receiver may elect to pass those Deployment Packages down to its own configured targets or process them through additional rules priorty to delivery. Configurati

Score: 10.370663

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

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

Deployment / Deployment Handlers / FTP Deployment Handler

FTP Deployment Handler Handles the deployment of one or more Deployment Packages to an SFTP or FTP server. The remote S/FTP server is described by a URL, username and password. 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. Nodes are written to disk like this: {deploymentPath}/{nodeId}/node.json No

Score: 10.108525

Deployment / Deployment Handlers / Amazon S3 Deployment Handler

Amazon S3 Deployment Handler Handles the deployment of one or more Deployment Packages to an Amazon S3 bucket. The Amazon S3 bucket is described by: accessKey secretKey region bucketName 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. Nodes are written to disk like this: {deploymentPath}/{nodeId}/no

Score: 9.334902

Deployment / Deployment Handlers / File System Deployment Handler

File System Deployment Handler Handles the deployment of one or more Deployment Packages to a file system. A file system is described by a local path on disk, such as: /www/files /data /Users/joesmith/files These paths, in turn, my describe mounts that are ephemeral or non-ephemeral (such as Amazon EBS mounted drives or shared network storage). The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails

Score: 9.316902

Publishing / Example Publishing Setup

Example Publishing Setup Following are the steps to config a typical Publishing setup: Step 1: Create Projects Create two projects one for the Authoring and another to handle contents published as Live, Create an "Authoring" project Create a "Live" Project Step 2 : Create a Deployment Target Deployment Target is the endpoint where the package will be deployed or sent. Go to Manage Platform Go to Deployment Targets under Deployment Left Navigation Menu Click on Create a Deployment Target Title :

Score: 8.756189

How does Cloud CMS compare to Prismic.io?

Not sure which CMS is a better fit? Review these points to help guide your selection. Criteria Cloud CMS Prismic.io Ease of Use Implements a role-based UI to accommodate various functions. Complex user interface for defining content types and instances. Item creation must occur here. See API Access. Update Strategy Documents are published individually, or as part of larger change sets. Documents are published individually, or as part of larger change sets. Workflow Process Flexible workflow capa

Score: 8.38909

How does Cloud CMS compare to Contentful?

Not sure which CMS is a better fit? Review these points to help guide your selection. Criteria Cloud CMS Contentful Ease of Use Implements a role-based UI to accommodate various functions. Simple user interface for defining content types and instances. Update Strategy Documents are published individually, or as part of larger change sets. Documents are published one-by-one. Workflow Process Flexible workflow capability. Allows teams and roles to be created along with a workflow designer for defi

Score: 8.333536

Cloud CMS Architecture

Cloud CMS has two clusters that we run for customers who host apps with us. One cluster is for the "app server" tier (*.cloudcms.net) and the other is the "API" tier (api.cloudcms.com). The app server cluster consists of Node.js servers, and the API is a Java-backend that is stateless and implements the full REST API: As such, the API doesn't manage connections directly. Any invocation to it is a one-shot where each request contains everything needed to assert the user's identity and proceed wit

Score: 8.105879

User Interface / Multilingual

Multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i

Score: 7.429704