Found 39 results for "docker docker overview overview"

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

Getting Started

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

Score: 55.46042

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

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

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

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

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

Modules / Create a Module / Bindings / Type Pages

Type Pages The type-pages key lets you define routes that serve as landing pages for entity types. Specific pages within Cloud CMS serve as landing pages for an entity that is being viewed. Type Page configurations allow you to specify which URI should be dispatched to when viewing. Each type page has a very simple binding like this: { "uri": "{uri}" } Example - Dispatching a Workflow Task to the Overview Page { "evaluator": "entity-is-type", "condition": "Gitana.WorkflowTask", "

Score: 11.911621

User Interface / Workflow / Your Task Dashboards

Your Task Dashboards Tasks assigned to you in a Workflow process can be seen in your Platform Dashboard, Project Dashboard, or an email may have been sent to you with the Task link Platform Dashboard - Tasks asigned to you for all Projects will be listed Project Dashboard - Tasks asigned to you for the Project only will be listed Task Overview If you click on a task, or open the Task link in the email, the Task Overview page is opened - From here you can perform the following actions on the task

Score: 11.857308

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

User Interface / Workflow / View/Create a Workflow Model

View/Create a Workflow Model Switch to Platform level Click 'Workflow Models' (left Nav). Note: You will need to have admin or owner permissions to see the Workflow options. If you select a Workflow model you can Deploy, Undeploy, delete a Workflow model View/Edit Workflow Model Click on the Workflow name, eg Adhoc Approval, to view the Workflow Model To view/edit the Workflow click JSON Manage Active Workflow To see active instances of the workflow model click on Workflow option Note: you can s

Score: 11.593004

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

User Interface / Create/Edit Content

Create/Edit Content In a Project you can find your content a number of ways: Content (left Nav) - Content listed under Content Types Folders (left Nav) - Folder/File view of the content Search (left Nav for a detailed search or top right for a keyword search) Viewing a Content item With any of the options above, to find or list the content, click on the 'title' of the content item to open the 'Document Overview': Note: your tenant may be configured such that the options available in the left nav

Score: 11.330156

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

Application Server / Services

Services Awareness Broadcast Cache Config Driver Config Duster Flow Insight Local Notifications Overview Performance Server Tags Virtual Driver Virtual Hosts Web Content Management Welcome

Score: 10.781278

User Interface / Workflow / View Active/Inactive Workflow

View Active/Inactive Workflow You can view both the Active and Inactive workflow from the Platform and Project levels. The Platform level will show all workflow for all Projects and at Project level it will show all workflow for that Project. Click Workfow Title to open the Workflow Overview page

Score: 10.477214

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

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

Application Server / Installation

Installation Docker Installation Module Installation Standalone Installation

Score: 9.652139

User Interface / Favorites

Favorites Cloud CMS allows users to add documents to Favorites. Add to Favorites To add to favorites, click "Add to Favorites" under "Document Actions" in a Document Overview page. Remove from Favorites To remove from favorites, click "Remove from Favorites". Manage All Favorite Documents Navigate to "Manage Favorites" from your account drop-down menu and view all of your personal favorite documents. You can, for instance, remove selected items from Favorites (this action only removes the docume

Score: 9.53592

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

User Interface / Tags

Tags Cloud CMS lets you manage your tag hierarchy and assign those tags to your content. Content that is tagged is automatically marked with the tag information (within the tags property) and will also maintain an a:has_tag association in the content graph that points back to the tag instance. Tags are first class citizens within Cloud CMS. They are content like everything else. Once content is tagged, you will see it reflected in the user interface as such. You will be able to navigate your con

Score: 9.019573

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

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

User Interface / Multilingual

Multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i

Score: 8.545345