tvl-depot/monzo_ynab/shell.nix

{ pkgs, briefcase, ... }:

pkgs.mkShell {
  buildInputs = [
    pkgs.go
    pkgs.goimports
    pkgs.godef
    briefcase.monzo_ynab.job
    briefcase.monzo_ynab.tokens
  ];
}
Remove default values for Nix expression parameters I'm not sure if this commit breaks everything in my monorepo. I think it will. Why am I doing this? Perhaps it's a bad idea. I don't fully understand how readTree works. My ignorance is costing me hours of time spent debugging. In an effort to better understand readTree, I'm removing the default values for my Nix expression parameters, which I believe have preventing errors from surfacing. 2020-02-23 23:29:32 +01:00			`{ pkgs, briefcase, ... }:`
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
			`pkgs.mkShell {`
			`buildInputs = [`
			`pkgs.go`
			`pkgs.goimports`
			`pkgs.godef`
Nixify tokens.go - Package tokens.go with Nix - Add monzo_ynab.{job,tokens} to shell.nix 2020-02-09 14:50:44 +01:00			`briefcase.monzo_ynab.job`
			`briefcase.monzo_ynab.tokens`
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			`];`
			`}`