Right now we should have more than simple stack running, containing almost everything that we may need. Downside is that there are lot of movable parts and after all, we should have some way to find how (and if) everything is running.
There are a lot of solutions for that kind of tasks but we will use Prometheus
Procedure is (almost) well known: create docker volume, create prometheus configuration file, create prometheus service declaration in compose.yml, create route in Caddyfile:
Last post left us with working caddy / database servers / openId server stack.
Let’s continue with that and add another very important part of the whole setup: centralized logging service. We will use Datalust Seq for that, and we will start with usual: create external docker volume for seq data:
docker volume create --label reco-seq reco-seq
Last part should have left us, hopefully, with working database servers, caddy proxy and phpMyAdmin as a management tool for mariadb database.
Next step is to add authorization server as it is very important part of the infrastructure, so let’s add it. For that, we will need gitlab registry docker image(s) which brings us to next requirement: gitlab account. If you have that, you should login to gitlab docker registry:
docker login registry.gitlab.com --username <gitlab-username>