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

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

Gitana 3.2 / Guide / Guide / Docker / Kits

Download pre-built Cloud CMS Docker kits for common scenarios, ideal for quick setup or as a configuration reference. Explore our resources now.

Score: 2.2751803

Gitana 4.0 / Self Managed / Kits

Explore Cloud CMS Docker Kits for pre-built, user-friendly configurations to quickly deploy APIs, UI, and more with ease using Docker and Docker Compose.

Score: 2.2751803

Gitana 3.2 / Guide / Guide / Docker / Kits / API Cluster

Optimize API management with our API Cluster kit, featuring load balancing and efficient service distribution across api1 and api2 servers.

Score: 2.251549

Container Registry - Gitana

Container Registry - Gitana Status Releases Registry Blog Cloud CMS Platform Platform Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Automation Automate your content creation and approval flows while taking advantage of AI services to enhance and curate cont

Score: 2.2493024

Gitana 3.2 / Guide / Guide / Docker / UI Extensions

Enhance your Cloud CMS UI with Docker-based extensions, utilizing environment variables and custom configurations for tailored user experiences.

Score: 2.19499

Gitana 4.0 / Self Managed / UI Extensions

Enhance your Cloud CMS UI with Docker-based extensions, utilizing environment variables and custom configurations for tailored user experiences.

Score: 2.19499

Gitana 3.2 / Guide / Guide / Application Server / Installation

Learn how to set up your server with our comprehensive guides: Docker, Module, or Standalone Installation for Gitana 3.2.

Score: 2.1107817

Gitana 4.0 / Developers / Application Server / Installation

Explore Docker, Module, and Standalone installation guides for Gitana App Server. Step-by-step instructions for seamless setup.

Score: 2.1107817

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.79

Upgrade to Cloud CMS 3.2.79 with support for ARM-64, enhanced ElasticSearch integration, and Redis 6.x compatibility for improved performance.

Score: 2.0997221

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.80

Upgrade to Cloud CMS 3.2.80 for enhanced ARM-64 support, improved ElasticSearch integration, and Redis 6.x compatibility. Optimize your deployment now.

Score: 2.0997221

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.81

Upgrade to Cloud CMS 3.2.81 for ARM aarch64 support, new ElasticSearch client, Redis 6.x upgrade, and improved performance. Explore release notes now!

Score: 2.0997221

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.82

Upgrade to Cloud CMS 3.2.82 for ARM-64 support and enhanced performance. Optimize ElasticSearch connections with the Condor client and update Redis to 6.x+.

Score: 2.0997221

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.83

Upgrade to Cloud CMS 3.2.83 with improved ARM aarch64 support, ElasticSearch connection via condor, and Redis updates for better performance.

Score: 2.0997221

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

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.84

Upgrade to Cloud CMS 3.2.84 for ARM-64 support, enhanced performance, and Redis 6.x compatibility. Access release and upgrade notes for more details.

Score: 2.0551236

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.85

Upgrade to Cloud CMS 3.2.85 with ARM-64 support, enhanced performance, and Redis 6.x compatibility. Access detailed release and upgrade notes.

Score: 2.0551236

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.86

Upgrade to Cloud CMS 3.2.86 for ARM-64 support, improved performance, and compatibility with Redis 6.x. Follow release notes and upgrade tools for guidance.

Score: 2.0551236

Gitana 3.2 / Guide / Guide / Docker / Container Services / Kubernetes

Kubernetes: Automate deployment, scaling & management of containers on cloud platforms like Amazon, Google, Azure with open-source Kubernetes & Gitana SDK.

Score: 2.0527842

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.87

Upgrade to Cloud CMS 3.2.87 for enhanced ARM-64 support, requiring MongoDB 4.0+ and Redis 6.x+. Optimize deployments with AWS Graviton.

Score: 2.0256703

Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.88

Upgrade to Cloud CMS 3.2.88! Enjoy ARM aarch64 support with better performance and lower costs. Requires MongoDB 4.0+ and Redis 6.x+.

Score: 2.0256703

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

Gitana 3.2 / Guide / Guide

Comprehensive guide covering topics like API, security, workflows, and more for effective Gitana 3.2 documentation and application management.

Score: 1.9372028

Gitana 3.2 / Guide / Guide / Docker / Security Notices / CVE-2021-44228

Secure your Cloud CMS with Log4j2 updates against CVE-2021-44228. Upgrade to version 3.2.71 and follow mitigation steps for enhanced protection.

Score: 1.93098

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

Migrating Binary files to S3

By default, on-premise installations of Cloud CMS are configured with a GridFS (`gridfs`) Binary Storage Provider. This allows Cloud CMS to read and write binary files (such as attachments) to GridFS. At some point, as your installation grows, you may want change this. Suppose you wanted to move your binary files into S3 and use S3 as a Binary Storage Provider for Cloud CMS. To do so, we recommend the following steps: 1. Make a backup of your Cloud CMS database. 2. Create an S3 bucket and IAM us

Score: 1.8191433