Search Results

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, see our documentation on the general Authentication / SSO framework. API Keys You will need to configure a LinkedIn application and have the following information

Score: 7.062241

Application Server / Getting Started / Overview

Overview The Cloud CMS Application Server offers an easy way for customers to assemble powerful, front-end custom APIs and web sites for Cloud CMS. It is completely free and runs on top of the popular Node.js technology stack. With Cloud CMS, customers have a choice of using any front-end presentation technology they wish. In many cases, customers already have a technology investment (such as C#, PHP, Java or Ruby) and thus a preference for continuing to build on that technology stack. However,

Score: 4.6925526

Application Server / Services / Duster

Duster The Duster Service provides template rendering using the LinkedIn Dust.js template engine. The Duster Service loads output templates for you, executes Dust across them and outputs markup like HTML and JSON. It allows you to build full web sites or custom APIs using a powerful template engine. Tags The Cloud CMS Application Server provides a library of * Dust Tags available out of the box. These are listed in more detail on the left-hand side menu. Fragment Caching Some Dust tags support c

Score: 4.3162355

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

Advanced Content Modeling options (example)

Question. If I have the following collections: Categories Products Product_Description_Schemas Each Product is linked to a Category. Each Category is linked to a Product_Description_Schema. The outcome I want to accomplish is that the description schema for Product X I am entering, is defined by the Category it is linked to ( which in turn is defined by the Product_Description_Schema that the Category is linked to ). e.g. Product = Hilton Hotel London, Category = Hotel, Product_Description_Schem

Score: 4.017013

API / Features / Container

Container QName: f:container Makes a node as a container. In Cloud CMS, all nodes are essentially equivalent. There is no assumed containment model - in other words, Cloud CMS does not assume a folder structure or any kind of graph that you must adhere to. You can use associations to model any kind of relationship you would like. For example, you might have nodes that maintain only a kind of "linked" relationship to do things like link together related items for a product catalog. Another exampl

Score: 3.4199572

API / 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: 3.2854457

API / Workflow Handlers / Sync Node

Sync Node Type: syncNode This handler "syncs" nodes that are part of a workflow's payload to a target branch. This handler can be used to have workflow payload nodes automatically copied to or deleted from a target branch. The full config for this handler is as follows: { "targetProjectId": "", "targetRepositoryId": "", "targetBranchId": "", "includeAllAssociations": , "delete": } Examples Sync nodes to another branch in

Score: 2.9155989

API / 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: 2.8774903

API / 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: 2.8774903