Jason Morganson jasonmorganson

The Twelfth Factor Correction

This is a series of notes on the Essay https://12factor.net/codebase

I. Codebase: One codebase tracked in revision control, many deploys

A twelve-factor app is always tracked in a version control system, such as Git, Mercurial, or Subversion. A copy of the revision tracking database is known as a code repository, often shortened to code repo or just repo.
A codebase is any single repo (in a centralized revision control system like Subversion), or any set of repos who share a root commit (in a decentralized revision control system like Git).

12 factor app specifically argues against a monorepo. Their argument is that the shared code should be refactored out into dependencies, as in Factor II. This is a valid argument, but the overhead of separating dependencies and testing them individually is not worth the cost for most small teams. The pattern of building a series of components of a distributed system from a common codebase - Of having one monorepo that produces m

Base role with limit in inherited roles

Suppose, we have an inherited role, inherited_role which inherits from two roles role1 and role2 which are defined as the following manner:

{
  "select_permissions": [
       {
         "role": "role1",
 "permission": {

Synchronized Output

Synchronized output is merely implementing the feature as inspired by iTerm2 synchronized output, except that it's not using the rare DCS but rather the well known SM ? and RM ?. iTerm2 has now also adopted to use the new syntax instead of using DCS.

Semantics

When rendering the screen of the terminal, the Emulator usually iterates through each visible grid cell and renders its current state. With applications updating the screen a at higher frequency this can cause tearing.

This mode attempts to mitigate that.

Clone the repo.
Use git rebase -i --root
vim will open. Select the commits you want to modify by changing pick to edit. If you would like to change all the commits, perform the following replace: :%s/^pick/edit/g. This command changes all instances of "pick" at the start of lines to "edit".
You will now be shown all the selected commits one by one. Each commit message will be displayed. You have two options:
- If you would like to keep the commit author details the same, do a git rebase --continue.
- If you would like to change it to a different name/email, do git commit --amend --reset-author. If --reset-author is specified, it will use the details from your git config. (If you need to specify an alternate name/email, you can do so with --author="John Doe <[email protected]>". If you would like to change the time to a previous date, you can do so with --date "2 days ago".)
Do the same for all the commits and finish the rebase.
Perform git push -f origin master to

Interactive rebase off of a point earlier in the history than the commit you need to modify (git rebase -i <earliercommit>). In the list of commits being rebased, change the text from pick to edit next to the hash of the one you want to modify. Then when git prompts you to change the commit, use this:

git commit --amend --reset-author --no-edit

For example, if your commit history is A-B-C-D-E-F with F as HEAD, and you want to change the author of C and D, then you would...

Update author's info git config --global user.email [email protected]
Specify git rebase -i B (here is an example of what you will see after executing the git rebase -i B command)

How Nix works

Nix is a purely functional package manager

/nix folder in my dotfiles repo

this is how I utilize nix to have better management of initial setup in terms of both logically and performantely better

How I package Docker image using Nix

My first attempt to package with Nix for a Docker image with Dockerfile

From Homebrew to Home Manager

	// Run with node --expose-gc bench.js ../automerge-paper.json.gz
	// automerge-paper.json.gz from https://github.com/josephg/crdt-benchmarks

	// Read in a patch file and check that the patches all apply correctly.
	const fs = require('fs')
	const assert = require('assert')
	const zlib = require('zlib')
	const automerge = require('automerge')
	const v8 = require('v8')

	class BQDatasetAuthorizer(ContextDecorator):
	def __init__(self, target, profile_file):
	self.target = target
	self.profile_file = profile_file
	# this dict maps a dataset to a list of BigQuery Access entries defined by code.
	# We expect groupByEmail and View.
	# https://googleapis.dev/python/bigquery/latest/generated/google.cloud.bigquery.dataset.AccessEntry.html
	self.auth_dict = defaultdict(list)

	def __enter__(self):

	#!/usr/bin/env ruby
	# Generate a dbdiagram for dbdiagram.io from a dbt project.
	#
	# Usage:
	# 1. Run `dbt docs generate` first.
	# 2. Run `dbt_to_dbdiagram.rb`
	# 3. Paste the output in https://dbdiagram.io/

	require 'yaml'
	require 'json'

	#!/bin/bash

	## Change following to '0' for output to be like ls and '1' for eza features
	# Don't list implied . and .. by default with -a
	dot=0
	# Show human readable file sizes by default
	hru=1
	# Show file sizes in decimal (1KB=1000 bytes) as opposed to binary units (1KiB=1024 bytes)
	meb=0
	# Don't show group column