Publish in Real Time

Continuous Rapid Deployment of Content on time all around the world, to APIs, databases, AI models and custom endpoints

• Deployment Targets

  Gitana Deployment lets you publish content from a source Gitana project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Gitana branches.

• Reporting and Verification

  View reports that indicate the state of your deployed content. Find discrepancies with checksum and path validation. Instantly deploy fresh content to all of your endpoints.

• Lifecycle Integration

  Automatically synchronize content to your endpoints based on how it moves across lifecycles, including content in draft, approved and archived states.

Gitana provides tools to allow Users to work in their own workspace and not conflict with other users/teams. However, a conflict may occur when merging your changes back to the Master Branch if the same content has been updated and merged back to Master from another release. Not to worry.. this is a complex problem which Gitana provides options and solutions for:

• Automatically accept/reject merge conflicts

  It is possible to automatically resolve a conflict in a certain way. For example, it may be true that the latest change is always the change that should be Accepted.

• User selects which changes to keep

  Users often need to review the Merge Conflicts and select which change to accept (local change or the change in Master).

Snap together your editorial contributions into a scheduled Release. Lock in a date and Gitana will automatically detect any potential conflicts with other scheduled Releases ahead and after your own. We make it easy to reconcile those conflicts so that your published content is always consistent.

• Scheduled Releases

  A scheduled release describes a future, locked in state of your content. Simply lock it in, walk away and rest assured that your content will go live on time.

• Hot Fixes

  Even with a locked-in schedule, you will at times need to quickly push a hot fix. Gitana lets you slot in a hot fix and discover any potential conflicting properties or content items that might be impacted in future releases after the hot fix.

• The Big Event

  When a scheduled Release goes live, it merges and triggers a series of events. These include sending emails, trigger Slack notifications and publishing to remote endpoints such as CDNs, S3 or other Gitana installations around the world.

Automatic calculation of the differences between work sets means that publishing is incremental and fast! Approved changes are replicated out to deployment endpoints instantly.

• Changeset Versioning

  Our changeset versioning model provides full-site capture of every property-level change made to your content. By quickly calculating deltas between branches, we are able to publishing the smallest incremental changes from source to target.

• Synchronized Endpoints

  Our out-of-the-box deployment handlers communicate with your deployment endpoints to discover content that is missing, out-of-date or placed in the wrong place. Changes are recalculated and shipping to keep endpoints up-to-date.

• Safe - Ensure related content is published

  When content is published, a check is made on related content to decide whether to include the related content or not. If the related content has been updated or does not exist on the target, then the related content will be published. For example,publishing an article without the related images would result in an incomplete page on the target.

Migrate data between development, authoring, test and live environments automatically using real-time sync and subscription-based push and pull.

• Data Hub

  Configure replication rules for your data to automatically push your data out to subscriber endpoints on schedule (or manually as needed).

• Incremental

  All replication is incremental, taking into differences calculated within the underlying changeset-versioning model.

• Fast

  Quick delta-replication means that deltas are computed to ship the optimal and fastest set of changes to keep everyone in sync.