Ky-Anh Huynh icy

Think twice before abandoning Xorg. Wayland breaks everything!

Hence, if you are interested in existing applications to "just work" without the need for adjustments, then you may be better off avoiding Wayland.

Wayland solves no issues I have but breaks almost everything I need. Even the most basic, most simple things (like xkill) - in this case with no obvious replacement. And usually it stays broken, because the Wayland folks mostly seem to care about Automotive, Gnome, maybe KDE - and alienating everyone else (e.g., people using just an X11 window manager or something like GNUstep) in the process.

As 2024 is winding down:

This was initially posted in an kubernetes-sigs/kustomize issue.

We are using Kustomize's vars feature. Initially we didn't understand how to use it for our purpose, but it is a 100% fit. One example is our Ingress resource, which looks like this:

# file: base/ingress.yaml
apiVersion: networking.k8s.io/v1beta1
kind: Ingress
metadata:
  name: services

	#!/usr/bin/env bash
	#
	# Script to remove GPG user (recipient) with git-crypt
	#
	# It will re-initialize git-crypt for the repository and re-add all keys except
	# the one requested for removal.
	#
	# Note: You still need to change all your secrets to fully protect yourself.
	# Removing a user will prevent them from reading future changes but they will
	# still have a copy of the data up to the point of their removal.

	#!/bin/bash

	# Unlock the directory, we need the unencrypted versions of the files
	git crypt unlock

	# Re-initialize git crypt, generating a new key
	rm .git/git-crypt/keys/default
	git crypt init

	# Make the key available to the current users