From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id BB42C1381F3 for ; Sun, 12 May 2013 19:18:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id B940AE0833; Sun, 12 May 2013 19:18:34 +0000 (UTC) Received: from mail.babbelbox.org (babbelbox.org [83.133.105.186]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 46ECEE08F5 for ; Sun, 12 May 2013 19:18:32 +0000 (UTC) Received: (qmail 24474 invoked from network); 12 May 2013 19:20:21 -0000 Received: from tmo-096-79.customers.d1-online.com (HELO sammi.localnet) (sascha@babbelbox.org@80.187.96.79) by babbelbox.org with ESMTPA; 12 May 2013 19:20:21 -0000 From: sascha-ml@babbelbox.org To: gentoo-dev Subject: [gentoo-dev] GitLab Feature-Set / Was: devmanual moved to github Date: Sun, 12 May 2013 21:18:13 +0200 Message-ID: <39106330.P4KaKQNKU3@sammi> User-Agent: KMail/4.10.3 (Linux/3.9.0-gentoo; KDE/4.10.3; x86_64; ; ) In-Reply-To: <20130512172003.9979.qmail@stuge.se> References: <20879.47550.568189.770408@a1i15.kph.uni-mainz.de> <20130512172003.9979.qmail@stuge.se> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 72417ae3-5926-4e2d-9448-bd519b20099c X-Archives-Hash: 0e70d78cccdf1831abb979fba8ce9c05 [...] > > Another option that looks nice is GitLab. > > How does it work? The screenshots look exactly like github. Maybe, I can summarize it up a bit: - GitLab is a Ruby-On-Rails Application => Requires very few setup on a gentoo system: ruby, a webserver and a mysql or postgresl database and redis. Some gems. That's it mostly. - It makes use of a lot of the FOSS-Code which was written by GitHub. - Itself is licensed under the MIT-License. - It used to be based around the gitolite shell, but nowadays has it's own shell to implement access restrictions on the managed repositories. - Repositories can be private (to users or teams) or public with write-access granted to individuals or teams. => Up to here, it's just a way to manage multiple git repositories via http and access them via git://, ssh://, http:// and https:// It can be used just the same way a pure gitolite installation can be used. (Which by the way is true for any repository on github as well). On top of that: - It supports "Merge Requests", which are almost the same as PRs on Github, which allows user contributions to be reviewed quite easily. - It can trigger web-hooks in a similar way to github. It has some other nice features - but I personally believe they are not very relevant to gentoo: - Issue tracking per git repository - Wiki per git repository I am running an instance of gitlab for some of my private projects. The instance is accessed from roughly a dozen scripts and me. I run it including it's database (aside to some other services) on a VServer, which has 1 CPU assigned to it and 1 gigabyte of ram. Accessing it never appeared any slower to me than accessing github (even given that low hardware). Though, i have no data on how it scales to bigger environments. Updates to it are release on a once-per-month basis. Most of the time they are quite straight forward and installed in less than 5 minutes. The overall configure on the above mentioned hardware took me roughly 2 hours (sql, nginx, ruby etc being already emerged). This is mostly due to the fact gitlab's author mainly targets ubuntu. But it wasn't very hard to adapt the instructions to Gentoo w/ OpenRC. Hopefully these datapoints help to fill up some gaps :-) Sascha