Florian Le Frioux floweb
| #!/usr/bin/env python3 | |
| # MIT License | |
| # | |
| # Copyright (c) 2025 Nick Doyle | |
| # | |
| # Permission is hereby granted, free of charge, to any person obtaining a copy | |
| # of this software and associated documentation files (the "Software"), to deal | |
| # in the Software without restriction, including without limitation the rights | |
| # to use, copy, modify, merge, publish, distribute, sublicense, and/or sell |
| Gans Media Retro Games Hot Mulligan | |
| Wonder Cheese Xavier Dang | |
| Shhhh! Golf is On Hot Mulligan | |
| This Is Why Paramore | |
| Shhhh! Golf is On Hot Mulligan | |
| BCKYRD - Acoustic Hot Mulligan | |
| Black Hole Be Your Own Pet | |
| Heem Wasn't There Hot Mulligan | |
| BCKYRD Hot Mulligan | |
| À la renverse Intenable |
This logging setup configures Structlog to output pretty logs in development, and JSON log lines in production.
Then, you can use Structlog loggers or standard logging loggers, and they both will be processed by the Structlog pipeline (see the hello() endpoint for reference). That way any log generated by your dependencies will also be processed and enriched, even if they know nothing about Structlog!
Requests are assigned a correlation ID with the asgi-correlation-id middleware (either captured from incoming request or generated on the fly).
All logs are linked to the correlation ID, and to the Datadog trace/span if instrumented.
This data "global to the request" is stored in context vars, and automatically added to all logs produced during the request thanks to Structlog.
You can add to these "global local variables" at any point in an endpoint with `structlog.contextvars.bind_contextvars(custom
| # syntax=docker/dockerfile:1.4 | |
| FROM jbangdev/jbang-action as builder | |
| WORKDIR / | |
| COPY <<EOF main.java | |
| //DEPS io.quarkus:quarkus-bom:2.8.0.Final@pom | |
| //DEPS io.quarkus:quarkus-resteasy-reactive | |
| import javax.ws.rs.*; | |
| import javax.ws.rs.core.MediaType; |
| FROM quay.io/keycloak/keycloak:17.0.0 as builder | |
| ENV KC_METRICS_ENABLED=true | |
| ENV KC_FEATURES=preview | |
| ENV KC_DB=postgres | |
| ENV KC_HTTP_RELATIVE_PATH=/auth | |
| # specify the custom cache config file here | |
| ENV KC_CACHE_CONFIG_FILE=cache-ispn-jdbc-ping.xml | |
| # copy the custom cache config file into the keycloak conf dir |
This (and related gists) captures how i created my docker swarm architecture. This is intended mostly for my own notes incase i need to re-creeate anything later! As such expect some typos and possibly even an error...
Each major task has its own gist, this is to help with maitainability long term.
Security Advisories / Bulletins / vendors Responses linked to Log4Shell (CVE-2021-44228)
- If you want to add a link, comment or send it to me
- Feel free to report any mistake directly below in the comment or in DM on Twitter @SwitHak
- Royce Williams list sorted by vendors responses Royce List
- Very detailed list NCSC-NL
- The list maintained by U.S. Cybersecurity and Infrastructure Security Agency: CISA List
| -- Based off IETF draft, https://datatracker.ietf.org/doc/draft-peabody-dispatch-new-uuid-format/ | |
| create or replace function uuid_generate_v7() | |
| returns uuid | |
| as $$ | |
| begin | |
| -- use random v4 uuid as starting point (which has the same variant we need) | |
| -- then overlay timestamp | |
| -- then set version 7 by flipping the 2 and 1 bit in the version 4 string | |
| return encode( |
- Motherboard : Aorus B550 Pro Ax
- CPU : AMD Ryzen 7 3700X
- Ram : Kit 2 x 16Gb Corsair Vengeance @ 3200Mhz
- GPU : Zotac RTX 3080 Amp Holo
- Storage:
- Crucial P2 1To