The blog aims to create a zero to fully working instance of VersionVault Explorer on AWS. The assumption is that the reader has a valid credential on AWS with permission to EC2 and S3 on an admin level. We also presume, the user has his initial setup in place and can take off with the installation with the instructions that follow.
VersionVault Express features an intuitive side-by-side comparison viewer where you can easily compare files and directories. VersionVault Express not only allows you to compare elements against their immediate predecessor but also to compare them against the changeset predecessor.
As VVE is released as OVA files (Open Virtual Appliance file), that must be downloaded and loaded as a VM in any of the VM provisioning tools or Hypervisor.In this document we will see how we can load the VersionVault Express OVA image in Oracle Virtual Box VM manager.
VersionVault Express’s primary UI is a browser-based application. It supports editing and saving single files, comparing files and reviewing change sets, simple cases of rebasing and delivering between streams, and more.
VersionVault Express can be configured to send out notifications when interesting events happen inside projects. These notifications are called webhooks. A webhook is simply a JSON payload sent to an endpoint over HTTP as a POST request. Any system that can respond to an HTTP POST request can be a webhook endpoint and perform any action it so chooses.
VersionVault Express relies on VersionVault Unified Change Management (UCM) as a set of processes for code development. In this article we’ll describe some of the concepts used in UCM and how to work as a team using VersionVault Express. In order to work with UCM in VersionVault Express the user must have the Developer role.