diff options
author | William Carroll <wpcarro@gmail.com> | 2020-07-20T09·26+0100 |
---|---|---|
committer | William Carroll <wpcarro@gmail.com> | 2020-07-20T13·38+0100 |
commit | c6106f7884fab3048ccce14dd56a193e706fbaac (patch) | |
tree | 473254a350490ce6956a656370fe695bf7cb0bdf /website | |
parent | 5add8ddc13be3a7a5fbb6deb3f70cb18594f8750 (diff) |
Create //playbooks
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...
Diffstat (limited to 'website')
-rw-r--r-- | website/habits/default.nix | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/website/habits/default.nix b/website/habits/default.nix index 71329c7963d5..c9e56bb0e828 100644 --- a/website/habits/default.nix +++ b/website/habits/default.nix @@ -2,7 +2,7 @@ pkgs.stdenv.mkDerivation { name = "habits-webpage"; - src = builtins.path { path ../../org; name = "org"; }; + src = builtins.path { path = ../../playbooks; name = "playbooks"; }; buildInputs = []; buildPhase = '' ${pkgs.pandoc}/bin/pandoc $src/habits.org -o index.html |