[tek-nol-uh-jee]

Gitlab-CI and how to safely build docker images

Posted on

Well. That was some hard time to get that running. These ways of building docker images with gitlab-runner(s) can be found online: just binding the docker executable into your build image and the socket using docker-in-docker (dind) using docker-in-docker with own entrypoint But no one mentioned just using a bare gitlab-runner on your server with […]

[tek-nol-uh-jee]

Gitlab still a pain to update…

Posted on

But it gets smoother. Still no ‘just call the update command’ but at least better than before. This time a dependency created the most headache: ruby. But creating the package again after upgrade of the whole system from the AUR solved that issue. There are still some warnings and exceptions here and there, but the […]

[tek-nol-uh-jee]

Gitlab updates over arch-aur

Posted on

Again are GitLab updates quite exhausting. Better to say, not GitLab itself, but the repository updates of Arch Linux in combination with GitLab. ruby got a new release 2.2 and my GitLab instance is still running on 2.1. A downgrade of ruby prevented my instance from collapsing, but as usual upgrading GitLab is quite painful, […]

[tek-nol-uh-jee]

Evil gitlab update…

Posted on

During the weekend I’ve managed to bring down my webserver and my gitlab service, due to a failed gitlab update. Well, the install script of the new gitlab version did some not so good things, which prevented me from updating without hassle. But after all I’ve just put two projects up there, which were easily […]

[tek-nol-uh-jee]

Setting up gitlab on archlinux behind an apache

Posted on

Setting up gitlab is quite straight forward on archlinux, following this article. The wiki article even mentions the procedure to run gitlab behind an apache https proxy. The only thing I’ve missed was the hint for changing the base url of gitlab so that a repository link would work with the correct domain instead of […]