y0m's blog

Some contextual informations

I’ve been using self-managed Gitlab both for work and home projects, and just as anyone would, I’ve learnt to use the Gitlab CI, installing the Gitlab Runner inside various OS, as a simple shell executor on FreeBSD, and also on Docker inside a Linux virtualized guest. I like both, because the shell executor can be a really quick interface on a development server used by many developers, and because Docker let you manage things in fresh containers almost always up to date.

It’s been a while since previously posting, since it’s been busy years and I couldn’t find the time to update. I was using a custom method to update my Let’s Encrypt certificate for this site, but since then, it has been nicely integrated into Gitlab and so… it’s a burden less to monitor and it’s getting updated automatically.

It’s sometimes nice to have a full control over some data, but in that case: a personal web log, it doesn’t really matter much.

So, if you’ve been following my past blog posts, you may have read this one: Blog migrated!. But just in case:

• this blog is running with the help of gitlab.com pages feature

I’m using a free account, so this means I’m not paying a penny for this blog to be served. It’s no big deal, there are many other services like this on Internet. I’m just using the GitLab one because it’s serving my purpose.

These configuration have been tested only on FreeBSD 12.1-RELEASE.

1. Introduction

Wait… what? FreeBSD does not have Docker! Doesn’t it?

Well of course not really, but you can still install Docker using FreeBSD, it won’t just be FreeBSD in Docker since FreeBSD is not supported as Docker images.

In this blog post, I won’t discuss exactly how to install a few things, I will mostly point to blog posts and documentations so that you know what to do to install Docker and Kubernetes using FreeBSD.

These configuration have been tested only on FreeBSD 12.0-RELEASE.

Description

I’ve been trying for almost half a day to gather informations around about FreeBSD Jails using the VNET/VIMAGE, and since the only informations about this subject are only in /usr/share/examples/jails. It seems there are 2 choices when considering the VNET jail approach:

• using netgraph with the ngctl utility, and the jng helper in /usr/share/examples/jails
• using bridges and epair interfaces to bridge networks over the public interface, and so to use jib in the same folder

Since I don’t know anything about netgraph, I’ve prefered to take time and put the correct configurations on the host and the jail for bridge/epair.

It’s been a while since I first created my blog on Blogger, but I really needed a more simple solution at the time. I guess and think I’ve found it in GitLab Pages and Hugo SSG!

So… Welcome to my new blog!

I’ve removed almost all ancient/irrelevant/obsolete posts which I can’t really upgrade to current technologies (even if I could). Please bear with it :)

Earlier this year, I decided not to throw as much money in some dedicated online server (dedicated racked server) from Online.net. Not that the service would have been horrible, but with my current budget I could not offer myself such a high level service anymore.

So and since I had already tested DO (DigitalOcean) VPS (Droplets), I had migrated my mail server there. It was a simple 40GB / 2GB / 2CPU VPS with ZFS installed until recently, so with just one disk.

I’ve been looking for a C library to create CGI, and found a page that’s listing some :
Comparison of CGI libraries in C

Some are simple, maybe too much…, and some look complete, but too much complex and/or the code doesn’t suit my requirements, or the licence used is clearly not one I’d like to use also.

So I’ve decided to develop my own, a simple CGI C library, which try to be :