Found 646 results for "docs fields any"
The search executed in 0.002156091 seconds. That's fast.
|
Gitana / 4.0 / Developers / Application Server / Authentication / Providers / CustomCustom This page provides some guidance on how to define your own custom Authentication Provider class for use within the Application Server. Note: If you're looking information on how to easily integrate a third-party Authentication Provider into the Application Server, we recommend first taking a look at the Local Provider as it can be configured to work with third-party endpoints pretty easily. Implementation Class We recommend extending the AbstractProvider class. The basic skeleton of the c
Score: 0.6237844
|
|
|
Gitana / 4.0 / Data Engine / API / Data Types / Billing Provider ConfigurationBilling Provider Configuration Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} If this sounds familiar, it's because it's exactly what Cloud CMS uses to supports its own subscription plans for Cloud CMS custom
Score: 0.6237844
|
|
Access Cloud CMS content anonymously or as a guest userThis question often comes up from folks who are building HTML applications that run in a browser. They'd like the browser to connect to Cloud CMS to download content and display it. Usually this consists of things like images but also may consist of other types of content in Cloud CMS such as raw nodes, PDF files, video assets or more. OAuth 2.0 and Access Tokens Fundamentally, everything in Cloud CMS is secured from an access perspective using OAuth 2.0. This means that an OAuth 2.0 access toke
Score: 0.6237844
|
|
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: 0.6237844
|
|
|
Gitana / 3.2 / Guide / Guide / Single Sign On (SSO) / OktaOkta This page provides information on how to configure Cloud CMS Single Sign On (SSO) for Okta and SAML 2.0. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). You can learn more about Okta here: https://www.okta.com Set up Okta In this section, we'll set up Single Sign On with Okta. Log into the Okta Administration Console Login at https://{your-okta-domain}.okta.co
Score: 0.61847305
|
|
|
Gitana / 3.2 / Guide / Guide / User Interface / MultilingualMultilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i
Score: 0.61847305
|
|
|
Gitana / 3.2 / Guide / Guide / User Interface / LockingLocking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr
Score: 0.61847305
|
|
|
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: 0.61847305
|
|
|
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: 0.61847305
|
|
|
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: 0.61847305
|
|
|
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: 0.61847305
|
|
|
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: 0.61847305
|
|
|
Gitana / 3.2 / Guide / Guide / Forms / Fields / Related ContentRelated Content ID: related-content The related-content field type renders an upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simil
Score: 0.61847305
|
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Projects / Deleted ItemsDeleted Items Cloud CMS provides a "copy on write" mechanism for any creates, updates or deletes to the content in a branch. This means that whenever you delete something, you're actually masking it as deleted. The content itself is never destroyed or removed permanently. As such, it is always possible walk backwards in time and discover content that was deleted - all the way back to the moment when your branch or repository was created. To make things easier, Cloud CMS provides a "deletions" in
Score: 0.61847305
|
|
|
Gitana / 4.0 / Data Engine / Authentication / Single Sign On (SSO) / OktaOkta This page provides information on how to configure Cloud CMS Single Sign On (SSO) for Okta and SAML 2.0. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Providers using SAML 2.0 and/or JWT. For more information, see Cloud CMS Single Sign On (SSO). You can learn more about Okta here: https://www.okta.com Set up Okta In this section, we'll set up Single Sign On with Okta. Log into the Okta Administration Console Login at https://{your-okta-domain}.okta.co
Score: 0.61847305
|
|
|
Gitana / 4.0 / Forms / CMS / Fields / Related ContentRelated Content ID: related-content The related-content field type renders an upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simil
Score: 0.61847305
|
|
|
Gitana / 4.0 / User Interface / Projects / Deleted ItemsDeleted Items Cloud CMS provides a "copy on write" mechanism for any creates, updates or deletes to the content in a branch. This means that whenever you delete something, you're actually masking it as deleted. The content itself is never destroyed or removed permanently. As such, it is always possible walk backwards in time and discover content that was deleted - all the way back to the moment when your branch or repository was created. To make things easier, Cloud CMS provides a "deletions" in
Score: 0.61847305
|
|
|
Gitana / 4.0 / User Interface / User Interface / MultilingualMultilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i
Score: 0.61847305
|
|
|
Gitana / 4.0 / User Interface / User Interface / LockingLocking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr
Score: 0.61847305
|
|
|
CMS editor LockingThere are two levels of locking which usually come into play in a scenario like this. One is a "UI lock" which is taken out when a user begins editing something within the user interface. This lock is released when they finished editing (either by hitting save or canceling). The other lock is a "data lock" which is a transactional lock taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and
Score: 0.61847305
|
|
|
Gitana / 3.2 / Guide / Guide / Cookbooks / JavaScript (Legacy) CookbookJavaScript (Legacy) Cookbook Getting Started To get started with the JavaScript driver, please visit the Gitana JavaScript (Legacy) Driver Page. Connecting to Gitana To connect, supply your API Keys as the argument to the connect() method. Gitana.connect({ "clientKey": "{clientKey}", "clientSecret": "{clientSecret}", "username": "{username}", "password": "{password}", "baseURL": "https://api.cloudcms.com" }, function(err) { var platform = this; }); If a problem w
Score: 0.61746764
|
|
|
Gitana / 4.0 / Developers / Cookbooks / JavaScript (Legacy) CookbookJavaScript (Legacy) Cookbook Getting Started To get started with the JavaScript driver, please visit the Gitana JavaScript (Legacy) Driver Page. Connecting to Gitana To connect, supply your API Keys as the argument to the connect() method. Gitana.connect({ "clientKey": "{clientKey}", "clientSecret": "{clientSecret}", "username": "{username}", "password": "{password}", "baseURL": "https://api.cloudcms.com" }, function(err) { var platform = this; }); If a problem w
Score: 0.61746764
|
|
|
Gitana / 3.2 / Guide / Guide / ProjectsProjects In Cloud CMS, a Project is an isolated workspace in which your team can collaborate on the production and publication of content. You can create as many Projects as you wish. Within each Project, you can: Design your content model (types, features and associations) Build out editorial forms for easy-content entry Wire up "automagic" business logic consisting of Rules, Actions and Conditions to automatically do things like call out to web hooks, send emails or sanitize your data as edito
Score: 0.614635
|
|
|
Gitana / 4.0 / Data Engine / Platform / ProjectsProjects In Cloud CMS, a Project is an isolated workspace in which your team can collaborate on the production and publication of content. You can create as many Projects as you wish. Within each Project, you can: Design your content model (types, features and associations) Build out editorial forms for easy-content entry Wire up "automagic" business logic consisting of Rules, Actions and Conditions to automatically do things like call out to web hooks, send emails or sanitize your data as edito
Score: 0.614635
|
|
|
CEM - shuffling deck chairs on the titanicGoing back 15 years, we’ve seen the core of providing websites shift across various types of “platforms” - from Web Content Management (WCM) to Enterprise Content Management (ECM) to Customer Experience Management (CEM). Every iteration involved another set of technologies, and associated migration headaches. Each expansion also consumed more and more of the resulting presentation tier. At first, this was mostly a good thing as no standard mechanisms existed to facilitate efforts. However, in th
Score: 0.614635
|