public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Gitlab experiences
Date: Wed, 13 Jul 2016 15:06:46 +0000 (UTC)	[thread overview]
Message-ID: <loom.20160713T165748-546@post.gmane.org> (raw)
In-Reply-To: e77a9c8e-101f-aa76-6736-dc26a14a867d@ramses-pyramidenbau.de

Ralf <ralf+gentoo <at> ramses-pyramidenbau.de> writes:


> On 07/13/16 16:35, Rich Freeman wrote:
> > On Wed, Jul 13, 2016 at 9:19 AM, Ralf
> > <ralf+gentoo <at> ramses-pyramidenbau.de> wrote:
> >> I recommend to deploy gitlab inside a Debian LXC/Docker container as
> >> Gitlab guys provide and maintain precompiled .deb packages. You do not
> >> want to compile it on your own as it comes with a load of dependencies.
> >> And once dependencies change you really might run into trouble with
> >> gentoo. Gitlab isn't just a tiny one-click-and-it-runs webservice, it's
> >> a whole ecosystem.

Yep, I heard a bit of bitching about maintaining it. I was contacted by a
corp to install and manage gitlab for them. It's not my cup of tea, so folks
in that space must be upset with maintenance issues....

> > This is part of why I'd suggest not upgrading it in-place.  Just
> > create a new container from scratch every time there is an update. 
> Sure, I totally agree. But from a maintenance point of view this can
> become a full-time job very quickly, as gitlab has pretty short
> innovation and release cycles. And you do want to install updates very
> quickly, especially for web-apps.

Interesting idea. It certainly is a good candidate for codes that stress
a cluster. I'll keep that in mind.

>   Ralf

> > OF course, Gentoo makes this somewhat more painful than other distros; 
> > it tends to be designed around upgrading in-place.

I did not realize it was so java centric...... I'm out, cause I have more
icedtea-java projects than I know what to do with..... (apache-spark).

Thanks for all the info guys,
James






  reply	other threads:[~2016-07-13 15:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 12:44 [gentoo-user] Gitlab experiences James
2016-07-13 13:13 ` Rich Freeman
2016-07-13 15:13   ` J. García
2016-07-13 18:14     ` [gentoo-user] " James
2016-07-13 20:57       ` Alan McKinnon
2016-07-13 13:19 ` [gentoo-user] " Ralf
2016-07-13 14:35   ` Rich Freeman
2016-07-13 14:48     ` Ralf
2016-07-13 15:06       ` James [this message]
2016-07-13 15:30   ` [gentoo-user] " James
2016-07-13 16:37     ` Ralf
2016-07-13 18:04   ` [gentoo-user] " Jeremi Piotrowski
2016-07-13 19:13     ` [gentoo-user] " James
2016-07-13 21:00       ` Alan McKinnon
2016-07-13 22:11         ` James
2016-07-15 23:04 ` GitPrep? (was: Re: [gentoo-user] Gitlab experiences) Andreas K. Huettel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20160713T165748-546@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox