Cloud based version control has two major benefits: it makes version control readily accessible to everyone and it provides an offsite backup. Several cloud based providers are available; GitHub, BitBucket, Visual Studio Team Services, Google Cloud Platform, and CodePlex to name a few. However, most (if not all) of them have their limitations. For the most part, if you want to keep your repositories private, you'll end up paying at some point.
GitHub has changed it plans so that all paid plans now include unlimited private repositories. When I first started using GitLab you were limited to just a few private repositories on most of the reasonably priced plans. However, if you are a large company with several developers or you simply don't like the idea of your code being hosted on someone else's server GitLab is still a solid alternative to GitHub
GitLab is a pretty solid repository manager. It offers most of the features that the more well known options offer and you can host it locally or you can use GitLab.com. If you have a Linux box available use it. Otherwise you can leverage VirtualBox to setup an Ubuntu VM.
GitLab's website does an excellent job of walking you through the installation process. Rather than trying to reinvent the wheel, I'm just going to direct you to their website: https://about.gitlab.com/downloads/.
You were probably beginning to think that I was one of those flash in the pan bloggers. Here one day, gone the next. Nope.
It's been a while, but I'm back. Some things beyond my control happened. They sucked, but they're in the past now. Time to keep moving forward.
My next post will focus on GitLab: an awesome alternative to GitHub if you have the resources to host it locally (and these days, just about everyone should have those resources available in some form or fashion). After that I'm hoping to move onto some F# posts. While I've been enamored with the language for some time, I haven't had the chance to really put it to use until now.
I'm also planning to continue my work with Antlr. According to Google Analytics that's what brings most of you to my blog anyway.
Beyond that we'll just have to wait and see what catches my interest. I'm doing my best to talk my current client into using a document database for caching. Not only is it something I want to learn more about, it's something I honestly believe is to valuable to pass up. Why hammer your relational DB when you can just grab the data from a cache or a secondary data store that has the data in the format you need without having to do four hundred joins?
Thanks for stopping by. I'll have that GitLab post up soon (unless things start to go south again).