Application Server 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.

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

Clustering The Cloud CMS Application Server supports running on a single Node process as well as multiple Node processes. Node processes can run on a single server instance or can be spread across multiple server instances behind a load balancer. By default, the Application Server starts up and allocates itself to a single CPU. This is known as single mode. Even if you have a server with more than one CPU on it, the Application Server will still only bind to 1 of those CPUs. When the Application

Public Services Cloud CMS provides a special set of application services methods that provide convenience functions for your front-end mobile or web applications to accomplish things like user registration, password resets and more. Technically speaking, everything that you can do with these convenience functions can be done using the Cloud CMS API in other ways, however doing so is often multi-step and involves lots of interactions. The convenience methods make this easier by letting you pre-wi

Our definitions are based on JSON schema and, as such, the default is to use strings for dates. The date controls in our forms engine let you customize the format string so that you can store ISO 8601 or other formats (perhaps simplified formats) as per your preference. The advantage here is simplicity with these controls and compatibility with JSON schema. The disadvantage is that MongoDB provides a lot of very powerful capabilities for range query and sorting that do not play as nicely with th

Geolocation Services Cloud CMS provides geolocation information look up services that can be used to determine geographic information for a given IP address or set of coordinates. In many places, Cloud CMS automatically utilizes these geolocation services for you. In places where geolocation information is stored on your content instances, geolocation data can automatically be looked up and applied using Cloud CMS features. In addition, you can invoke the API directly to look up geolocation info

Welcome The welcome service allows you to configure a default URI path for any requests that do not have a path supplied. Configuration {
"welcome": {
"enabled": ,
"file": ""
}
} Example #1 For example, you may wish for users who access your website at: http://mywebsite.com/ To be served back the page at: http://mywebsite.com/index.html This is accomplished using a config block like this: {
"welcome": {
"enabled": true,
"file": "inde

Yes, Cloud CMS supports SSO (Single Sign On) with a variety of authentication providers. Many of these providers are offered out-of-the-box -- including providers for Keycloak, Google, CAS and more. In addition, we allow you to implement your own SSO providers and customize the authentication handshake. To learn more about how Cloud CMS authentication providers work, check out the following documentation: https://www.cloudcms.com/documentation/appserver/services/auth.html Custom Authenticators a

@form A form can be rendered from Cloud CMS by identifying the definition and form key. Forms are rendered on the client-side using Alpaca Forms. For a working example, see: https://github.com/gitana/sdk/tree/master/appserver-form-sample Parameters parameter required description definition yes the type definition QName form yes the form key list no the data list to populate successUrl no the URL to redirect to upon success failureUrl no the URL to redirect to upon failure formId no override the

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

Setting up your Email Provider The public application services often need to send emails as part of their respective flows. To do this, a public email provider must be configured for the application. This is email provider that the public services will use when dispatching emails as part of a public flow. On this page, we cover a few convenience methods that are available to test your email provider as well as send emails straight away. This page assumes that you are already familiar with email

Integrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser

Registration Flow One of the more frequent flows that an application must achieve is that of registering a user. Cloud CMS already provides registration support. The application service convenience method shown below make it a little easier to register users for your web application by letting you predefine: The Custom Domain Name where new users will be created. The Email Provider to be used to send emails to new users. The Registrar where new tenants will be created (optional). The Domain User

Plugins Cloud CMS plugins let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Plugins provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associations an

Cloud CMS maintains two indexes that are of interest for finding things. The primary index is the MongoDB index - against which you can run any query you can dream up using the MongoDB DSL. The secondary index is the Elastic Search index - against which you can run any search you can dream up using the Elastic Search DSL. For information all kinds of really powerful stuff you can do with this, see: https://www.cloudcms.com/documentation/content-services/query.html https://www.cloudcms.com/docume

UI 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 store

At present, Cloud CMS can be configured to publish notifications to Amazon SNS. Thus, to take advantage of this, you'd have to first have an Amazon Web Services account and an SNS topic created. Cloud CMS publishes notifications to it. Your topic can then do anything it wants with these notifications. Your cluster can listen for these events and process messages to invalidate cache. Most commonly, people hook the SNS services to the SQS service for queue-based event management. We've chosen this

A Project is a logical separation for work within Cloud CMS. It could be a site, a sub-site, a department, a web project or anything else you'd like. Projects let you organize teams, invite members and provide a place for you to collaborate on content. An Application is something that you create to provision resources and services dedicated to your web site or web/mobile application. Each Application provides storage and services that your app can access for things like user registration, passwo

Cloud CMS provides implementation services to help build your iOS, Android or HTML5 application and connect it to Cloud CMS for dynamic content delivery. As experts in both the front-end and back-end technologies, we provide quality work and deliver on schedule. For a quote, please contact us and tell us about your project.

Transcoders Cloud based services for transcoding files can be integrated with Cloud CMS. This allows files associated with content but stored remotely to be transcoded, i.e. changing the file type or resolution of a video file. Pre-requisites Transcoding requires that you have a cloud storage provider configured and that you also subscribe to the associated transcoding product. Usage Transcoding can be implemented with the follow: Transcode Action Transcodable Feature Available Transcoders Amazo