c33s

When an interger is sent for monitor>type an internal error occurs. If a string is sent as in the main.yml example it is okay.

When an internal error occurs a 200 response not 500 is sent.

When an error occurs (e.g. monitor already exists) a 200 response is sent.

c33s

PostgreSQL is Enough

• Just Use Postgres for Everything
• Simplify: move code into database functions
• Hacker News discussion

Background and Cron Jobs

• https://github.com/citusdata/pg_cron
• https://github.com/cybertec-postgresql/pg_timetable

c33s

mTLS with self-signed certificates in nginx

First step is to generate the certificate and keys:

mkdir nginx-certs
cd nginx-certs
# Using the -nodes flag here so it does not ask for any password when exporting the key
openssl req -subj '/CN=ssl.test.local' -x509 -new -newkey rsa:4096 -keyout key.pem -out cert.pem -sha256 -days 365 -nodes -addext "keyUsage = digitalSignature,keyAgreement" -addext "extendedKeyUsage = serverAuth, clientAuth" -addext "subjectAltName = DNS:ssl.test.local, DNS:localhost, IP:127.0.0.1"
# The PCKS12 export will ask for a password. I will use 'test' again and will refer it in the final curl test command

c33s

VERSION = \"1.0.0\"

PREFIX ?= out
INCDIR	= inc
SRCDIR	= src
LANG	= c
OBJDIR	= .obj

MODULE		= binary_name
CC		= gcc

c33s

;What does this script do?
;It's a workaround for broken G910  Logitech keyboards (possibly other keyboards too) whereby some keys occasionally register multiple keystrokes for one kkkkkeypress.
;The key bug appears because keyboard registers multiple keystrokes in a very short timespan even though you pressed the key only once. 
;This script makes it so the subsequent keystrokes registered in a very short timespan are ignored thus outputing the key only for the first stroke.

;List all your broken keys between quotes below. I.e. if your broken keys are g and f then the line below shoud be 
;brokenKeys := "gf"
brokenKeys := "gf"

c33s

Running docker-compose as a systemd service

Files

File	Purpose
/etc/compose/docker-compose.yml	Compose file describing what to deploy
/etc/systemd/system/docker-compose.service	Service unit to start and manage docker compose
/etc/systemd/system/docker-compose-reload.service	Executing unit to trigger reload on docker-compose.service
/etc/systemd/system/docker-compose-reload.timer	Timer unit to plan the reloads

c33s

systemd for Administrators

Chronological list of the "systemd for Administrators" series published on 0pointer.net/blog:

• Part I: Verifying Bootup
• Part II: Which Service Owns Which Processes?
• Part III: How Do I Convert A SysV Init Script Into A systemd Service File?
• Part IV: Killing Services
• Part V: The Three Levels of "Off"
• Part VI: Changing Roots

c33s

daemon off;
worker_processes  1;
error_log  logs/error.log;

events {
    worker_connections  1024;
}

http {
    include       mime.types;

c33s

#!/usr/bin/env sh

# Example: ./download_minio.sh example.url.com username password bucket-name minio/path/to/file.txt.zst /download/path/to/file.txt.zst

if [ -z $1 ]; then
  echo "You have NOT specified a MINIO URL!"
  exit 1
fi

if [ -z $2 ]; then

c33s

#!/usr/bin/env sh

# Example: ./upload_to_minio example.url.com username password bucket-name internal/minio/path /absolute/path/file.txt.zst

if [ -z $1 ]; then
  echo "You have NOT specified a MINIO URL!"
  exit 1
fi

if [ -z $2 ]; then