1 |
[...] |
2 |
> > Another option that looks nice is GitLab. |
3 |
> |
4 |
> How does it work? The screenshots look exactly like github. |
5 |
|
6 |
Maybe, I can summarize it up a bit: |
7 |
|
8 |
- GitLab is a Ruby-On-Rails Application |
9 |
=> Requires very few setup on a gentoo system: ruby, a webserver and a mysql |
10 |
or postgresl database and redis. Some gems. That's it mostly. |
11 |
|
12 |
- It makes use of a lot of the FOSS-Code which was written by GitHub. |
13 |
|
14 |
- Itself is licensed under the MIT-License. |
15 |
|
16 |
- It used to be based around the gitolite shell, but nowadays has it's own |
17 |
shell to implement access restrictions on the managed repositories. |
18 |
|
19 |
- Repositories can be private (to users or teams) or public with write-access |
20 |
granted to individuals or teams. |
21 |
|
22 |
=> Up to here, it's just a way to manage multiple git repositories via http |
23 |
and access them via git://, ssh://, http:// and https:// |
24 |
It can be used just the same way a pure gitolite installation can be used. |
25 |
(Which by the way is true for any repository on github as well). |
26 |
|
27 |
On top of that: |
28 |
|
29 |
- It supports "Merge Requests", which are almost the same as PRs on Github, |
30 |
which allows user contributions to be reviewed quite easily. |
31 |
|
32 |
- It can trigger web-hooks in a similar way to github. |
33 |
|
34 |
It has some other nice features - but I personally believe they are not very |
35 |
relevant to gentoo: |
36 |
|
37 |
- Issue tracking per git repository |
38 |
- Wiki per git repository |
39 |
|
40 |
I am running an instance of gitlab for some of my private projects. The |
41 |
instance is accessed from roughly a dozen scripts and me. I run it including |
42 |
it's database (aside to some other services) on a VServer, which has 1 CPU |
43 |
assigned to it and 1 gigabyte of ram. Accessing it never appeared any slower |
44 |
to me than accessing github (even given that low hardware). Though, i have no |
45 |
data on how it scales to bigger environments. |
46 |
|
47 |
Updates to it are release on a once-per-month basis. Most of the time they are |
48 |
quite straight forward and installed in less than 5 minutes. |
49 |
|
50 |
The overall configure on the above mentioned hardware took me roughly 2 hours |
51 |
(sql, nginx, ruby etc being already emerged). This is mostly due to the fact |
52 |
gitlab's author mainly targets ubuntu. But it wasn't very hard to adapt the |
53 |
instructions to Gentoo w/ OpenRC. |
54 |
|
55 |
Hopefully these datapoints help to fill up some gaps :-) |
56 |
|
57 |
Sascha |