git

Recently I learned about GitOps which is a way to manage your Kubernetes clusters and the applications you run on top using Git. The idea is that you can declaratively describe the desired state of your systems in Git and roll out changes as soon as merges occur. You can immediately see the main benefits of such an approach: Your Git repositories become the single source of truth for both your infrastructure and application code, allowing the teams to increase productivity and stability (you get the Git log to audit changes).

Backup your Team Services Git Repositories with VSTS Vault: A simple windows service or console application designed to keep a local copy of all your code. Since January 2016 we’ve moved the source code of more than 30 projects to Git repositories hosted by Visual Studio Team Services. Moving to the cloud has some downsides and one thing that kept us thinking was the need to be sure that in the event of an internet connection failure or a Team Services outage we would be able to access our code and deploy hot fixes for our applications as part of our data protection plan.

Since the year started I’ve been working hard with Visual Studio Team Services (VSTS) with Git as source control. I was getting tired of entering my git credentials on each clone, pull or push, on Windows or Mac OS X, so this weekend I decided to surf the web and look for a multi-platform solution.