Found 314 results for "deployment deployment-handlers http"
The search executed in 0.001658642 seconds. That's fast.
|
Gitana / 3.2 / Guide / Guide / DeploymentDeployment 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: 25.099329
|
|
|
Gitana / 4.0 / Data Engine / Deployment / OverviewDeployment 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: 20.915218
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment HandlersDeployment 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: 17.880089
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / HTTP Deployment HandlerHTTP Deployment Handler Handles the deployment of one or more Deployment Packages to a custom HTTP endpoint. The custom HTTP endpoint is described by: url statusUrl username password Custom HTTP endpoints are useful for a large variety of purposes, including writing data into custom databases, synchronizing content from Cloud CMS with existing Content Management products, hooking into custom logic for CDN or cache invalidation and much more. Configuration { "url": "{url}", "statusUrl": "
Score: 16.915934
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / HTTP Deployment HandlerHTTP Deployment Handler Handles the deployment of one or more Deployment Packages to a custom HTTP endpoint. The custom HTTP endpoint is described by: url statusUrl username password Custom HTTP endpoints are useful for a large variety of purposes, including writing data into custom databases, synchronizing content from Cloud CMS with existing Content Management products, hooking into custom logic for CDN or cache invalidation and much more. Configuration { "url": "{url}", "statusUrl": "
Score: 16.915934
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment TargetDeployment 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.141073
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment StrategyDeployment 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: 14.074541
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment ReceiversDeployment 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: 13.124048
|
|
|
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: 12.046246
|
|
|
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: 12.046246
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment MappingsDeployment 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: 11.886792
|
|
|
Gitana / 4.0 / Data Engine / Publishing / Example Publishing SetupExample 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: 11.251351
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Remote Deployment HandlerRemote Deployment Handler Handles the deployment of one or more Deployment Packages to a remote Deployment Receiver. Where: url is the URL of the target Cloud CMS API server receiverId is the ID of the receiver on the target Cloud CMS API server In addition, you should provide the API keys of the user who the Remote Deployment Handler will authenticate as. clientKey clientSecret username password Configuration { "url": "{url}", "clientKey": "{clientKey}", "clientSecret": "{clientSecr
Score: 10.404086
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Remote Deployment HandlerRemote Deployment Handler Handles the deployment of one or more Deployment Packages to a remote Deployment Receiver. Where: url is the URL of the target Cloud CMS API server receiverId is the ID of the receiver on the target Cloud CMS API server In addition, you should provide the API keys of the user who the Remote Deployment Handler will authenticate as. clientKey clientSecret username password Configuration { "url": "{url}", "clientKey": "{clientKey}", "clientSecret": "{clientSecr
Score: 10.404086
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment HandlersDeployment 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: 10.263671
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment ReceiversDeployment 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: 8.649972
|
|
|
Gitana / 4.0 / Data Engine / Publishing / PublicationsPublications 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.516992
|
|
|
Gitana / 3.2 / Guide / Guide / PublishingPublishing 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: 8.420169
|
|
|
Gitana / 4.0 / Data Engine / Publishing / OverviewPublishing 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: 8.420169
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment TargetDeployment 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.02573
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment StrategyDeployment 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: 7.959199
|
|
|
Gitana / 4.0 / Data Engine / Publishing / Preview ServersPreview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up
Score: 7.313188
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment MappingsDeployment 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: 7.294009
|
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Local Deployment HandlerLocal 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.253363
|
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Local Deployment HandlerLocal 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.253363
|