Found 144 results for "appserver installation docker"
The search executed in 0.002365813 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Application Server / ClusteringClustering The Cloud CMS Application Server supports running on a single Node process as well as multiple Node processes. Node processes can run on a single server instance or can be spread across multiple server instances behind a load balancer. By default, the Application Server starts up and allocates itself to a single CPU. This is known as single mode. Even if you have a server with more than one CPU on it, the Application Server will still only bind to 1 of those CPUs. When the Application
Score: 5.285649
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Security NoticesSecurity Notices Please review the following notices for information on mitigating known vulnerabilities and our recommended upgrade paths: CVE-2021-44228 CVE-2022-22965
Score: 4.7175245
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.843.2.84 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.84. Release Notes The release notes for this release are available here: https://gitana.io/releases/3.2.84.html Support for ARM-64 With version 3.2.84, we officially support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x86-64
Score: 4.458667
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.853.2.85 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.85. Release Notes The release notes for this release are available here: https://gitana.io/releases/3.2.85.html Support for ARM-64 With version 3.2.85, we officially support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x86-64
Score: 4.458667
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.863.2.86 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.86. Release Notes The release notes for this release are available here: https://gitana.io/releases/3.2.86.html Support for ARM-64 With version 3.2.86, we officially support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x86-64
Score: 4.458667
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.793.2.79 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.79. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.79 Support for ARM-64 With version 3.2.79, we are proud to announce official support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being
Score: 4.382657
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.803.2.80 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.80. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.80 Support for ARM-64 With version 3.2.80, we officially support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x8
Score: 4.382657
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.813.2.81 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.81. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.81 Support for ARM-64 With version 3.2.81, we officially support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x8
Score: 4.382657
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.823.2.82 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.82. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.82 Support for ARM-64 With version 3.2.82, we officially support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x8
Score: 4.382657
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.833.2.83 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.83. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.83 Support for ARM-64 With version 3.2.83, we officially support for ARM aarch64 architectures. This provides our customers with a choice of chip architectures to deploy on. The demand for ARM has increased as performance testing has shown a 20% better performance while being 10% cheaper than x8
Score: 4.382657
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / UpgradesUpgrades 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 / Upgrades / 3.2.733.2.73 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.73. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op
Score: 3.97648
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.743.2.74 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.74. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op
Score: 3.97648
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.763.2.76 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.76. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op
Score: 3.97648
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.773.2.77 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.77. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.77 Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support fo
Score: 3.8201232
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.783.2.78 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.78. Release Notes The release notes for this release are available here: https://gitana.io/release.html?name=3.2.78 Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support fo
Score: 3.8201232
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.753.2.75 Upgrade Notes The notes supplied here pertain to upgrading to Cloud CMS version 3.2.75. Elastic Search Client Make sure that you are have configured Cloud CMS to connect to Elastic Searching using the condor HTTP/S client. In prior versions of Cloud CMS, an http and transport client were offered that utilized the native drivers of Elastic Search. As we've expanded our support for Elastic Search to include Amazon OpenSearch, we've moved over to using the condor driver which is built and op
Score: 3.7473717
|
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / Azure Binary StorageAzure Binary Storage Cloud CMS supports Microsoft Azure's Blob Storage service by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to the Azure Blob Storage Service for persistence. When users seek to download those binary files, they are streamed back from Azure. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ
Score: 3.597216
|
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / IBM COS Binary StorageIBM COS Binary Storage Cloud CMS supports IBM Cloud Object Storage (COS) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to IBM COS for persistence. When users seek to download those binary files, they are streamed back from IBM COS. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to
Score: 3.597216
|
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / S3 Binary StorageS3 Binary Storage Cloud CMS supports Amazon S3 (Simple Storage Service) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avo
Score: 3.597216
|
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / Azure Binary StorageAzure Binary Storage Cloud CMS supports Microsoft Azure's Blob Storage service by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to the Azure Blob Storage Service for persistence. When users seek to download those binary files, they are streamed back from Azure. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ
Score: 3.597216
|
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / IBM COS Binary StorageIBM COS Binary Storage Cloud CMS supports IBM Cloud Object Storage (COS) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to IBM COS for persistence. When users seek to download those binary files, they are streamed back from IBM COS. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to
Score: 3.597216
|
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / S3 Binary StorageS3 Binary Storage Cloud CMS supports Amazon S3 (Simple Storage Service) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avo
Score: 3.597216
|
|
|
Gitana / 3.2 / Guide / Guide / Docker / Security Notices / CVE-2021-44228CVE-2021-44228 Cloud CMS API Container Cloud CMS API docker containers prior to version 3.2.71 ship with a version of Log4j2 that contains the vulnerability identified on December 9, 2021 as CVE-2021-44228. The Cloud CMS API shipped with recent versions packages with Log4j2 version 2.10.1 and runs on JDK 11.0.2. While the Cloud CMS product does not use Log4j lookups and does not use JNDI, we still recommend taking mitigation steps for this vulnerability. For purposes of mitigating CVE-2021-44228
Score: 3.5053916
|
|
Content Management as a MicroserviceOne of the big ideas we pursued when we set out to build Cloud CMS was to design the product so that it was entirely decoupled. Our vision was to have a number of discrete tiers that would consist of either single servers or clusters of servers dedicated to a single class of problems. For example, the Content API tier is dedicated to powering our JSON API. It does nothing else but receive requests, execute them and hand back JSON data responses. It had nothing to do with presentation or renderin
Score: 3.361176
|