Found 326 results for "search examples"
The search executed in 0.001445444 seconds. That's fast.
WorkflowWorkflow A workflow instance. Properties Name Type Description context object The workflow instance context. description string The Description of this document. documents object Any documents that are bound to the workflow instance. id string The ID of this document. modelId string The ID of the workflow model backing this workflow instance. modelVersion string The version of the workflow model backing this workflow instance. projectId string The ID of the project that this workflow instance wa
Score: 1.1209558
|
|||||||||||||||||||||||||||
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: 1.0881333
|
|||||||||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Command Line / Modules CommandsModules Commands The Cloud CMS command-line tool provides developers with a command-line driven mechanism that allows them to: register and unregister user interface modules deploy and undeploy user interface modules User Interface Modules are deployed from public Git repositories (such as GitHub) and consist of AMD JavaScript modules. These modules contain JavaScript, HTML, CSS, a JSON configuration file any additional client-side assets that may be used (such as images). For more information a
Score: 1.0843049
|
|||||||||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Releases / ActionsActions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat
Score: 1.0843049
|
|||||||||||||||||||||||||||
Gitana / 4.0 / Developers / Command Line Interface / Modules CommandsModules Commands The Cloud CMS command-line tool provides developers with a command-line driven mechanism that allows them to: register and unregister user interface modules deploy and undeploy user interface modules User Interface Modules are deployed from public Git repositories (such as GitHub) and consist of AMD JavaScript modules. These modules contain JavaScript, HTML, CSS, a JSON configuration file any additional client-side assets that may be used (such as images). For more information a
Score: 1.0843049
|
|||||||||||||||||||||||||||
Gitana / 4.0 / Data Engine / Releases / ActionsActions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat
Score: 1.0843049
|
|||||||||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / APIAPI The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish
Score: 1.0789437
|
|||||||||||||||||||||||||||
Gitana / 4.0 / Data Engine / API / OverviewAPI The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish
Score: 1.0789437
|
|||||||||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / Auto Analyze TextAuto Analyze Text This section describes features that are coming in 4.0 QName: f:auto-analyze-text With this feature in place, a content instance will automatically have its default binary attachment analyzed using a Text Analyzer service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up a Text Analysis Service. The service can either be c
Score: 1.065271
|
|||||||||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Features / Auto OCR ExtractAuto OCR Extract This section describes features that are coming in 4.0 QName: f:auto-ocr-extract With this feature in place, a content instance will automatically have its default binary attachment analyzed using an Optical Character Recognition (OCR) service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up an OCR Extraction Service. The
Score: 1.065271
|
|||||||||||||||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / Auto Analyze TextAuto Analyze Text This section describes features that are coming in 4.0 QName: f:auto-analyze-text With this feature in place, a content instance will automatically have its default binary attachment analyzed using a Text Analyzer service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up a Text Analysis Service. The service can either be c
Score: 1.065271
|
|||||||||||||||||||||||||||
Gitana / 4.0 / Data Engine / Aspects / Auto OCR ExtractAuto OCR Extract This section describes features that are coming in 4.0 QName: f:auto-ocr-extract With this feature in place, a content instance will automatically have its default binary attachment analyzed using an Optical Character Recognition (OCR) service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up an OCR Extraction Service. The
Score: 1.065271
|
|||||||||||||||||||||||||||
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @fragment@fragment Used to identify a section of output that can be cached based on the presently known request-time dependencies or any dependencies resolved by nested elements or nested @dependency tags. Parameters There are no parameters for this tag. Examples Example #1: Restaurant List Here is a template block that lists restaurants: {@fragment} {@query sort="title" skip="2" limit="7" type="custom:restaurant"}
|