Found 111 results for "docker notices cve-2021-44228"

The search executed in 0.001500522 seconds. That's fast.

Gitana / 4.0 / Data Engine / Integrations / Docker

Docker Cloud CMS ships its on-premise offering using Docker. Docker provides a way to package up the architectural tiers of Cloud CMS into services that can easily be deployed in all kinds of interesting configurations. It greatly reduced the heavy Dev/Ops and IT cycle involved with running a cloud infrastructure service. With Docker, our customers can easily and efficiently run Cloud CMS on-premise, in their own data centers and even on their own laptops. Cloud CMS services running in Docker ar

Score: 24.739264

Gitana / 3.2 / Guide / Guide / 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: 22.17003

Gitana / 3.2 / Guide / Guide / Docker / Security Notices

Security Notices Please review the following notices for information on mitigating known vulnerabilities and our recommended upgrade paths: CVE-2021-44228 CVE-2022-22965

Score: 16.400015

Gitana / 3.2 / Guide / Guide / Integrations / Docker

Docker Cloud CMS ships its on-premise offering using Docker. Docker provides a way to package up the architectural tiers of Cloud CMS into services that can easily be deployed in all kinds of interesting configurations. It greatly reduced the heavy Dev/Ops and IT cycle involved with running a cloud infrastructure service. With Docker, our customers can easily and efficiently run Cloud CMS on-premise, in their own data centers and even on their own laptops. Cloud CMS services running in Docker ar

Score: 14.72628

Gitana / 4.0 / Self Managed / Docker / Overview

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

Gitana / 4.0 / Self Managed / 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: 12.998567

Gitana / 4.0 / Self Managed / Overview

Self-Managed Gitana offers the option to run development and production installations of its software on-premise or within a virtual private cloud. Getting Started To get started with Gitana Self-Managed, please check out the following: Configuration Docker Kits Kubernetes Maintenance Monitoring Supported Stacks UI Extensions

Score: 12.984586

Gitana / 4.0 / Self Managed / 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: 12.905646

Gitana / 4.0 / Self Managed / Monitoring / Overview

Monitoring API Server with an APM The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. As such, Application Performance Montioring (APM) frameworks such as New Relic can be used to monitor performance metrics and other run-time data. Production Performance Although APM frameworks are designed such that they do not impact production performance more than is necessary, the impact is not zero. Cloud CMS Support may, therefore, ask you to disable monitorin

Score: 10.621506

Gitana / 3.2 / Guide / Guide / 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: 7.545323

Gitana / 4.0 / Developers / 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: 7.545323

Gitana / 3.2 / Guide / Guide / 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: 5.8205338

Gitana / 3.2 / Guide / Guide / 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: 5.4811344

Gitana / 3.2 / Guide / Guide / Docker / Upgrades

Upgrades The following notes are available to help guide upgrades for on-premise installations of Cloud CMS. 3.2.73 3.2.74 3.2.75 3.2.76 3.2.77 3.2.78 3.2.79 3.2.80 3.2.81 3.2.82 3.2.83 3.2.84 3.2.85 3.2.86

Score: 4.307395

Gitana / 3.2 / Guide / Guide / Docker / Monitoring API Server with an APM

Monitoring API Server with an APM The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. As such, Application Performance Montioring (APM) frameworks such as New Relic can be used to monitor performance metrics and other run-time data. Production Performance Although APM frameworks are designed such that they do not impact production performance more than is necessary, the impact is not zero. Cloud CMS Support may, therefore, ask you to disable monitorin

Score: 3.8104842

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

Gitana / 3.2 / Guide / Guide / 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: 2.527136

Gitana / 4.0 / Self Managed / 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: 2.527136

Gitana / 3.2 / Guide / Guide / 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 acc

Score: 2.511725

Gitana / 4.0 / Self Managed / 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 acc

Score: 2.511725

Gitana / 3.2 / Guide / Guide / Docker / Kits / MongoDB Replica Set

MongoDB Replica Set The MongoDB Replica Set kit defines an environment with a 3 node MongoDB replica set and two Cloud CMS environments running against it The configuration files for this kit can be found in the Gitana SDK Running Start the mongo servers first and then initialize the cluster: docker login --username {docker-username} --password '{docker-password}' docker-compose up -d mongodb1 mongodb2 mongodb3 Initialize the replic set. only have to do this once since the mongo servers persist

Score: 2.5024076

More Ways to Run Cloud CMS On-Premise

We just released Cloud CMS version 3.1.315 which includes more sample configurations to help customers and prospects get started with on-premise Docker deployments. Our Docker distribution includes several “kits” that contain pre-built Docker Compose configurations that help customers to get up and running right away. These configurations can either be used as is or they may serve as a reference for building out new configurations that meet a customer’s exact needs. Cloud CMS offers Docker as an

Score: 2.5017655

Gitana / 3.2 / Guide / Guide / 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.4510612

Gitana / 4.0 / Self Managed / 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.4510612

How we use Docker at Cloud CMS

At Cloud CMS, we use Docker to provision our cloud infrastructure servers on top of Amazon Web Services. Our stack consists of five different clusters: Cloud CMS API Cloud CMS UI Cloud CMS App Server for Dynamic Hosting Elastic Search MongoDB With the exception of MongoDB, all of these clusters are allocated using elastic load balancing and are architected in such a way that we can spin up new servers and tear down old ones with elastic demand. That is to say, they are fully elastic in design. T

Score: 2.4508