From b47ca8b8769883557ac1ef62a6fb1cd815f08fb6 Mon Sep 17 00:00:00 2001
From: William Carroll <wpcarro@gmail.com>
Date: Thu, 6 Feb 2020 21:39:23 +0000
Subject: Support lorri

From what I currently understand, lorri is a tool (sponsored by Target) that
uses nix and direnv to build and switch between environments quickly and
easily.

When you run `lorri init` inside of a directory, lorri creates a shell.nix and
an .envrc file. The .envrc file calls `eval "$(lorri direnv)"` and the shell.nix
calls `<nixpkgs>.mkShell`, which creates a shell environment exposing
dependencies on $PATH and environment variables. lorri uses direnv to ensure
that $PATH and the environment variables are available depending on your CWD.

lorri becomes especially powerful because of Emacs's `direnv-mode`, which
ensures that Emacs buffers can access anything exposed by direnv as well.

I still need to learn more about how lorri works and how it will affect my
workflow, but I'm enjoying what I've seen thus far, and I'm optimistic about the
road ahead.
---
 .envrc               |  8 +-------
 monzo_ynab/.envrc    |  5 +++++
 monzo_ynab/shell.nix |  9 +++++++++
 shell.nix            | 14 ++++++++++++++
 4 files changed, 29 insertions(+), 7 deletions(-)
 create mode 100644 monzo_ynab/shell.nix
 create mode 100644 shell.nix

diff --git a/.envrc b/.envrc
index 1e44420ed401..051d09d292a8 100644
--- a/.envrc
+++ b/.envrc
@@ -1,7 +1 @@
-export BRIEFCASE=~/briefcase
-export DEPOT=~/depot
-export NIXPKGS=$HOME/nixpkgs
-export DESKTOP=zeno.lon.corp.google.com
-export LAPTOP=seneca
-export CLOUDTOP=wpcarro.c.googlers.com
-NIX_PATH=nixpkgs=$NIXPKGS:depot=$DEPOT:briefcase=$BRIEFCASE
+eval "$(lorri direnv)"
diff --git a/monzo_ynab/.envrc b/monzo_ynab/.envrc
index 265077343800..121cc134de18 100644
--- a/monzo_ynab/.envrc
+++ b/monzo_ynab/.envrc
@@ -1,5 +1,10 @@
 # source_up traversing up directories until it finds the nearest .envrc file,
 # which it uses to extend the environment in this .envrc.
+#
+# Since ../.envrc calls `eval "$(lorri direnv)"`, the buildInputs and variables
+# definitions inside of the attribute set passed to pkgs.mkShell become
+# available here as well.
 source_up
 export client_id="$(pass show finance/monzo/client-id)"
 export client_secret="$(pass show finance/monzo/client-secret)"
+eval "$(lorri direnv)"
diff --git a/monzo_ynab/shell.nix b/monzo_ynab/shell.nix
new file mode 100644
index 000000000000..836718d85f29
--- /dev/null
+++ b/monzo_ynab/shell.nix
@@ -0,0 +1,9 @@
+{ pkgs ? import <nixpkgs> {}, ... }:
+
+pkgs.mkShell {
+  buildInputs = [
+    pkgs.go
+    pkgs.goimports
+    pkgs.godef
+  ];
+}
diff --git a/shell.nix b/shell.nix
new file mode 100644
index 000000000000..ef8960b822db
--- /dev/null
+++ b/shell.nix
@@ -0,0 +1,14 @@
+{ pkgs ? import <nixpkgs> {}, ... }:
+
+pkgs.mkShell rec {
+  buildInputs = [];
+  # TODO(wpcarro): How does pkgs.mkShell handle exported and non-exported
+  # variable definitions?
+  BRIEFCASE = builtins.toPath ~/briefcase;
+  DEPOT = builtins.toPath ~/depot;
+  NIXPKGS = builtins.toPath ~/nixpkgs;
+  NIX_PATH="nixpkgs=${NIXPKGS}:depot=${DEPOT}:briefcase=${BRIEFCASE}";
+  DESKTOP = "zeno.lon.corp.google.com";
+  LAPTOP = "seneca";
+  CLOUDTOP = "wpcarro.c.googlers.com";
+}
-- 
cgit 1.4.1