As company we were very loyal to our beloved SCN – SVN. We used it from 2008. Few years ago (about two) we decided to use GIT as main SCN. We started using GIT repository on one of our serves using gitolite.

This method was very annoying and hard in administration. If You use GIT You of course know GitHub is great in it’s simplicity and embraces lot of tools for communication and co-work. Issues, Wikis – so on. We’ve planned to start with commercial version of GitHub (because we need private repos and strict security policies). But suddenly, one of our Developers (Michal – thanks!) discovered GitLab.

If You’re using GIT / GitHub – consider GitLab – which in short words is clone of Github, You could install on Your own servers.

… it even looks like GitHub and has most of it features

We use GitLab for:

  • easy management of repos management,
  • code review (possibly to use git pull requests, branches – so on. You could comment and reject all commits),
  • branching, mantaining code using web-browser GUI

GitLab has almost all GitHub features:

  • unified and side-by-side diffs
  • merge requests for code review
  • line specific comments
  • issues with attachments
  • issue labels and assignments
  • issue milestones / sprints
  • link to an external issue tracker
  • activity feed per project
  • user dashboard with filters
  • comprehensive activity feed
  • a wiki which is stored in git
  • project wall
  • code snippets
  • branches and a network graph
  • unique permission levels per user and project (guest, reporter, developer, master, owner)
  • protected branches (only masters can push to protected branches)
  • forking of repo’s
  • merge requests between forks
  • groups consisting of multiple people with a shared namespace for projects
  • multiple deploy keys are possible for the same project
  • multiple projects are possible for the same deploy key
  • global and per project notification settings
  • http(s) and ssh git access
  • LDAP user authentication (also compatible with Active Directory)
  • Single Sign On (SSO) support via Omniauth strategies
  • web hooks
  • convenient backups
  • administrative interface
  • web based editor
  • code search
  • runs on physical and virtual machines
  • high availability / clustering / scale out
  • access to the source code
  • broadcast messages

Check GitLab page and try it’s demo for details!

Make eCommerce ready for changes with microservices architecture  data-src=

Piotr Karwatka

Formet CTO of Divante eCommerce Technology Company. Open-source enthusiast and life-long builder. Co-founder of Vue Storefront and Open Loyalty. Now gathering engaged communities around new technologies. | LinkedIn | Twitter

Share your comment