mirror of https://github.com/release-engineering/dist-git.git synced 2025-02-23 15:02:54 +00:00

DistGit provides home for linux distribution packages.

Find a file

clime c909efc4db update README		2018-02-21 11:00:57 +01:00
beaker-tests	add distgit-centos7 machine config, add possibility to test against it, add more (direct) tests	2018-02-19 11:48:00 +01:00
configs	added default_namespace config option	2018-02-05 22:12:53 +01:00
images	hosting files image	2015-04-15 11:05:31 +02:00
rel-eng	Automatic commit of package [dist-git] release [1.4-1].	2017-07-25 15:27:02 +02:00
scripts	fix position of default namespace application	2018-02-06 19:30:38 +01:00
selinux	give optional map permission to git_system_t on git_user_content_t	2018-01-13 16:40:16 +01:00
.gitignore	fix tests and cleanup the repo after last two unintended commits	2017-07-25 15:13:27 +02:00
COPYING	review update	2015-04-23 14:54:24 +02:00
dist-git.spec	version bump	2018-02-19 12:05:41 +01:00
LICENSE	review update	2015-04-23 14:54:24 +02:00
README.md	update README	2018-02-21 11:00:57 +01:00
Vagrantfile	add distgit-centos7 machine config, add possibility to test against it, add more (direct) tests	2018-02-19 11:48:00 +01:00

README.md

DistGit

DistGit (Distributed Git) is Git with additional data storage. It is designed to hold content of source rpms and consists of these three main components:

Git repositories
Lookaside cache to store source tarballs
Scripts to manage both

Read here for information about most recent release: https://github.com/release-engineering/dist-git/wiki

How Does It Work

RPM source package typically contains a spec file and the sources (upstream tarball + additional patches). Source tarballs, being binary and potentially large, are not very well suited to be placed in a Git repository. On each their update, Git would produce a huge, meaningless diff. That's why DistGit was introduced as it employs an efficient lookaside cache where the tarballs can be stored. The Git repo itself can then be left to do what it does best: keep track of changes on the spec file, downstream patches, and an additional text file called sources that contains link to the source tarball in the lookaside cache.

User Guide

You can follow this basic workflow before reading the tips below.

1. Build and Install the Package:

The project is prepared to be built as an RPM package. You can easily build it on Fedora or CentOS using a tool called Tito. To build the current release, use the following command in the repo directory:

$ tito build --rpm

Install the resulting RPM package:

# dnf install /path/to/the-package.rpm

2. Configuration:

Enable the lookaside cache by using and modifying the example httpd config:

# cd /etc/httpd/conf.d/dist-git/
# cp lookaside-upload.conf.example lookaside-upload.conf
# vim lookaside-upload.conf

Lookaside Cache uses https communication and client authenticates with ssl client certificate. The Dist Git service provider needs to issue the client certificate for every user.

3. Users and Groups:

All DistGit users need to:

have an ssh server access with private key authentication
be in a packager group on the server
be provided with an ssl client certificate to authenticate with the lookaside cache

4. Install DistGit Web Interface:

Install Cgit, the web interface for Git:

# dnf install cgit

And point it to the DistGit repositories:

echo "scan-path=/var/lib/dist-git/git/" >> /etc/cgitrc

It is useful to comment out cache-size entry in /etc/cgitrc (or set it to zero) to always get up-to-date repository state at each page refresh.

The web interface will be available on address like http://your-server/cgit.

5. Systemd Services:

# systemctl start sshd
# systemctl start httpd
# systemctl start dist-git.socket

6. DistGit client tools:

To interact with DistGit server, you can use use rpkg command-line tool.