about summary refs log tree commit diff
path: root/playbooks
AgeCommit message (Collapse)AuthorFilesLines
2020-07-26 Create //playbooks/sqlite3.mdWilliam Carroll1-0/+115
Write a playbook for using SQLite to capture some trivia that I often forget in between my ~infrequent uses of SQLite.
2020-07-26 Create //playbooks/shell.mdWilliam Carroll1-0/+12
Taken from the overview: > I'm making this as an offline reference for some of the commands that I use > often enough to need to remember but not often enough to *actually* remember.
2020-07-24 Add two steps to finances playbookWilliam Carroll1-0/+2
I needed to add the first step since I dipped into my Emergency fund last month to pay for someone to prepare my US tax return. I added the other step as a reminder.
2020-07-24 Fix typo in finances playbookWilliam Carroll1-1/+1
amount -> amounts
2020-07-20 Create //playbooksWilliam Carroll7-0/+180
I'm particularly excited about this idea. As I was reading Graham's "Erase your darlings" blog post, I had an idea: I should have playbooks at the root of my monorepo. I can have playbooks for the following: - How to install NixOS - How to build GCR images from Nix expressions - A collection of miscellaneous shell commands (e.g. "how to kill a process by name") - What series of steps should I follow when I receive a paycheck I already keep README's at the root of each package, which I think is where many of these instructions belong. Other tutorials that I write for myself that do not belong to any package can go in //playbooks. I also will host my personal habits in //playbooks since habits are a bit like playbooks for life. Let's see how this idea ages as the caffeine wears off...