Search Results

API / Deployment / Channel

Channel Channel is the receiver branch to which you want to publish the live content. Channel can be any branch of a project on the Cloud CMS server. Right now, Channel is a branch of a project on the Cloud CMS server, but can be extended to be a file system or S3 bucket. For the publishing feature, it is nothing but a location to upload or publish the live content. Following are the steps to create a Channel: Click on Manage Platform > Channels Click on Create Channel Title - "Deploy to Live We

Score: 20.117935

API / Deployment / Deployment Strategy

Deployment Strategy Deployment Strategy holds all the information of the deployment. For example, what is the Source and Destination, when the deployment will happen etc. As soon as the deployment target is created and the project is enable to publish the content, a Deployment Strategy is automatically created. It holds the strategy of the deployment right from the source branch to the deployment target. Following are the details of the information: Title : This shows the title of the strategy.

Score: 20.117935

API / Deployment / Deployment Target

Deployment Target Deployment Target points to a place for publishing the content. It can be a Channel, a S3 Bucket or any File System Publishing to a channel : To publish the content to a Channel, select 'Channel' from the options while Creating a Deployment Target. Following are the steps to create a Deployment Target: Click on Manage Platform > Deployment Targets Click on Create Deployment Target Title : "Live Web Site" Type : "Channel" Channel : Select the channel where you want to deploy the

Score: 20.117935

API / Controls / Node Picker

Node Picker ID: node-picker The node-picker field type renders a modal picker for a node. The modal picker allows you to filter nodes as well as paginate, sort and inspect nodes. The picker supports single node and multi-node selection depending on how the field is configured. Sample configuration: { "type": "node-picker" } The node picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the latter is used for selectio

Score: 18.900984

API / Controls / File Picker

File Picker ID: file-picker The file-picker field type renders a modal picker for a file. This uses the File Folder service within Cloud CMS to let you browse through folder-based navigation. A breadcrumb is rendered at the top to help users step through the folder hierarchy. Sample configuration: { "type": "file-picker" } As with the node picker, the file picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the lat

Score: 18.84377

API / Controls / Related Content

Related Content ID: related-content The related-content field type renders a n upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simi

Score: 17.396414

Docker Guide / Getting Started / Overview

Overview 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 en

Score: 16.331001

Recommended environment

This is a big subject and, as you know, there are many ways to set things up to be robust. That said, some practices are better than others. I can relate at least what we do and what we've seen customers do. First, I'd recommend thinking of Cloud CMS as black box application that runs on top of MongoDB, Elastic Search (both of which can be thought of as databases) and a binary storage provider. Cloud CMS is a stateless application whose setup is actually quite simple. It doesn't maintain any sta

Score: 10.803404

Docker Guide / 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: 9.219333

Docker Guide / User Interface / Extensions

Extensions The Docker-based Cloud CMS UI provides additional extension patterns beyond the AMD-driven mechanism for user interface components and screens. Since Docker allows you to run on-premise, you can use these extension patterns to influence more foundational changes to the way the application works. Environment Variables When the Cloud CMS user interface starts up, it looks to environment variables to tell it whether there are any extensions available to be loaded. Extensions are stored w

Score: 9.170706