Found 25 results for "docker docker maintenance docker maintenance compression"

The search executed in 0.001 seconds

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

Docker / Maintenance

Maintenance Repository Compression Health Check / Load Balancers Upgrades

Score: 53.544838

Application Server / Installation / Docker Installation

Docker Installation The Cloud CMS Application Server is additionally provided as a Docker image. With Docker, you can launch this image within its own container running on Linux, Mac OS or Windows. The container can be managed, brought online and shutdown at any time. Docker To get started, you will need to familiarize yourself with Docker. Install Docker onto your operating system and become familiar with the command line tools. Git You will also need to be familiar with Git. The source for the

Score: 46.14126

Cloud CMS Docker images

Cloud CMS is available as a set of Docker images so that you can run it on your own. This includes running it on-premise within your own data center as well as running it on Amazon AWS, Rackspace, IBM Bluemix or a variety of other Docker Container hosting platforms. Cloud CMS distributes its Docker images via Docker Hub. These are private images that are not generally available. Rather, Cloud CMS subscribers are granted permission to pull down the images once they've signed up for a Cloud CMS Do

Score: 18.66098

Docker / Maintenance / Repository Compression

Repository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif

Score: 18.505318

Docker / Maintenance / Upgrades

Upgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's

Score: 18.137856

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

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

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

Docker / UI Extensions

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

Score: 15.205678

Application Server / Installation

Installation Docker Installation Module Installation Standalone Installation

Score: 15.045679

Recommended environment

This is a big subject and, as you know, there are many ways to set things up to be robust. That said, some practices are better than others. I can relate at least what we do and what we've seen customers do. First, I'd recommend thinking of Cloud CMS as black box application that runs on top of MongoDB, Elastic Search (both of which can be thought of as databases) and a binary storage provider. Cloud CMS is a stateless application whose setup is actually quite simple. It doesn't maintain any sta

Score: 14.720835

How does multi-tenancy work?

How does multi-tenancy work? ie I want to have multiple companies with sub-groups of users in each company - to follow, how would we customize the interface for each company? There are two good ways to achieve multi-tenancy with Cloud CMS. - One is to use multiple "projects" - i.e. one per customer. Each project has it's own domain of users and groups, as well as it's own content definitions, instances and ACLs. As such, you can use each project to store the content on a per-client basis. You ca

Score: 13.896489

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

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

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

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 th

Score: 11.435582

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

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

How does Cloud CMS work with a CDN

There are a few places where this either occurs automatically if you're using our hosted service or can occur optionally if you're either running within Docker containers on your own or integrating to custom CDN endpoints. First, the API itself can be fronted by a CDN that supports fallback lookup to an origin server. In this case, we recommend Amazon CloudFront with short-lived TTLs on cache headers. More specifically, you can use Amazon's API Gateway to get caching coverage across multiple geo

Score: 9.637091

Application Server

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.

Score: 9.028546

Files / Binaries

Binaries Cloud CMS supports the storage of binary files into one of three possible storage locations: MongoDB GridFS Amazon S3 Local file system Binary files are stored using directory structures (key prefixes) that allow for fast object retrieval from any of these systems. These storage paths are optimized for retrieval and write speed and are subject to implementation changes. The actual API retrieval of these files, on the other hand, utilizes a simple filename convention. You simply retrieve

Score: 9.028546

Features / Thumbnailable

Thumbnailable QName: f:thumbnailable Configures a node to automatically generate thumbnails for the node content or attachments. With this feature applied, one or more thumbnail images will be generated based on the node's JSON or attachment content. These thumbnails can be of various sizes and are automatically generated when the node's content is created, updated or deleted or its relevant attachment is updated. Thumbnail generation is always synchronous. Thumbnails are generated when the node

Score: 8.892232

Actions / Add Feature

Add Feature ID: addFeature Adds a feature to a node. The configuration for this feature is described using JSON Schema like this: { "title": "Add Feature", "properties": { "qname": { "title": "Feature QName", "type": "string" }, "config": { "title": "Feature Configuration", "type": "object" } } } See the examples below for more detail. Example #1 Let's say we want to automatically configure the filename

Score: 7.677965

Application Server / Authentication

Authentication The Authentication Service provides a full authentication framework for stateless and session-based applications. It authenticates requests against back end providers and offers interpretation and parsing of request scope information to provide Single-Sign-On (SSO). Authenticated requests will have user accounts created and synchronized within Cloud CMS either automatically or as part of a registration form process. Authenticated users have Cloud CMS connectivity state managed for

Score: 4.398129