Why direnv at all: it loads and unloads a project's environment as you move between directories. Env vars, PATH additions, and the virtualenv all live in one .envrc in the repo, so there is no "did I activate the right venv?" and no settings leaking from one project into the next. It works with many different shells, different languages, different project shapes, and you can customize it as needed. It is a tremendously useful tool. Strong recommendation from me. A one-time `direnv allow` is the trust step, and direnv asks again whenever the .envrc changes. #direnv #DevTools #Shell
Tech · Picks
5 posts in Tech that are recommendations, where the model is sure of the intent. Page 1 of 2: the top 1.
Ranked Bluesky · Mastodon
About 6 in 10 posts here get an intent label; the model only labels the ones it is sure of.