docker

So far so good: last part left us with several services exposed by caddy with impressive domain names like ticketchangelog.domain.com, but that is not why are we here for. Therefore, edit your Caddyfile with an axe: remove all those selected lines

Let’s add few more basic modules:

Podzir

Add following to compose.yml:

144  podzir:
145    image: registry.gitlab.com/tekelija/tekelija/tekelija-podzir:latest
146    environment:
147      - AUTHSERVER__ISSUER=https://authenticatomatic.domain.com
148      - SERILOG__WRITETO__SEQ__ARGS__SERVERURL=http://seq:5341
149      - SERILOG__MINIMUMLEVEL__DEFAULT=Debug
150      - SERILOG__MINIMUMLEVEL__OVERRIDE__OpenIddict=Information
151      - SERILOG__MINIMUMLEVEL__OVERRIDE__Microsoft=Information
152      - MESSAGEBUS__URL=rabbitmq://rabbit
153      - CONNECTIONSTRINGS__PODZIR=server=mssql;initial catalog=podzir;user id=sa;password=<YourStrong!Passw0rd>;encrypt=false;
154      - TZ=Europe/Ljubljana
155      - ASPNETCORE_FORWARDEDHEADERS_ENABLED=true
156    hostname: podzir
157    depends_on:
158      - mssql

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>

What do we want?

To add few well known services to our simple-so-far setup, namely mariadb, mssql and mongodb.

What do we need?

What do we want?

At the end - to create very simple docker stack containing caddy serving simple responses over tls using provided keys.

What do we need?