These articles discuss how to use version control systems, like Git and Subversion, on A2 Hosting servers. Version control systems enable you to track multiple file revisions, and are an important component of any software project.
The popular Git revision control system is installed on A2 Hosting's servers, and this article provides a brief introduction to using it. This article covers how to create and host a Git repository, how to make changes to a repository, how to work with branches (and merge changes from another branch), and how to clone a repository.
Learn how to set up a client to work with a Git repository on an A2 Hosting server. This article covers how to configure TortoiseGit on Microsoft Windows, and the "git" command line client on Linux and Mac OS X.
Learn how to set up and use the Subversion (SVN) revision control system on your A2 Hosting account here. This article covers how to create a repository, select an authentication method, and configure an SVN client.
Subversion clients use SSH to access remote repositories on A2 Hosting servers. However, a shared hosting account only has one SSH login. This is problematic if you want to grant multiple users access to an SVN repository. The solution is to create and deploy a separate SSH key pair for each user, and this article shows you how.
The Python-based Mercurial version control system is installed on all A2 Hosting shared servers. This article gives you an overview of the Mercurial system, as well as how to create and publish a repository.
A2 Hosting accounts include support for the Concurrent Versions System (CVS) revision control system. Learn how to create a repository and configure a CVS client in this article.
Your server may have an outdated version of the Git client installed. If so, there are ways you can use a newer version; learn how to configure and use a newer version of Git on both managed and unmanaged servers in this article.
This article discusses a problem that may occur when you try to push to a remote GitHub repository using HTTPS from an A2 Hosting server, and how to resolve it with two different methods (using SSH or modifying the HTTPS URL).