From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-172187-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 291A6138306
	for <garchives@archives.gentoo.org>; Wed, 13 Jul 2016 13:13:18 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 184CB21C1B5;
	Wed, 13 Jul 2016 13:13:08 +0000 (UTC)
Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com [209.85.220.180])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id DA06721C18C
	for <gentoo-user@lists.gentoo.org>; Wed, 13 Jul 2016 13:13:06 +0000 (UTC)
Received: by mail-qk0-f180.google.com with SMTP id s63so42828643qkb.2
        for <gentoo-user@lists.gentoo.org>; Wed, 13 Jul 2016 06:13:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:from:date:message-id
         :subject:to;
        bh=P+WMoEOMw5IbiHNjVbpfxTcMUZpJGo9EGVfc5FynD6g=;
        b=AkK0d3zvVGLsTzQJcdvTWoISSDlbI2n5NhpLkKp7UT6zj/gv3juoNlV9OarSgsYDOY
         VZ8E/dNv9w3LHetBMMBnIoiJCYNrqEC9mAcGp7nxuULNznPcJy2m0vUd++qat4ROz1pe
         jbzt2wOsmAW2+nkY01IyWMny74RauT1kkDJhT046kcUWN4lRdCvvZShCwYndFy/qfDSb
         HGsEu1lfsIVxVkMJpp1MfdKQkgAyMIkI8D/pXV8S+iMM39ptb86bY1qyC9htW3bp51Gp
         wecDDGTf+6dyu2iApeiQMgJOXqRKzQHz+TcF7GF5sPO9kEOyFv2Y8wVN3Xvb+3BW+D5t
         CsKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:sender:in-reply-to:references:from
         :date:message-id:subject:to;
        bh=P+WMoEOMw5IbiHNjVbpfxTcMUZpJGo9EGVfc5FynD6g=;
        b=E0lJj6CsFZ/KNrNGfsiNy7FufJmL8NNM+Sn076xdfFzj7qKb6evLp+MzGxUGrA3m+J
         txDdwaSucK2V+GCHEte6leiZlSuTSzPotzLlpuyr2+R1OiBlwbc3V8u8cZOPNd4Ch0TM
         tXF7eDTXD7bmwzHeuI9jbfKvgtfHl9DTUHEGnxi17KD1mPmtoibsgEqMJUcEXYNxc8iE
         a99PTglWMq//XvEbXlKmQnoqO/boYnfy8Rk6ZUqE4pxY8vP5PqBMo2VKqmPBDLTvSuYb
         XNsGlX2TInzaS0S+xlgOMp/wH6iz7OBHtNsLKiGkHGERJjqanmgxl0kwd70IYyZV711R
         lv8w==
X-Gm-Message-State: ALyK8tJGOSLRIhTBwtoI1BX/1eUZp3sEjrep2E2NuDWq86QDmWjWlZ9XKWLD1vTHKQErJxeO+AMOboYlgnSRuA==
X-Received: by 10.55.69.69 with SMTP id s66mr10349349qka.100.1468415585697;
 Wed, 13 Jul 2016 06:13:05 -0700 (PDT)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
Sender: freemanrich@gmail.com
Received: by 10.140.43.200 with HTTP; Wed, 13 Jul 2016 06:13:05 -0700 (PDT)
In-Reply-To: <loom.20160713T123802-32@post.gmane.org>
References: <loom.20160713T123802-32@post.gmane.org>
From: Rich Freeman <rich0@gentoo.org>
Date: Wed, 13 Jul 2016 09:13:05 -0400
X-Google-Sender-Auth: vJ3nDOCCHUYoXKrSV0ZXmoc5qAs
Message-ID: <CAGfcS_kQ9rm+7xCynJXmajVr0pRLq8+DmWA9_ESFD23OvxnR4w@mail.gmail.com>
Subject: Re: [gentoo-user] Gitlab experiences
To: gentoo-user@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: 67233b18-2021-4895-986f-b5b6918a8a39
X-Archives-Hash: 5354ebd2da748ed50f71215d57a9b047

On Wed, Jul 13, 2016 at 8:44 AM, James <wireless@tampabay.rr.com> wrote:
>
> Has anyone attempted to install a self hosted gitlab  on gentoo server(s)?
> A small gentoo cluster/container setup? Using a Distributed File System,
> like cephfs, orangefs or other DFS?
>

I know the Gentoo Infra team has had negative experiences with hosting
just about anything Java and don't want to go near it.  I don't know
if that is based on specific experiences with GitLab or with just
avoidance with Java in general.  Most of the competing solutions in
this space are also Java-based which is why we don't host any kind of
alternative to Github.

So, take that as a data point or not as you wish.  Certainly
interested to hear what others have found.

One thing I might suggest if there are concerns with maintenance of
Java is that you try to containerize it as much as possible.  Put
Gitlab and its dependencies in a container.  Use config management to
carefully track what need to be changed above the baseline to get it
working.  Put all the storage on mounts hosted outside the container
and bind/network mount them into the container.  Then if things get
out of hand in updates/etc you can just build a new Gitlab container
on each update, apply configuration and mounts, and then test it out.
You could make everything Gitlab depends on essentially disposable
that way.

-- 
Rich