Andreas Palm zapling

Helm 3 is storing description of it's releases in secrets. You can simply find them via

$ kubectl get secrets
NAME                                                TYPE                                  DATA   AGE
sh.helm.release.v1.wordpress.v1                     helm.sh/release.v1                    1      1h

If you want to get more info about the secret, you can try to describe the secret

$ kubectl describe secret sh.helm.release.v1.wordpress.v1

True Color (24-bit) and italics with alacritty + tmux + vim (neovim)

This should make True Color (24-bit) and italics work in your tmux session and vim/neovim when using Alacritty (and should be compatible with any other terminal emulator, including Kitty).

Testing colors

Running this script should look the same in tmux as without.

curl -s https://gist.githubusercontent.com/lifepillar/09a44b8cf0f9397465614e622979107f/raw/24-bit-color.sh >24-bit-color.sh

ANSI Escape Sequences

Standard escape codes are prefixed with Escape:

Ctrl-Key: ^[
Octal: \033
Unicode: \u001b
Hexadecimal: \x1B
Decimal: 27

Story: Writing Scripts with Go

This is a story about how I tried to use Go for scripting. In this story, I’ll discuss the need for a Go script, how we would expect it to behave and the possible implementations; During the discussion I’ll deep dive to scripts, shells, and shebangs. Finally, we’ll discuss solutions that will make Go scripts work.

Why Go is good for scripting?

While python and bash are popular scripting languages, C, C++ and Java are not used for scripts at all, and some languages are somewhere in between.

Example: Moving up to a few commits to another branch

Branch A has commits (X,Y) that also need to be in Branch B. The cherry-pick operations should be done in the same chronological order that the commits appear in Branch A.

cherry-pick does support a range of commits, but if you have merge commits in that range, it gets really complicated

git checkout branch-B
git cherry-pick X
git cherry-pick Y

	// using require rather than import to make this simple for a standard javascript example
	const {connect, StringCodec, credsAuthenticator} = require('nats');
	const {encodeAccount, encodeUser} = require('nats-jwt');
	const {createAccount, createUser, fromSeed} = require('nkeys.js');

	// The Seed representing the Operator - you'll need this to sign new Accounts. Notice it starts with 'SO'
	const opSeed = 'SOA...';
	// The JWT representing the User from the System Account (Step 4)
	const sysJwt = 'eyJ0eXAiOiJKV1QiLCJhbGciOiJlZDI1NTE5LW5rZXkifQ...';
	// The Seed representing the User from the System Account (Step 3). Notice it starts with 'SU'

	from flask import Flask
	from requests import get

	app = Flask(__name__)
	SITE_NAME = 'https://google.com/'

	@app.route('/', defaults={'path': ''})
	@app.route('/<path:path>')
	def proxy(path):
	return get(f'{SITE_NAME}{path}').content

	#include "dz60.h"


	#define MODS_SHIFT_MASK (MOD_BIT(KC_LSHIFT)\|MOD_BIT(KC_RSHIFT))

	enum custom_keycodes {
	KX_UMLAUT_A = SAFE_RANGE,
	KX_UMLAUT_O,
	KX_UMLAUT_U,
	KX_UMLAUT_S,

	-- Found at:
	-- http://www.if-not-true-then-false.com/2009/postgresql-psql-psqlrc-tips-and-tricks/
	-- http://opensourcedbms.com/dbms/psqlrc-psql-startup-file-for-postgres/

	\set QUIET ON

	\pset pager always

	\pset null 'NULL'

	package main

	import (
	"bytes"
	"fmt"
	"io"
	"log"
	"mime/multipart"
	"net/http"
	"os"