I recently encountered a behaviour in Nginx that I didn’t expect and caused a production outage in the process. While I would love to blame DNS for this, as it’s usually the cause of most network-related issues, in this case, the fault lies with Nginx.

act

Additional:

• https://www.codereliant.io/tag/sre/

additional:

• https://www.reddit.com/r/devops/comments/15eb5e0/saved_more_than_30_compute_cost_by_switching_to/

docsy; hugo documentation

• https://lzone.de/cheat-sheet/Github
• https://docs.joshuatz.com/cheatsheets/github-actions/
• https://blog.gitguardian.com/github-actions-security-cheat-sheet/amp/

github action linter

k3s on premise with OIDC, secret manager, and workload identity GCP

Chaos testing, network emulation, and stress testing tool for containers

I frequently encounter the situation that the Pipewire audio server is suddenly stopped:

The problem usually appears when I connect/disconnect my laptop from the power adapter. My computer usually lags for a short time while switching between performance profiles.
systemctl --user status pipewire.service only shows that the Pipewire process was terminated by a SIGKILL signal, without any other useful log information.
Neither coredumpctl nor dmesg shows the existence of a core dump event.

the things that were forgotten always..

Creating a Culture of Documentation