Found 133 results for "api api content-services api content-services tree"

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

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

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

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

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

How can I retrieve content for a tree view?

The Cloud CMS API offers a number of convenience API methods that go beyond basic CRUD and bulk content operations. Among these methods are those that allow you to retrieve content from your repository branch in a tree-friendly format. A tree-organized format means that the data comes back in a such a way as to make it easy to load into front-end tree controls. Typical front-end tree controls requires the ability to load a "snapshot" of the tree as a starting point as well as iteratively grow or

Score: 12.172185

Tree Hierarchies

In Cloud CMS, there are no hard and fast rules regarding association types between nodes. And so, when dealing with things like tree structures, you usually have to first make some assumptions about the kinds of relationships between nodes that you want to traverse. For arbitrary relationships and traversals around nodes, Cloud CMS provides traversal methods which are a bit more intensive to use. However, if you're using typical a:child relationships between nodes (which is what Cloud CMS uses f

Score: 12.036247

How to Retrieve content by their document library path

You can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call: http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo

Score: 11.560316

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

Docker / Kits / OEM

OEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To acces

Score: 8.143797

Application Server / Authentication / Providers / LinkedIn

LinkedIn Cloud CMS provides integrated authentication and single-sign-on (SSO) with LinkedIn. This page describes the authentication provider available for the Cloud CMS Application Server that enables your mobile or web applications as well as the Cloud CMS user interface or API to authenticate against LinkedIn. For more information on Authentication within the App Server, see App Server Authentication / SSO. LinkedIn API Keys You will need to configure a LinkedIn application and have the follo

Score: 7.9563684

API Max Heap recommendation

What is the recommended Xmx value for running the API service? The 2GB setting on the On-Premise "quickstart" distribution is a default for development usage. In production, we recommend putting as much memory as you can. Essentially, the API should use as much memory as is allocated to the API docker container. We usually ask customers to consider an M class large instance type (something on the order of 7.5GB of RAM per API). The UI can use considerably less. For the UI, a 2GB allocation is fi

Score: 7.843571

Docker / Kits / Quickstart

Quickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:

Score: 7.833477

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

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

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

Docker / Kits

Kits Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes the

Score: 7.5241194

Proxy API calls

Whenever a resulting URL looks something like: https://api.cloudcms.com/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes//attachments/thumb.jpg It works great as an API URL but not necessarily as one that can be resolved by the end user's browser. In a typical Node.js-based architecture, you have the User’s browser Node.js application server Cloud CMS backend API The URL generated above is the URL directly to the resource in the backend API. What you really would pre

Score: 7.4952364

Supporting large binary files

Cloud CMS offers a few different ways for you to store files - including storing them in S3 (recommended) or even on a local partition (such as an NFS mount). In our SaaS offering, everything is stored in S3 automatically and when you install on-premise, you can configure this to your preference. See this documentation page under Binary Storage: https://www.cloudcms.com/documentation/docker/configuration/api-server.html We definitely can handle large binary files in the 10's or 100's of megabyte

Score: 7.3969617

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

Docker

Docker 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 enca

Score: 7.33178

Traversal

Traversal Content in Cloud CMS is stored in a graph-like structure that consists of nodes and associations. Nodes are entities in the graph and associations are the relationships (the lines between points in the graph). As such, when working with content in Cloud CMS, you'll often find it useful to employ these structures in terms of your content model. Your content can be spread out between nodes and associations equally so that both the entities and the relationships hold JSON properties that

Score: 7.287973

Recommended Cloud CMS architecture

In general, we recommend a three-tier architecture (browser -> app server -> API) for any applications you build. This would be our recommendation whether you're using Cloud CMS or anyone else. There are a few good reasons: The browser is an insecure runtime. Exposing any API keys within the browser is a very big security hole. Even exposing credentials within the browser (such as within a cookie) for the sake of working around this is also not recommended since hackers can siphon off the creden

Score: 7.287716

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

Docker / Configuration / Encrypting Properties

Encrypting Properties Cloud CMS lets you encrypt properties within your API configuration files to protect sensitive passwords, secrets and credentials. This encryption utilizes a public and private key. The private key is supplied to the Cloud CMS API server and the public key is provided to developers to encrypt sensitive data. To help you do this, Cloud CMS provides a command line tool. gitana-tools-encryptor.jar The gitana-tools-encryptor.jar works with Java 8 and gives you commands that you

Score: 7.255427