Found 183 results for "deployment deployment-handlers s3"

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

Gitana / 3.2 / Guide / Guide / Deployment

Deployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may

Score: 21.223793

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers

Deployment Handlers A Deployment Handler provides the deployment implementation for a Deployment Target. When Deployment Packages are routed to a Deployment Target, the Deployment Target's "handler" is instantiated to handle the actual connectivity, copy and delivery of the Deployment Package's content. The following Deployment Handlers are available: Azure Blob Storage Deployment Handler Branch Deployment Handler File System Deployment Handler FTP Deployment Handler HTTP Deployment Handler IBM

Score: 18.740791

Gitana / 4.0 / Data Engine / Deployment / Overview

Deployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may

Score: 17.038507

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Amazon S3 Deployment Handler

Amazon S3 Deployment Handler Handles the deployment of one or more Deployment Packages to an Amazon S3 bucket. The Amazon S3 bucket is described by: accessKey secretKey region bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configuration { "accessKey": "{a

Score: 15.962817

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Amazon S3 Deployment Handler

Amazon S3 Deployment Handler Handles the deployment of one or more Deployment Packages to an Amazon S3 bucket. The Amazon S3 bucket is described by: accessKey secretKey region bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configuration { "accessKey": "{a

Score: 15.962817

Gitana / 4.0 / Data Engine / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 15.883307

Gitana / 4.0 / Data Engine / Deployment / Deployment Target

Deployment Target A Deployment Target contains the configuration for a Deployment Handler. It informs the handler about how to connect or what settings should be used when executing. Deployment Targets are configured for Deployment Strategies as well as for Deployment Receivers. When content is changed within Cloud CMS, a Deployment Strategy may decide to package up that modified content and deployment it to one or more Deployment Targets. Similarly, content may be deployed to a Deployment Recei

Score: 14.192491

Gitana / 4.0 / Data Engine / Deployment / Deployment Mappings

Deployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c

Score: 13.627225

Gitana / 4.0 / Data Engine / Publishing / Example Publishing Setup

Example Publishing Setup The following are the steps to config a typical Publishing setup (Publish and Unpublish): Step 1: Create Projects Create two projects Create an "Authoring" project Create a "Live" Project Step 2 : Create a Deployment Target Deployment Target is the endpoint where the package will be deployed or sent. Go to Manage Platform Go to Deployment Targets under Deployment Left Navigation Menu Click on Create a Deployment Target Title : "Live Web Site" Deployment Target Type : "Br

Score: 13.099519

Gitana / 4.0 / Data Engine / Integrations / Amazon Web Services

Amazon Web Services Cloud CMS provides out-of-the-box integration with a variety of Amazon Web Service offerings, including services for natural language processing, machine learning, semantic analysis and image recognition. You can learn more about these services here: Amazon Comprehend Amazon DocumentDB Amazon Elastic Search Service Amazon Elastic Transcoder Amazon Polly Amazon SNS Amazon SQS Amazon Transcribe Amazon Translate

Score: 12.614592

Gitana / 4.0 / Data Engine / Deployment / Deployment Receivers

Deployment Receivers A Deployment Receiver acts as an endpoint for local and remote Deployment Handlers that seek to ship their Deployment Packages to a destination. These are frequently used to move content between data centers or across different parts of the world to solve for latency issues (or to simply move content to the correct side of a DMZ for security reasons or runtime-performance reasons). Cloud CMS lets you create Deployment Receivers from within its user interface. You can create

Score: 11.864637

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers

Deployment Handlers A Deployment Handler provides the deployment implementation for a Deployment Target. When Deployment Packages are routed to a Deployment Target, the Deployment Target's "handler" is instantiated to handle the actual connectivity, copy and delivery of the Deployment Package's content. The following Deployment Handlers are available: Azure Blob Storage Deployment Handler Branch Deployment Handler File System Deployment Handler FTP Deployment Handler HTTP Deployment Handler IBM

Score: 11.095739

Gitana / 3.2 / Guide / Guide / Publishing

Publishing Publishing brings together many parts of Cloud CMS to enable you to manage the lifecycle of your Content. Our Publishing is very configurable to meet your diverse needs. To help get you started we have a simple example showing a Publish and Unpublish mechanism between an Authoring Project and a Live project. When Publishing is enabled in a Project you get: Workflow With Publishing enabled there are 2 simple workflows added to your Project: simple publish and simple unpublish. The simp

Score: 10.217713

Gitana / 4.0 / Data Engine / Publishing / Overview

Publishing Publishing brings together many parts of Cloud CMS to enable you to manage the lifecycle of your Content. Our Publishing is very configurable to meet your diverse needs. To help get you started we have a simple example showing a Publish and Unpublish mechanism between an Authoring Project and a Live project. When Publishing is enabled in a Project you get: Workflow With Publishing enabled there are 2 simple workflows added to your Project: simple publish and simple unpublish. The simp

Score: 10.217713

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 9.74538

Gitana / 3.2 / Guide / Guide / Binary Files / S3 Binary Storage

S3 Binary Storage Cloud CMS supports Amazon S3 (Simple Storage Service) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avo

Score: 9.7120075

Gitana / 4.0 / Data Engine / Platform / Binary Files / S3 Binary Storage

S3 Binary Storage Cloud CMS supports Amazon S3 (Simple Storage Service) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avo

Score: 9.7120075

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Mappings

Deployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c

Score: 9.017509

Gitana / 4.0 / Data Engine / Publishing / Publications

Publications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t

Score: 8.557644

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / IBM COS Deployment Handler

IBM COS Deployment Handler Handles the deployment of one or more Deployment Packages to an IBM Cloud Object Store (COS) bucket. The IBM Cloud Object Store bucket is described by: apiKey serviceInstanceId endpointUrl location bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proce

Score: 8.13945

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / IBM COS Deployment Handler

IBM COS Deployment Handler Handles the deployment of one or more Deployment Packages to an IBM Cloud Object Store (COS) bucket. The IBM Cloud Object Store bucket is described by: apiKey serviceInstanceId endpointUrl location bucketName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proce

Score: 8.13945

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Target

Deployment Target A Deployment Target contains the configuration for a Deployment Handler. It informs the handler about how to connect or what settings should be used when executing. Deployment Targets are configured for Deployment Strategies as well as for Deployment Receivers. When content is changed within Cloud CMS, a Deployment Strategy may decide to package up that modified content and deployment it to one or more Deployment Targets. Similarly, content may be deployed to a Deployment Recei

Score: 8.0545635

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Receivers

Deployment Receivers A Deployment Receiver acts as an endpoint for local and remote Deployment Handlers that seek to ship their Deployment Packages to a destination. These are frequently used to move content between data centers or across different parts of the world to solve for latency issues (or to simply move content to the correct side of a DMZ for security reasons or runtime-performance reasons). Cloud CMS lets you create Deployment Receivers from within its user interface. You can create

Score: 7.3740687

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Local Deployment Handler

Local Deployment Handler Handles the deployment of one or more Deployment Packages to a local Deployment Receiver. The deployment receiver must exist on the same Cloud CMS platform. It is identified by the receiverId property. The Deployment Packages will be handed to the Deployment Receiver and then processed from there. The Deployment Receiver may elect to pass those Deployment Packages down to its own configured targets or process them through additional rules priority to delivery. Configurat

Score: 7.280564

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Local Deployment Handler

Local Deployment Handler Handles the deployment of one or more Deployment Packages to a local Deployment Receiver. The deployment receiver must exist on the same Cloud CMS platform. It is identified by the receiverId property. The Deployment Packages will be handed to the Deployment Receiver and then processed from there. The Deployment Receiver may elect to pass those Deployment Packages down to its own configured targets or process them through additional rules priority to delivery. Configurat

Score: 7.280564