Found 590 results for "gitana 4.0 developers api resources deployment"
The search executed in 0.023546468 seconds. That's fast.
Gitana / 4.0 / Self Managed / Supported Stacks / OverviewSupported Stacks Gitana certifies certain supported stacks for on-premise Gitana 4.x installations. This information is relevant to customers who run Gitana 4.x on-premise and manage their own Elastic Search and MongoDB database tiers. This information is not applicable to SaaS customers since Gitana runs that infrastructure for hosted subscribers. The following links provide detailed information on the combinations of operating systems, databases, application servers, bundled components and thi
Score: 21.980871
|
|
Gitana / 4.0 / Developers / OverviewDevelopers Explore our guides and examples to integrate with Gitana. Drivers Integrate to Gitana quickly using one of our pre-built drivers C# For Microsoft C# / .NET apps. Go For Go apps and tools. Java For Java, Spring Framework / Boot apps. JavaScript / Node For JavaScript / Node.js (ES 5, Promises, async). JavaScript (Legacy) (Deprecated) V1 driver for JS PHP For PHP apps (Drupal, Wordpress). Python For Python apps and tools. Ruby For Ruby and Ruby-on-Rails. Frameworks Get started quickly wi
Score: 19.187304
|
|
Gitana 4.0 Developers Guide | Overview - GitanaGitana 4.0 Developers Guide | Overview - 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 ser
Score: 16.405813
|
|
Gitana / 4.0 / Content 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: 16.165422
|
|
Announcing Gitana 4.0 - GitanaAnnouncing Gitana 4.0 - 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
Score: 15.153216
|
|
Gitana / 3.2 / Guide / Guide / PlatformPlatform Cloud CMS provides a Platform within which you can build out one or more Projects to create, manage and deliver your content. You can create as many Projects as you wish and are also free to duplicate, back up, download or export Projects at any time. Users You can add users to your Platform at any time. When users log in, they log in to the Platform and are then able to see all of the Projects that they have access to. You may choose to invite some users to have some permissions agains
Score: 15.136339
|
|
Gitana / 4.0 / Content Engine / Platform / OverviewPlatform Cloud CMS provides a Platform within which you can build out one or more Projects to create, manage and deliver your content. You can create as many Projects as you wish and are also free to duplicate, back up, download or export Projects at any time. Users You can add users to your Platform at any time. When users log in, they log in to the Platform and are then able to see all of the Projects that they have access to. You may choose to invite some users to have some permissions agains
Score: 15.136339
|
|
Gitana / 3.2 / Guide / Guide / API KeysAPI Keys When you sign up for Cloud CMS, you are given your own tenant. Your tenant is essentially a guarded vault of data. To access this data, you need to present two sets of credentials to the Cloud CMS server: Client Credentials User Credentials Client Credentials identify the application that is attempting to connect and User Credentials identify who is using the application. Once signed in, the User Credentials establish the security context of the authenticated user, potentially limiting
Score: 14.921624
|
|
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: 14.637421
|
|
Gitana / 4.0 / Content 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: 13.900829
|
|
Gitana / 4.0 / Content 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: 13.843386
|
|
Gitana / 4.0 / Content 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: 13.492584
|
|
Gitana / 4.0 / Developers / Cookbooks / REST API CookbookREST API Cookbook Getting Started This guide assumes that you have already installed an HTTP client with which you will be making requests. However, it is highly recommended that you look at our language drivers and you read about the one that you will be using in your application. Connecting to Gitana Gitana uses OAuth2 to perform authentication, and as such to connect you will have to perform the authentication handshake manually to connect directly with the rest api. The specifics of this dif
Score: 13.486169
|
|
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: 12.731636
|
|
Gitana / 4.0 / Content 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: 12.644707
|
|
Container Registry - GitanaContainer 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
Score: 11.909678
|
|
Gitana / 4.0 / Self Managed / Containers / API ServerAPI Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is
Score: 11.672091
|
|
Gitana Documentation Center - GitanaGitana Documentation Center - 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 en
Score: 11.252359
|
|
Gitana / 4.0 / Content 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 Platform Go to Deployments Targets under Deployments Left Navigation Menu Click on Create a Deployment Target Title : "Live Web Site" Deployment Target Type : "Branch"
Score: 11.170141
|
|
The Gitana Blog - Page 1 - GitanaThe Gitana Blog - Page 1 - 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 enhan
Score: 11.128443
|
|
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: 11.023907
|
|
Gitana / 4.0 / Developers / Command Line Interface / OverviewCommand Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started client
Score: 10.874287
|
|
Gitana / 3.2 / Guide / Guide / Command LineCommand Line The Cloud CMS command-line client gives developers a way to work with their Cloud CMS tenant projects, applications, data stores and other resources from the command line. The CLI (command-line client) is a Node.js based command line tool that is very easy to use and available at no charge. Note: A valid Cloud CMS subscription is required to connect to Cloud CMS with the command-line client. This subscription can be a paid subscription or a free trial account. Getting Started client
Score: 10.789991
|
|
Gitana / 4.0 / Developers / Command Line Interface / Transfer CommandsTransfer Commands The Cloud CMS command-line tool provides developers with a command-line driven mechanism that allows them to: export content from Cloud CMS as an Archive import content into new Cloud CMS environments using that Archive Archives consist of ZIP files that store a full capture of the exported content. Archives may consist of an entire snapshot export or they may be partial (spanning date ranges or changeset ranges in the case of Repositories). The Cloud CMS Transfer Services make
Score: 10.752413
|
|
Gitana / 4.0 / Developers / API Keys / Create new Application KeysCreate new Application Keys If no API keys exist for your desired project, you will need to create an application for the project. To create a new application simply go to Manage Project, select Applications, and then create a New Application. Once the application has been created you can view the API Keys either under Manage Project -> API Keys, or, Manage Platform -> API Keys Note: API keys should not be shared across more than one application. Therefore, create a separate Cloud CMS applicatio
Score: 10.484491
|