Found 717 results for "api node"
The search executed in 0.002317684 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / Policies / Attachment PoliciesAttachment Policies Attachment policies provide places where you can hook in behaviors that trigger when attachments are read, created, updated or deleted against a node. Unlike other policy handlers, these will only fire at the instance when an attachment is created, updated, or deleted, and will not fire upon a branch merge or release. When configuring your attachments, you can specify an attachment ID you wish to fire your policy. For example, suppose you are configuring a webhook rule that y
Score: 1.2054503
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Attachment PoliciesAttachment Policies Attachment policies provide places where you can hook in behaviors that trigger when attachments are read, created, updated or deleted against a node. Unlike other policy handlers, these will only fire at the instance when an attachment is created, updated, or deleted, and will not fire upon a branch merge or release. When configuring your attachments, you can specify an attachment ID you wish to fire your policy. For example, suppose you are configuring a webhook rule that y
Score: 1.2054503
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
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: 1.1992152
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Search / ExamplesExamples This page provides sample searches that you can review to get an idea of what is possible with search within Cloud CMS. Cloud CMS offers full integration to Elastic Search and, in doing so, it gives developers the ability to powerful queries using the Elastic Search DSL (as either JSON or a text-based query string format). Example: Full-text Search (using JS Driver) Suppose we want to search for all of the content nodes where the text eddie van halen appears. We can do so by using a ful
Score: 1.1973364
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 4.0 / Data Engine / Discovery / Search / ExamplesExamples This page provides sample searches that you can review to get an idea of what is possible with search within Cloud CMS. Cloud CMS offers full integration to Elastic Search and, in doing so, it gives developers the ability to powerful queries using the Elastic Search DSL (as either JSON or a text-based query string format). Example: Full-text Search (using JS Driver) Suppose we want to search for all of the content nodes where the text eddie van halen appears. We can do so by using a ful
Score: 1.1973364
|
||||||||||||||||||||||||||||||||||||||||||||
|
|
Gitana / 3.2 / Guide / Guide / Features / Translation
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Translation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration
Getting Started Welcome to the Cloud CMS Documentation center. Here is a test of a note adminition block: Note Here is a note! Here is a test of an important admonition blocK: Important Be wary of visitors bearing gifts!! Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Get
Getting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa
Login and Logout The Application Server provides login and logout support for development teams that wish to store their users and user account information inside of Cloud CMS Domains. Cloud CMS Domains are LDAP-like storage facilities for users, groups, group memberships and more. They're not required, technically, since the Application Server can accommodate other storage facilities (such as LDAP itself), but they're incredibly useful if you can use them since they let you take advantage of us
Container Hooks This page describes the configuration of HTTP hooks that can be wired into your container orchestration framework to facilitate container lifecycle events (such as shutdown). Lifecycle Hooks Your container orchestration framework likely supports the ability to signal a running API container when one of the following occurs: A container has finished starting up. A container is about to be shut down. In the Kubernetes world, there are two lifecycle hooks (postStart and preStop). Th
Login and Logout The Application Server provides login and logout support for development teams that wish to store their users and user account information inside of Cloud CMS Domains. Cloud CMS Domains are LDAP-like storage facilities for users, groups, group memberships and more. They're not required, technically, since the Application Server can accommodate other storage facilities (such as LDAP itself), but they're incredibly useful if you can use them since they let you take advantage of us
Container Registry - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and
We 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
One 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
Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/
Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/
Module Installation The Cloud CMS Application Server can also be run as a custom Node.js application. It is available as a Node.js module that you can require() in from npmjs.org. The server features a number of extension points that you can utilize to wire in new functionality or extend the framework. Getting Started Here is a simple example where we start up the Application Server from within a Node.js application: var server = require("cloudcms-server/server");
server.start();
The start() me
Module Installation The Cloud CMS Application Server can also be run as a custom Node.js application. It is available as a Node.js module that you can require() in from npmjs.org. The server features a number of extension points that you can utilize to wire in new functionality or extend the framework. Getting Started Here is a simple example where we start up the Application Server from within a Node.js application: var server = require("cloudcms-server/server");
server.start();
The start() me
Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior asso
Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior asso
Copied From QName: f:copied-from Indicates that a specific revision of a node received its content from a copy operation. This feature can be used to identify points in the node history where a copy operation occurred from a different node (even a node from a different branch or repository entirely) into the current node. The Copied From feature tracks a single property called sourceRef which is a node reference to the node on the source branch that was the source for the copy operation. The Cop
Copied From QName: f:copied-from Indicates that a specific revision of a node received its content from a copy operation. This feature can be used to identify points in the node history where a copy operation occurred from a different node (even a node from a different branch or repository entirely) into the current node. The Copied From feature tracks a single property called sourceRef which is a node reference to the node on the source branch that was the source for the copy operation. The Cop
Copy Multiple Nodes ID: copyMultipleNodes Copies multiple nodes and any of their owned children to a new location in the content graph. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeIds array true An array of node IDs to be copied (soure nodes) targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID
Copy Multiple Nodes ID: copyMultipleNodes Copies multiple nodes and any of their owned children to a new location in the content graph. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeIds array true An array of node IDs to be copied (soure nodes) targetRepositoryId text true The ID of the repository of the target parent node. targetBranchId text true The ID
|
