Found 287 results for "gitana 3.2 guide guide appserver installation docker"
The search executed in 0.002243148 seconds. That's fast.
![]() |
Gitana 3.2 / Guide / Guide / Search / Query String ReferenceOptimize your content searching skills with Cloud CMS query strings to efficiently find and manage data using Elastic Search.
Score: 2.5644445
|
![]() |
Cloud CMS Docker imagesCloud 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.5416837
|
![]() |
More Ways to Run Cloud CMS On-PremiseWe 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.4675384
|
![]() |
Gitana 3.2 / Guide / Guide / SearchOptimize your content discovery with Cloud CMS, using Elastic Search for full-text indexing and structured search capabilities.
Score: 2.440928
|
![]() |
Gitana 4.0 / Content Engine / SearchOptimize your search with Cloud CMS using full-text and structured search powered by Elastic Search and Find API, enabling precise content retrieval.
Score: 2.440928
|
![]() |
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.4217548
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Kits / QuickstartSet up your development environment quickly with our Quickstart kit, featuring UI, API, MongoDB, and Elasticsearch. Perfect for beginners!
Score: 2.4094522
|
![]() |
Gitana 4.0 / Self Managed / Kits / QuickstartLaunch your app effortlessly with Quickstart! Connect UI, API, MongoDB, and Elasticsearch using Docker for seamless local development.
Score: 2.4094522
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Configuration / Antivirus ServerSecure your applications with Cloud CMS Antivirus Server. Effortlessly scan files via HTTP with integrated ClamAV support for ultimate protection.
Score: 2.3524635
|
![]() |
Gitana 4.0 / Self Managed / Containers / Antivirus ServerSecure your applications with Cloud CMS Antivirus Server. Effortlessly scan files via HTTP with integrated ClamAV support for ultimate protection.
Score: 2.3524635
|
![]() |
Gitana 3.2 / Guide / Guide / Deployment / Deployment Handlers / HTTP Deployment HandlerEffortlessly deploy packages to custom HTTP endpoints for advanced data management and integration with this powerful handler.
Score: 2.2856202
|
![]() |
Gitana 4.0 / Content Engine / Deployment / Deployment Handlers / HTTP Deployment HandlerDeploy and manage custom packages to HTTP endpoints efficiently. Integrate with databases, CDNs, and more using basic authentication.
Score: 2.2856202
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / KitsDownload Cloud CMS Docker Kits for pre-built configurations, API setup, and more. Ideal for quick deployment and versatile references.
Score: 2.218435
|
![]() |
Gitana 4.0 / Self Managed / KitsExplore Cloud CMS Docker kits for pre-built configurations, from quick starts to OEM, designed to simplify deployment and improve performance.
Score: 2.218435
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Kits / API ClusterOptimize API management with our API Cluster kit, featuring load balancing and efficient service distribution across api1 and api2 servers.
Score: 2.1952617
|
![]() |
Gitana 4.0 / Developers / User Interface CustomizationOptimize your Cloud CMS experience with our guide to enhancing the user interface through customizable JavaScript and JSON configurations.
Score: 2.1327534
|
![]() |
Gitana 4.0 / Developers / Drivers / JavaConnect Java and Android apps effortlessly with Gitana's driver. Explore Maven, API keys, and open-source options for seamless integration.
Score: 2.1224155
|
![]() |
Gitana 4.0 / Developers / Drivers / RubyConnect your Ruby apps to Gitana with ease. Use our open-source Ruby driver for seamless API integration and access comprehensive documentation.
Score: 2.1157026
|
![]() |
Download Version 1.0.3 of the Cloud CMS Java DriverThe Cloud CMS team is pleased to announce the immediate availability of the 1.0.3 version of the Gitana Java Driver for Cloud CMS. Java Driver for Cloud CMS The Gitana Java Driver is a Java library that you can include with your Java applications to take advantage of a programmatic way of interacting with the Cloud CMS server. It makes it easier for developers to utilize Cloud CMS functionality without having to manually handle calls against HTTP/REST, data serialization and event handling. The
Score: 2.0395806
|
![]() |
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.037713
|
![]() |
Cloud CMS JavaScript Driver Release 1.0.3 is out!The Cloud CMS team is pleased to announce the immediate availability of version 1.0.3 of the Cloud CMS JavaScript Driver for jQuery, Dojo, Javascript/HTML5 and Node.js applications. Download today from http://github.com/gitana/gitana-javascript-driver. JavaScript Driver for Cloud CMS The Cloud CMS JavaScript Driver is a JS library that you can drop into your HTML5/JS applications to take advantage of the authoring and delivery APIs of the Cloud CMS server. It makes it easier for developers to ut
Score: 1.9788306
|
![]() |
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.9474051
|
![]() |
Gitana 4.0 / Content EngineEnhance content management effortlessly with Gitana's secure, scalable platform, offering efficient publishing, AI-driven automation, and enterprise features.
Score: 1.9032452
|
![]() |
Enterprise Access Policies in Gitana 4.0 (Part 2)In this article, we'll continue our series on Access Policies within Gitana. We'll take a few interesting and more complex examples of how Access Policies may be used to guarantee compliance witih enterprise security requirements. In the previous article, we left off looking at how you can grant access to content using Access Policies that are defined at either a Platform or Project-level. Platform-scoped policies can be written once and applied across all of your Projects. In this way, you can
Score: 1.8902688
|
![]() |
API Max Heap recommendationWhat 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.8507342
|