tvl-depot/website/habits/default.nix

{ pkgs, ... }:

pkgs.stdenv.mkDerivation {
  name = "habits-webpage";
  src = builtins.path { path = ../../playbooks; name = "playbooks"; };
  buildInputs = [];
  buildPhase = ''
    ${pkgs.pandoc}/bin/pandoc $src/habits.org -o index.html
  '';
  installPhase = ''
    mv index.html $out
  '';
}
Publish habits as a webpage I think it might be a good idea to version control my habits, so that I can audit them as they change. I'm publishing these on my website, so that I can refer to them wherever I had internet. 2020-03-27 16:55:26 +01:00			`{ pkgs, ... }:`

			`pkgs.stdenv.mkDerivation {`
			`name = "habits-webpage";`
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... 2020-07-20 11:26:12 +02:00			`src = builtins.path { path = ../../playbooks; name = "playbooks"; };`
Publish habits as a webpage I think it might be a good idea to version control my habits, so that I can audit them as they change. I'm publishing these on my website, so that I can refer to them wherever I had internet. 2020-03-27 16:55:26 +01:00			`buildInputs = [];`
			`buildPhase = ''`
			`${pkgs.pandoc}/bin/pandoc $src/habits.org -o index.html`
			`'';`
			`installPhase = ''`
			`mv index.html $out`
			`'';`
			`}`