Found 269 results for "api content-models overview"

The search executed in 6.95192E-4 seconds. That's fast.

Content Modeling / Scripts

Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: Association Policies function beforeAssociate(association)

Score: 2.5943553

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

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

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

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

Comparison: Cloud CMS vs Prismic

Not sure which CMS is a better fit? Review these points to help guide your selection. Criteria Cloud CMS Prismic 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 capabil

Score: 2.4856913

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

Docker / Configuration / UI Server

UI Server The Cloud CMS UI Server is a Node.js application that provides the editorial experience for Cloud CMS. It communicates with the Cloud CMS API via HTTP/HTTPS API calls and is built to be very extensible. Developers and system integrators can extend the Cloud CMS UI through the deployment of UI modules. Environment File (.env) The Cloud CMS UI is primarily configured via a series of environment variables. These environment variables are detected by the Node.js application at startup and

Score: 2.4291713

My UI modules aren't deploying. What should I check?

If you're running an on-premise installation of Cloud CMS and are unable to deploy UI modules via the main user interface, here are a few tips and pointers. Things to consider: 1. When you click on the "Deploy Module" option, your a URL connection is made from the UI server back to the API server. Specifically, it invokes a POST to the route: /oneteam/modules/deploy Check your API side logs or any firewalls or proxies along the way to make sure that an API server receives this call. For example,

Score: 2.422264

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

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

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

Comparison: Cloud CMS vs Contentful

Looking for the best CMS online? Review these points to help guide your headless CMS 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. Flexibility JSON schema with types and associations that you can continually evolve in-place. Basic content model only, difficult to change once configured Update Strategy Documents are published individually, or as part of larger change

Score: 2.3897336

REST based access calls

The authentication mechanism in Cloud CMS is OAuth 2.0. While you can use any of the flows, the easiest one to begin with is "password". We've outlined a basic example here using Advanced REST Client to show our API-first platform in action. First, from your Cloud CMS platform home page, navigate to "Manage Platform" and select the "API Keys" section to list all available projects for remote access: If you have no keys for your project then create a new "Application" from "Manage Platform" and t

Score: 2.3744457

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

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

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

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

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

Migrating Binary files to S3

By default, on-premise installations of Cloud CMS are configured with a GridFS (`gridfs`) Binary Storage Provider. This allows Cloud CMS to read and write binary files (such as attachments) to GridFS. At some point, as your installation grows, you may want change this. Suppose you wanted to move your binary files into S3 and use S3 as a Binary Storage Provider for Cloud CMS. To do so, we recommend the following steps: 1. Make a backup of your Cloud CMS database. 2. Create an S3 bucket and IAM us

Score: 2.3193758

Binary Files / File System Binary Storage

File System Binary Storage Cloud CMS supports store binary files to a direct file system volume or mount by by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually written down to the file system for persistence. When users seek to download those binary files, they are streamed back from disk. Depending on how you elect to configure your binary storage providers, Clou

Score: 2.3184383

Application Server / Authentication / Providers / GitHub

GitHub Cloud CMS provides integrated authentication and single-sign-on (SSO) with GitHub. 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 GitHub. For more information on Authentication within the App Server, see App Server Authentication / SSO. GitHub API Keys You will need to configure a GitHub application and have the following infor

Score: 2.3146977

Application Server / Authentication / Providers / Google

Google Cloud CMS provides integrated authentication and single-sign-on (SSO) with Google. 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 Google. For more information on Authentication within the App Server, see App Server Authentication / SSO. Google API Keys You will need to configure a Google application and have the following infor

Score: 2.3146977

Application Server / Authentication / Providers / Twitter

Twitter Cloud CMS provides integrated authentication and single-sign-on (SSO) with Twitter. 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 Twitter. For more information on Authentication within the App Server, see App Server Authentication / SSO. Twitter API Keys You will need to configure a Twitter application and have the following

Score: 2.3146977

Integrations / ActiveMQ

ActiveMQ ActiveMQ is a high performance Apache 2.0 licensed Message Broker and JMS 1.1 implementation. It provides a high performance and scalable implementation of an effective and popular message queue that lets you decouple your front end applications (and the Cloud CMS UI Server) from back end API notifications. You can use ActiveMQ to transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. Cloud CMS Application Ser

Score: 2.3018427