Version Control Introduction

The Version Control Layer (VCL) feature on Insites manages changes to your codebase. It allows multiple users to collaborate on the same file or project simultaneously without worrying about source code and file losses while ensuring that any changes made are recorded and tracked over time. Additionally, the version control feature also provides the ability to roll back changes or revert to a previous version of a codebase if necessary, which can be particularly helpful in cases where errors or bugs are introduced into a project. Version Control on Insites works by running GIT and File Management through AWS Lambda Function and Node JS.

Prerequisites

To understand this tutorial, it is required that you possess a certain level of familiarity with Instances on Insites, Version Control, and particular examples of Version Control Layer software such as Git and AWS CodeCommit.

• Instances
• Git
• Git Repository
• AWS CodeCommit

Supported Repositories

The Insites Version Control Layer (VCL) supports the following repositories:

• AWS CodeCommit (Private)
• GitHub (Private and Public)

Supported Modules

Version Control is currently supported on the following modules:

• Insites Site Manager

Limitations

The following limitations apply to Version Control:

• Can only update branch.
• Single file operations only.
• Does not yet have a to resolve or see where conflicts exist.
• GitHub and CodeCommit SSH Connection Test is not based on the Repository but on the account level.
• Can only align Pages/Views, Content Blocks/Partials and Templates/Layouts in the Instance and Local.
• Passphrase is currently not supported.