Hi, On 07/13/16 17:30, James wrote: > Ralf <ralf+gentoo <at> ramses-pyramidenbau.de> writes: > > >>> From the gentoo wiki, it looks like all of the dependencies are already >>> in portage:: >>> https://wiki.gentoo.org/wiki/GitLab#Prerequisites.2FDependencies Even if all dependency stuff is already inside portage, gitlab itself is not. So there's no guarantee that gitlab will meet dependency requirements in future when some packages upgrade or APIs change. > > >> 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. > > I wonder if using 'app-arch/dpkg' to just install the .deb files on gentoo > would work? > Issues with using dpkg to install gitlab on gentoo inside a VM/container ? Interesting idea, but I never tried it. The gitlab .deb is pretty huge (~350MiB) and is shipped along with its own webserver, ruby and all that other dependency monsters and a minimum requirement to external dependencies. So maybe this is in deed worth a try! Good point.
But what I know for sure that the .deb said to fit to current debian, where i have kind of a 'guarantee' that it will work in future with minimum pain. So for me a debian LXC container inside my gentoo box is the best solution. > > >> For private use, I deployed my Gitlab inside a LXC container on my >> Gentoo server box, everything else is really way too much tinkering >> around. If you have no other problems in your life, just try it out and >> go for it. > > Can you be more specific? Exactly which package(s) did you install this way? > Is debian inside that LXC, or just pure gentoo? Are you using CI with this > configuration? Yes, it's debian inside LXC. And no, I'm not using CI. > > >>> Any experiences with gitlab are most welcome for comment, good or bad. >> Yes. Bad. Slow, unreactive, eats tons of resources. Doesn't scale with >> large repos (except you have unlimited access to hardware resources). A >> Linux kernel git mirror finally crashed it. > > On a cluster would be my approach, after the installation issues are ironed > out on a single server install. > >> That's why I decided to switch to Gogs [1], even for business cases. >> Gogs is implemented in Go, has a pretty active and responsive community >> and (in my opinion) it is a well-maintained project. Looks and feels >> like gitlab but is much faster and consumes a minimum of resources. I >> strongly recommend to use Gogs. Just try it out on their website. > > Is this the gogs package you installed:: www-apps/gogs [1] > [1] "go-overlay" layman/go-overlay > > Or did you just use a SaaS/PaaS for Gogs....? Same here (sorry i was inaccurate): Gogs guys also provide a .deb file. Same strategy: Debian inside a LXC container on my Gentoo box. > > >> They also provide a .deb package, that's the reason why I'm running it >> inside a Debian LXC container as well. > > And this runs on a gentoo server, with debian inside the LXC? Or on a debian > machine with LXC? Ok, so this is my *private* setup: Single server box with gentoo on bare-metal, latest bleeding edge stuff. Nginx on that Gentoo that serves some lightweight sites and webapps (wordpress, roundcube, usual suspects). Nginx also terminates SSL. I did not want to install gitlab on gentoo because of its tons of dependencies. So I run a Debian LXC Container inside Gentoo. Nginx then reverse-proxies and SSL-terminates the Gitlab LXC container and iptables forwards the ssh port of the gitlab container. Updating gitlab to the latest version just costs an apt-get upgrade and a dozen updates later nothing exploded so far. > > Have you tried any VCS on a cluster (openstack/mesos/hadoop/others? Nope, not my department. Ralf > > curiously, > James > > > > >
