tvl-depot/monzo_ynab/.envrc

# 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 monzo_client_id="$(pass show finance/monzo/client-id)"
export monzo_client_secret="$(pass show finance/monzo/client-secret)"
export ynab_personal_access_token="$(pass show finance/youneedabudget.com/personal-access-token)"
eval "$(lorri direnv)"
Inherit parent's .envrc variables I discovered direnv's convenient `source_up` function today. I needed it to inherit the values defined in ~/briefcase/.envrc, and it's working exactly as I expected it would. What a fine piece of software direnv is. 2020-02-06 00:26:57 +01:00			`# source_up traversing up directories until it finds the nearest .envrc file,`
			`# which it uses to extend the environment in this .envrc.`
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. 2020-02-06 22:39:23 +01:00			`#`
			# 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.`
Inherit parent's .envrc variables I discovered direnv's convenient `source_up` function today. I needed it to inherit the values defined in ~/briefcase/.envrc, and it's working exactly as I expected it would. What a fine piece of software direnv is. 2020-02-06 00:26:57 +01:00			`source_up`
Support YNAB personal-access-token Define my YNAB personal access token as an environment variable. Prefix Monzo environment variables with "monzo_" to more easily differentiate between Monzo credentials and YNAB credentials. 2020-02-07 22:30:24 +01:00			`export monzo_client_id="$(pass show finance/monzo/client-id)"`
			`export monzo_client_secret="$(pass show finance/monzo/client-secret)"`
			`export ynab_personal_access_token="$(pass show finance/youneedabudget.com/personal-access-token)"`
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. 2020-02-06 22:39:23 +01:00			`eval "$(lorri direnv)"`