Found 105 results for "docker notices cve-2022-22965"
The search executed in 0.0016 seconds. That's fast.
![]() |
Gitana 3.2 / Guide / Guide / Docker / KitsDocumentation Reference Explore Cloud CMS Docker Kits for easy deployment and diverse scenarios, featuring pre-built configurations for optimal performance. (Gitana 3.2)
Score: 2.2736
|
![]() |
Gitana 4.0 / Self Managed / KitsDocumentation Reference Download Cloud CMS Docker Kits for pre-built configurations and efficient setup based on customer feedback. (Gitana 4.0)
Score: 2.2736
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Kits / API ClusterDocumentation Reference Optimize API management with our API Cluster, featuring load balancing and seamless server communication. (Gitana 3.2)
Score: 2.2489
|
![]() |
Container Registry - GitanaWeb Page Container Registry - Gitana Status Releases Registry 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 content. Publishing
Score: 2.2475
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / UI ExtensionsDocumentation Reference Optimize your Cloud CMS UI with Docker extensions for seamless on-premise deployment and enhanced customization. (Gitana 4.0)
Score: 2.1945
|
![]() |
Gitana 4.0 / Self Managed / UI ExtensionsDocumentation Reference Optimize your Cloud CMS UI with Docker extensions for seamless on-premise deployment and enhanced customization. (Gitana 4.0)
Score: 2.1945
|
![]() |
Gitana 3.2 / Guide / Guide / Application Server / InstallationDocumentation Reference Explore comprehensive installation guides for Docker, Module, and Standalone setups. Simplify app server deployments now. (Gitana 3.2)
Score: 2.1058
|
![]() |
Gitana 4.0 / Developers / Application Server / InstallationDocumentation Reference Explore seamless Gitana app server installation with Docker, modules, or standalone options for developers. (Gitana 4.0)
Score: 2.1058
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.79Documentation Reference Upgrade to Cloud CMS 3.2.79 with ARM architecture support, ElasticSearch, and Redis 6.x configuration enhancements. (Gitana 3.2)
Score: 2.0992
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.80Documentation Reference Upgrade to Cloud CMS 3.2.80 for enhanced ARM-64 support, ElasticSearch integration, and Redis compatibility. (Gitana 3.2)
Score: 2.0992
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.81Documentation Reference Upgrade to Cloud CMS 3.2.81 for enhanced performance with ARM support, new ElasticSearch integration, and Redis updates. (Gitana 3.2)
Score: 2.0992
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.82Documentation Reference Upgrade seamlessly to Cloud CMS 3.2.82 with ARM aarch64 support, improved ElasticSearch client, and Redis 6.x compatibility. (Gitana 3.2)
Score: 2.0992
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.83Documentation Reference Upgrade to Cloud CMS 3.2.83 for ARM-64 support, ElasticSearch condor client integration, and Redis 6+. (Gitana 3.2)
Score: 2.0992
|
![]() |
Recommended environmentSupport Article 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.0896
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.84Documentation Reference Upgrade to Cloud CMS 3.2.84 with ARM aarch64 support, new Redis 6.x compatibility, and enhanced upgrade tools. (Gitana 3.2)
Score: 2.0546
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.85Documentation Reference Upgrade to Cloud CMS 3.2.85 for improved ARM-64 support and efficient Redis integration. Explore release notes for details. (Gitana 3.2)
Score: 2.0546
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.86Documentation Reference Discover Cloud CMS 3.2.86 with ARM-64 support, upgrade notes, Redis requirements, and detailed release info. (Gitana 3.2)
Score: 2.0546
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Container Services / KubernetesDocumentation Reference Automate Kubernetes deployment with Gitana SDK. Seamlessly integrate MongoDB, ElasticSearch, and more. (Gitana 3.2)
Score: 2.0532
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.87Documentation Reference Upgrade to Cloud CMS 3.2.87 with ARM-64 support and performance boosts. Requirements include MongoDB 4.0+ and Redis 6.x+. (Gitana 3.2)
Score: 2.0254
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.88Documentation Reference Upgrade seamlessly to Cloud CMS 3.2.88 with full ARM-64 support, using MongoDB 4.0+ and Redis 6.x or newer. (Gitana 3.2)
Score: 2.0254
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.89Documentation Reference Upgrade to Cloud CMS 3.2.89 with support for ARM-64, MongoDB 4.4+, and Redis 6.x for enhanced performance. (Gitana 3.2)
Score: 2.0254
|
![]() |
How does multi-tenancy work?Support Article 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.9971
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Security Notices / CVE-2021-44228Documentation Reference Mitigate CVE-2021-44228 vulnerability in Cloud CMS by upgrading to version 3.2.71 and Java Driver 1.0.42. (Gitana 3.2)
Score: 1.9308
|
![]() |
API Max Heap recommendationSupport Article 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.896
|
![]() |
Migrating Binary files to S3Support Article 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.82
|