Mario Ranftl majodev

Launch Sublime Text 2 from the Mac OS X Terminal

Sublime Text 2 ships with a CLI called subl (why not "sublime", go figure). This utility is hidden in the following folder (assuming you installed Sublime in /Applications like normal folk. If this following line opens Sublime Text for you, then bingo, you're ready.

open /Applications/Sublime\ Text\ 2.app/Contents/SharedSupport/bin/subl

You can find more (official) details about subl here: http://www.sublimetext.com/docs/2/osx_command_line.html

Installation

How to setup your own CA with OpenSSL

For educational reasons I've decided to create my own CA. Here is what I learned.

First things first

Lets get some context first.

Create Root CA (Done once)

Last update: Nov 2025.

Create Root Key

Attention: this is the key used to sign the certificate requests, anyone holding this can sign certificates on your behalf. So keep it in a safe place!

openssl ecparam -genkey -name secp384r1 | openssl ec -aes256 -out rootCA.key

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

Electron Apps Causing System-Wide Lag on Tahoe

This script detects apps with not yet updated versions of Electron.

Repo: https://github.com/tkafka/detect-electron-apps-on-mac

See:

LLM Wiki

A pattern for building personal knowledge bases using LLMs.

This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.). Its goal is to communicate the high level idea, but your agent will build out the specifics in collaboration with you.

The core idea

Most people's experience with LLMs and documents looks like RAG: you upload a collection of files, the LLM retrieves relevant chunks at query time, and generates an answer. This works, but the LLM is rediscovering knowledge from scratch on every question. There's no accumulation. Ask a subtle question that requires synthesizing five documents, and the LLM has to find and piece together the relevant fragments every time. Nothing is built up. NotebookLM, ChatGPT file uploads, and most RAG systems work this way.

	try {
	module.$localStorage[key] = serializer(value);
	} catch(e) {
	if(e.name === 'QUOTA_EXCEEDED_ERR') {
	// reset to make space
	module.reset();
	module.$localStorage[key] = serializer(value);
	} else {
	module.localStorageAvailable = false;
	$log.error("Local storage write failure - " + e);

	#!/bin/bash
	# __
	# _____ ____ _/ \|_ ____ ____ _______
	# / \ _/ __ \ \ __\_/ __ \ / _ \ \_ __ \
	# \| Y Y \\ ___/ \| \| \ ___/ ( <_> ) \| \| \/
	# \|__\|_\| / \___ > \|__\| \___ > \____/ \|__\|
	# \/ \/ \/
	#
	# .___
	# __\| _/ __ __ _____ ______

	require.config({

	paths: {
	jquery : "../../vendors/js/jquery/jquery",
	validate : "../../vendors/js/jquery.validation/jquery.validate",
	validate_fr : "../../vendors/js/jquery.validation/messages_fr"
	},
	map: {
	// Façade modules or swap them for another one
	"*": {

	#!/bin/bash

	PATH=/bin:/usr/bin:/usr/local/bin

	check-nfs () {
	local TMPFILE=/tmp/checknfs.$$ RET=0 ORPHAN SUBSHELLPID

	if [ "$#" -eq 0 ]; then
	cat<<EOF
	usage: check-nfs NFS-DIRECTORY...