![]() ![]() Some non-Git source control systems like Perforce (Helix) and Plastic SCM have evolved to have a “git interface” that allows them to work with Git client tools. However, we don’t consider those Git servers – and since this article is about how to choose a self-hosted Git solution, we didn’t evaluate those systems. Type 1: Technically Not Gitįor better or worse, Git has become the de-facto standard for source control, and virtually all other source control tools, from SVN to Mercurial, are considered dying, dead, or niche. ![]() We’ll talk about that, and some other options later. But first, let’s review the five types of self-hosted Git servers. On top of that, it is significantly more complex and challenging to maintain. If you don’t want to use their other features, it’s going to feel confusing and bloated. GitLab CE (free edition) is also a great choice, but it’s a whole lot more than source control. The simplest choice is, spoiler alert, to go with Gitea! Since you’ll be responsible for maintaining the server and hosting the software, the licensing costs should be less than a “cloud-hosted” version. Licensing Costsīudget is always a consideration – and source control isn’t the only tool that you’ll need when self-hosting development tools. Your source control server should be easy to install and use you’ll likely need to set it up a few times through your evaluation – plus have the flexibility to create new source control servers to test upgrades, and new versions, and provide new instances is convenient.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |