Found 134 results for "drivers index"

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

Gitana / 4.0 / Developers / Drivers / Overview

Drivers We offer driver libraries that you can drop into your new or existing web applications to make it very easy to interact with Cloud CMS. These drivers handle things like authentication state, concurrency and fast API calls over the wire. The following drivers are available: C# Go Java JavaScript / Node JavaScript (Legacy) PHP Python Ruby

Score: 20.057983

Gitana / 3.2 / Guide / Guide / Authentication / Drivers

Drivers To connect to Cloud CMS, you need to establish two important pieces of information: The client that you are connecting as The user that you are signing on as The only way that a remote application can connect to your platform is if it can produce the correct credentials to identify itself as a client that you know about. As the platform administrator, you issue a client key/secret ahead of time. The application then needs to present these credentials to you and prove that it is who it sa

Score: 9.142466

Gitana / 4.0 / Data Engine / Authentication / Drivers

Drivers To connect to Cloud CMS, you need to establish two important pieces of information: The client that you are connecting as The user that you are signing on as The only way that a remote application can connect to your platform is if it can produce the correct credentials to identify itself as a client that you know about. As the platform administrator, you issue a client key/secret ahead of time. The application then needs to present these credentials to you and prove that it is who it sa

Score: 9.142466

Gitana / 4.0 / Developers / Overview

Developers Explore our guides and examples to integrate with Gitana. Drivers Integrate to Gitana quickly using one of our pre-built drivers C# For Microsoft C# / .NET apps. Go For Go apps and tools. Java For Java, Spring Framework / Boot apps. JavaScript / Node For JavaScript / Node.js (ES 5, Promises, async). JavaScript (Legacy) (Deprecated) V1 driver for JS PHP For PHP apps (Drupal, Wordpress). Python For Python apps and tools. Ruby For Ruby and Ruby-on-Rails. Frameworks Get started quickly wi

Score: 2.8582957

What is the reason for "Failed to index node"?

If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates

Score: 2.6101236

Gitana / 3.2 / Guide / Guide / Cookbooks

Cookbooks We've put together the following Cook Books to help you get started coding using the Cloud CMS drivers. Content Modeling Cookbook C# Cookbook Go Cookbook Java Cookbook JavaScript (Legacy) Cookbook JavaScript 2.0 Cookbook Node.js Cookbook PHP Cookbook Python Cookbook REST API Cookbook Ruby Cookbook Scripting Cookbook

Score: 2.5849657

Gitana / 4.0 / Developers / Cookbooks / Overview

Cookbooks We've put together the following Cook Books to help you get started coding using the Cloud CMS drivers. Content Modeling Cookbook C# Cookbook Go Cookbook Java Cookbook JavaScript (Legacy) Cookbook JavaScript 2.0 Cookbook Node.js Cookbook PHP Cookbook Python Cookbook REST API Cookbook Ruby Cookbook Scripting Cookbook

Score: 2.5849657

Gitana / 3.2 / Guide / Guide / Branches / Custom Indexes

Custom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha

Score: 2.5715296

Gitana / 4.0 / Data Engine / Branches / Custom Indexes

Custom Indexes Cloud CMS internally maintains indexes to improve the speed of your data lookups across all data store types. In most cases, there is no need to concern yourself with these as they deliver optimal performance. With respect to content repositories, however, Cloud CMS allows you to define custom database indexes on a per-branch basis. These custom indexes add to the default set that Cloud CMS automatically maintains. Each branch and/or snapshot maintains its own "tip" collection tha

Score: 2.5715296

Does Cloud CMS work with iOS, Android, Node.js, PhoneGap, JavaScript, HTML5 and any other popular frameworks?

You work with Cloud CMS just like you would any other ReSTful HTTP/OAuth2 service. In addition, we have a library of drivers and developer guides that you can look to for guidance on building apps for the web as well as iPhone, iPad, Android, PhoneGap, Titanium and many other frameworks.

Score: 2.5259838

Gitana / 3.2 / Guide / Guide / Features / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 2.5081131

Gitana / 4.0 / Data Engine / Aspects / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 2.5081131

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.73

3.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: 2.461144

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.74

3.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: 2.461144

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.76

3.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: 2.461144

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.77

3.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: 2.3563724

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.78

3.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: 2.3563724

Gitana / 3.2 / Guide / Guide / Docker / Upgrades / 3.2.75

3.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: 2.307262

How do I search for nested content?

Cloud CMS maintains two indexes that are of interest for finding things. The primary index is the MongoDB index - against which you can run any query you can dream up using the MongoDB DSL. The secondary index is the Elastic Search index - against which you can run any search you can dream up using the Elastic Search DSL. For information all kinds of really powerful stuff you can do with this, see: https://www.cloudcms.com/documentation/content-services/query.html https://www.cloudcms.com/docume

Score: 2.302228

Gitana / 3.2 / Guide / Guide / API / Pagination

Pagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver

Score: 2.2996454

Gitana / 4.0 / Data Engine / API / Pagination

Pagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver

Score: 2.2996454

Query Performance

Application queries Application code which consumes Cloud CMS content typically runs query API calls. These queries can be optimized in the following ways: Request only the properties needed When an application requires only a few properties from a set of nodes you should use “_fields” to limit the properties returned. This can drastically reduce the size of the payload and therefore the response time. In this example, we only need “_doc”, “title” and “_type” so these are the only fields that wi

Score: 2.2987282

Connecting via a Corporate Proxy

The Cloud CMS drivers support connectivity through a corporate proxy. The means of doing so are slightly different depending on which driver you're using. Node.js The Cloud CMS Node.js driver detects the following environment variable: HTTP_PROXY If this environment variable is specified, all API calls with be routed through the proxy server at that location. This proxy server may support either HTTP or HTTPS. For example, you may set the environment variable like this: HTTP_PROXY=http://127.0.0

Score: 2.244332

Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Upgrades

Upgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's

Score: 2.1897287

Gitana / 4.0 / Self Managed / Maintenance / Upgrades

Upgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's

Score: 2.1897287