Search Results

Amazon SQS


Score: 25.188868

Amazon SNS


Score: 22.566292

Node Lifecycle Events

First, you configure your tenant with the AWS credentials of an IAM user and a SNS topic ARN that you wish to publish notification events to. This can be on your own AWS account so that you can work with these notifications any way you'd like.

The notifications are for a variety of node lifecycle events. The primary one is "node_invalidation" which happens whenever a node's state changes. It's an indication that anyone caching anything downstream might want to reconsider their cache

Score: 20.161047

Cache invalidation via SNS

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 c

Score: 18.888987

Notifications

Notifications { "notifications": { "enabled": false, "type": "sqs", "configuration": { "queue": "", "accessKey": "", "secretKey": "", "region": "" } } }

Score: 12.172954

Overview

Overview Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team

Score: 10.3081455

Overview

Overview Releases, also referred to as branches, allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls

Score: 10.3081455

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

Amazon Route 53

Amazon Route 53 Amazon Route 53 is a highly available and scalable cloud Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost effective way to route end users to Internet applications by translating names like www.example.com into the numeric IP addresses like 192.0.2.1 that computers use to connect to each other. Cloud CMS integrates with Route 53 to dynamically provision domain names for deployed applications.

Score: 8.054241

Definitions for Date format

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

Score: 6.553939