Docker vs Gitolite

Overview

Docker

Stacks194.2K

Followers143.8K

Votes3.9K

Gitolite

Stacks38

Followers87

Votes12

GitHub Stars8.5K

Forks1.0K

Docker vs Gitolite: What are the differences?

Deployment and Version Control: Docker is a containerization technology used for deploying applications in isolated environments, while Gitolite is a tool used for managing access control and authorization for Git repositories.
Purpose: Docker focuses on providing a platform for building, shipping, and running applications using containers, whereas Gitolite is specifically designed for managing Git repositories and access control for version control.
Resource Management: Docker manages resources at the container level, allowing applications to run in isolated environments with their own resources, while Gitolite manages access control and permissions at the repository level, regulating user interactions with the codebase.
Collaboration: Docker enables collaboration by providing a consistent environment for developers to work across different machines, whereas Gitolite facilitates collaboration by allowing multiple developers to version control their code and manage access rights to repositories.
Storage: Docker utilizes Docker images and containers for packaging and running applications, focusing on runtime isolation and reproducibility, whereas Gitolite stores Git repositories and manages permissions for a codebase, focusing on version control and access management.
Scaling: Docker enables horizontal scaling of applications by running multiple containers across different hosts, providing flexibility and scalability, whereas Gitolite scales in terms of managing multiple repositories and controlling access rights across an organization's codebase.

In Summary, Docker and Gitolite serve different purposes in the development workflow, with Docker focusing on containerization for deployment and Gitolite on access control and authorization for version control repositories.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on Docker, Gitolite

Florian

IT DevOp at Agitos GmbH

Oct 22, 2019

Decided

lxd/lxc and Docker aren't congruent so this comparison needs a more detailed look; but in short I can say: the lxd-integrated administration of storage including zfs with its snapshot capabilities as well as the system container (multi-process) approach of lxc vs. the limited single-process container approach of Docker is the main reason I chose lxd over Docker.

483k views483k

Comments

Detailed Comparison

Docker	Gitolite
The Docker Platform is the industry-leading container platform for continuous, high-velocity innovation, enabling organizations to seamlessly build and share any application — from legacy to what comes next — and securely run them anywhere	Gitolite allows you to setup git hosting on a central server, with fine-grained access control and many more powerful features. Gitolite is an access control layer on top of git.
Integrated developer tools; open, portable images; shareable, reusable apps; framework-aware builds; standardized templates; multi-environment support; remote registry management; simple setup for Docker and Kubernetes; certified Kubernetes; application templates; enterprise controls; secure software supply chain; industry-leading container runtime; image scanning; access controls; image signing; caching and mirroring; image lifecycle; policy-based image promotion	Use a single unix user ("real" user) on the server.;Provide access to many gitolite users: they are not "real" users, so they do not get shell access.;Control access to many git repositories: read access controlled at the repo level, and write access controlled at the branch/tag/file/directory level, including who can rewind, create, and delete branches/tags.;Can be installed without root access, assuming git and perl are already installed.;Authentication is most commonly done using sshd, but you can also use "smart http" mode if you prefer (this may require root access to setup).
Statistics
GitHub Stars -	GitHub Stars 8.5K
GitHub Forks -	GitHub Forks 1.0K
Stacks 194.2K	Stacks 38
Followers 143.8K	Followers 87
Votes 3.9K	Votes 12
Pros & Cons
Pros 823 Rapid integration and build up 692 Isolation 521 Open source 505 Testability and reproducibility 460 Lightweight Cons 8 New versions == broken features 6 Documentation not always in sync 6 Unreliable networking 4 Moves quickly 3 Not Secure	Pros 5 Easy setup 4 Fine-tuned per-branch permissions 1 Really easy setup 1 Free 1 Free multi-server mirroring Cons 1 No tools for project and issue tracker 1 Doesn't have any user interface 1 Antiquated
Integrations
Java Docker Compose VirtualBox Linux Amazon EC2 Container Service Docker Swarm boot2docker Kubernetes Docker Machine Vagrant	No integrations available

What are some alternatives to Docker, Gitolite?

GitHub

GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.

Bitbucket

Bitbucket gives teams one place to plan projects, collaborate on code, test and deploy, all with free private Git repositories. Teams choose Bitbucket because it has a superior Jira integration, built-in CI/CD, & is free for up to 5 users.

GitLab

GitLab offers git repository management, code reviews, issue tracking, activity feeds and wikis. Enterprises install GitLab on-premise and connect it with LDAP and Active Directory servers for secure authentication and authorization. A single GitLab server can handle more than 25,000 users but it is also possible to create a high availability setup with multiple active servers.

RhodeCode

RhodeCode provides centralized control over distributed code repositories. Developers get code review tools and custom APIs that work in Mercurial, Git & SVN. Firms get unified security and user control so that their CTOs can sleep at night

AWS CodeCommit

CodeCommit eliminates the need to operate your own source control system or worry about scaling its infrastructure. You can use CodeCommit to securely store anything from source code to binaries, and it works seamlessly with your existing Git tools.

Gogs

The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.

Gitea

Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD. It published under the MIT license.

LXD

LXD isn't a rewrite of LXC, in fact it's building on top of LXC to provide a new, better user experience. Under the hood, LXD uses LXC through liblxc and its Go binding to create and manage the containers. It's basically an alternative to LXC's tools and distribution template system with the added features that come from being controllable over the network.

Upsource

Upsource summarizes recent changes in your repository, showing commit messages, authors, quick diffs, links to detailed diff views and associated code reviews. A commit graph helps visualize the history of commits, branches and merges in your repository.

Beanstalk

A single process to commit code, review with the team, and deploy the final result to your customers.

Related Comparisons

Docker vs Gitolite: What are the differences?

Deployment and Version Control: Docker is a containerization technology used for deploying applications in isolated environments, while Gitolite is a tool used for managing access control and authorization for Git repositories.
Purpose: Docker focuses on providing a platform for building, shipping, and running applications using containers, whereas Gitolite is specifically designed for managing Git repositories and access control for version control.
Resource Management: Docker manages resources at the container level, allowing applications to run in isolated environments with their own resources, while Gitolite manages access control and permissions at the repository level, regulating user interactions with the codebase.
Collaboration: Docker enables collaboration by providing a consistent environment for developers to work across different machines, whereas Gitolite facilitates collaboration by allowing multiple developers to version control their code and manage access rights to repositories.
Storage: Docker utilizes Docker images and containers for packaging and running applications, focusing on runtime isolation and reproducibility, whereas Gitolite stores Git repositories and manages permissions for a codebase, focusing on version control and access management.
Scaling: Docker enables horizontal scaling of applications by running multiple containers across different hosts, providing flexibility and scalability, whereas Gitolite scales in terms of managing multiple repositories and controlling access rights across an organization's codebase.

Docker vs Gitolite

Overview