Found 182 results for "deployment deployment-handlers remote"
The search executed in 0.001858043 seconds. That's fast.
![]() |
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / IBM COS Deployment HandlerIBM 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.536095
|
![]() |
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / IBM COS Deployment HandlerIBM 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.536095
|
![]() |
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / File System Deployment HandlerFile System Deployment Handler Handles the deployment of one or more Deployment Packages to a file system. A file system is described by a local path on disk, such as: /www/files /data /Users/joesmith/files These paths, in turn, my describe mounts that are ephemeral or non-ephemeral (such as Amazon EBS mounted drives or shared network storage). The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails
Score: 8.515579
|
![]() |
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / File System Deployment HandlerFile System Deployment Handler Handles the deployment of one or more Deployment Packages to a file system. A file system is described by a local path on disk, such as: /www/files /data /Users/joesmith/files These paths, in turn, my describe mounts that are ephemeral or non-ephemeral (such as Amazon EBS mounted drives or shared network storage). The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails
Score: 8.515579
|
![]() |
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 workflow are meant as a starting point and may meet your needs. If you have more complex requirements you can also define
Score: 8.364327
|
![]() |
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 workflow are meant as a starting point and may meet your needs. If you have more complex requirements you can also define
Score: 8.294326
|
![]() |
Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Azure Blob Storage Deployment HandlerAzure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName 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. Configurat
Score: 8.196724
|
![]() |
Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Azure Blob Storage Deployment HandlerAzure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName 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. Configurat
Score: 8.196724
|
![]() |
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.074354
|
![]() |
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: 8.0074005
|
![]() |
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.3330936
|
![]() |
Gitana / 4.0 / Data Engine / Publishing / Lifecycle StatesLifecycle States Cloud CMS contains two content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. The two states in the Publishing lifecycle are : - Approved - Draft You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview the content either on the authoring website or the production/live website
Score: 7.174205
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers GuideUI Developers Guide The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature-complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired editorial
Score: 6.528948
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / OverviewUI Developers Guide The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature-complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired editorial
Score: 6.528948
|
![]() |
Gitana / 4.0 / Data Engine / Publishing / Content TypesContent Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi
Score: 6.528948
|
![]() |
Gitana / 3.2 / Guide / Guide / 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: 6.104316
|
![]() |
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: 5.724039
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / deployment-subcontextdeployment-subcontext [ { "evaluator": "and", "condition": [ { "evaluator": "context-deployment" }, { "evaluator": "not", "condition": { "evaluator": "context-pagerendition" } }, { "evaluator": "not", "condition": { "evaluator": "context-document" } } ], "config": { "deployment-subcontext": { "items": [ { "key": "deployment",
Score: 5.6257343
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / deployment-subcontextdeployment-subcontext [ { "evaluator": "and", "condition": [ { "evaluator": "context-deployment" }, { "evaluator": "not", "condition": { "evaluator": "context-pagerendition" } }, { "evaluator": "not", "condition": { "evaluator": "context-document" } } ], "config": { "deployment-subcontext": { "items": [ { "key": "deployment",
Score: 5.6257343
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / context-deploymentcontext-deployment If an Application Deployment is currently being observed. { "evaluator": "context-deployment" }
Score: 5.561945
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Evaluators / context-deploymentcontext-deployment If an Application Deployment is currently being observed. { "evaluator": "context-deployment" }
Score: 5.561945
|
![]() |
Gitana / 3.2 / Guide / Guide / Features / Deployment ConfigDeployment Config QName: f:deployment-config The Deployment Config feature lets you describe settings that should be considered by one or more Deployment Handlers during deployment. These settings may describe things such as a mappings of deployed content to file system paths. When a node is deployed, if it has the f:deployment-config feature on it, then that feature may instruct the Deployment Handler about how to deploy. Configuration The f:deployment-config feature is utilized by the followin
Score: 5.4466968
|
![]() |
Gitana / 4.0 / Data Engine / Aspects / Deployment ConfigDeployment Config QName: f:deployment-config The Deployment Config feature lets you describe settings that should be considered by one or more Deployment Handlers during deployment. These settings may describe things such as a mappings of deployed content to file system paths. When a node is deployed, if it has the f:deployment-config feature on it, then that feature may instruct the Deployment Handler about how to deploy. Configuration The f:deployment-config feature is utilized by the followin
Score: 5.4466968
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / deployment-receiver-subcontextdeployment-receiver-subcontext [ { "config": { "deployment-receiver-subcontext": { "items": [ { "key": "deployment-receiver", "title": "Deployment Receiver", "header": true, "order": 1000, "items": [ { "key": "deployment-receiver/overview", "title": "Overview", "uri": "#/deployment-receivers/{deploymentReceiverId}", "order": 10000
Score: 5.0629907
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / deployment-receiver-subcontextdeployment-receiver-subcontext [ { "config": { "deployment-receiver-subcontext": { "items": [ { "key": "deployment-receiver", "title": "Deployment Receiver", "header": true, "order": 1000, "items": [ { "key": "deployment-receiver/overview", "title": "Overview", "uri": "#/deployment-receivers/{deploymentReceiverId}", "order": 10000
Score: 5.0629907
|