DistGit provides home for linux distribution packages.
Find a file
2019-05-28 16:51:21 +02:00
.tito Wait with tito->rpkg migration, we still need tito here and there 2018-02-26 09:34:05 +01:00
beaker-tests fix naming of GroupCheckTest 2019-03-11 16:01:45 +01:00
configs add lookaside_dir option, deprecate cache_dir 2018-08-14 21:06:50 +02:00
docs/scripts/httpd add lookaside_dir option, deprecate cache_dir 2018-08-14 21:06:50 +02:00
images hosting files image 2015-04-15 11:05:31 +02:00
scripts add script for removing unused source tarballs in lookaside cache 2019-05-17 10:49:17 +02: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 remove old changelog entries 2019-05-28 16:46:13 +02:00
LICENSE review update 2015-04-23 14:54:24 +02:00
README.md update link to rpkg site 2019-05-28 16:51:21 +02:00
rpkg.conf add rpkg.conf with auto_pack = True so that srpm can be built 2019-05-16 12:20:51 +02:00
Vagrantfile update tests to f29 2019-03-11 16:09:32 +01:00

DistGit

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

  1. Git repositories
  2. Lookaside cache to store source tarballs
  3. Scripts to manage both

Read here for information about the 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.

storage

User Guide

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 with EPEL7 enabled using a tool called rpkg. To build the current release, use the following command in the repo directory:

$ rpkg srpm && rpkg local

Install the resulting RPM package:

# dnf install ./noarch/*

Clean-up:

$ rpkg clean -x

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:

  1. have an ssh server access with private key authentication
  2. be in a packager group on the server
  3. 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 or fedpkg command-line tools.

7. Deployment

You can see example of deployement in Fedora Infastructure and in Copr.

LICENSE

Whole project use MIT license. File upload.cgi uses GPLv1.