Found 611 results for "docker configuration api-server"
The search executed in 0.002163935 seconds. That's fast.
How we use Docker at Cloud CMSAt 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.994893
|
|
Gitana / 3.2 / Guide / Guide / Docker / KitsKits 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: 2.974352
|
|
Gitana / 4.0 / Self Managed / Kits / OverviewKits 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: 2.974352
|
|
Gitana / 3.2 / Guide / Guide / Docker / Configuration / Encrypting PropertiesEncrypting Properties Cloud CMS lets you encrypt properties within your API configuration files to protect sensitive passwords, secrets and credentials. This encryption utilizes a public and private key. The private key is supplied to the Cloud CMS API server and the public key is provided to developers to encrypt sensitive data. Getting Started To get started, an administrator should generate a set of public/private keys. These are RSA encrypted keys. docker run -v .:/data public.ecr.aws/gitana
Score: 2.9331663
|
|
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: 2.874353
|
|
Gitana / 3.2 / Guide / Guide / Docker / Container Services / KubernetesKubernetes Kubernetes, also known as K8s, is an open-source system for automating the deployment, scaling, and management of containerized applications. Kubernetes is open-source and adaptable to a number of cloud providers including Amazon, Google, Azure and others. It allows you to express your infrastructure configuration in such a way as to take advantage of on-premises and a diversity of hybrid and public cloud infrastructures. For information on Kubernetes, please visit https://kubernetes.
Score: 2.8238165
|
|
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: 2.6981268
|
|
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: 2.6981268
|
|
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: 2.6981268
|
|
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: 2.6981268
|
|
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: 2.6981268
|
|
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: 2.5221105
|
|
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: 2.5221105
|
|
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: 2.5221105
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / OEMOEM 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 / OEMOEM 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
|
|
Migrating Binary files to S3By 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: 2.4669442
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / QuickstartQuickstart 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 / QuickstartQuickstart 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 / 3.2 / Guide / Guide / IntegrationsIntegrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser
Score: 2.4503632
|
|
Gitana / 4.0 / Data Engine / Integrations / OverviewIntegrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser
Score: 2.4503632
|
|
Recommended environmentThis 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.4308221
|
|
Gitana / 3.2 / Guide / Guide / Docker / UI ExtensionsUI 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: 2.3866086
|
|
Gitana / 4.0 / Self Managed / UI Extensions / OverviewUI 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: 2.3866086
|
|
Gitana / 3.2 / Guide / Guide / Docker / Configuration / Antivirus ServerAntivirus Server The Cloud CMS Antivirus Server is a Node.js application that exposes a HTTP interface to allow an application to remotely scan files by submitting them via HTTP. Submitted files are passed through TCP to a ClamAV daemon process. API GET / If the server is online, this will always return: { "ok": true } POST /status This checks the status of the daemon process and returns whether the Antivirus service is working nominally. If everything is working well, you will get back som
Score: 2.379285
|