Like many of you, I work on a lot of different projects. Even when a project is less serious—hey, I should check out this new JS framework!—I strive to reduce the friction involved with setting up the project's dev environment to the absolute bare minimum possible.
In JavaScript/Node world, we usually store scripts in package.json and run them using npm. In other worlds, we use Makefile or create a directory and put all our scripts there. But there is a better way to manage and run scripts for your team. No, I’m not talking about Warp or other pricey fancy tools. I will share about direnv and our old friend bash: How we are using them to effectively write and manage scripts as a team.
unclutter your .profile. Contribute to direnv/direnv development by creating an account on GitHub.
Like many of you, I work on a lot of different projects. Even when a project is less serious—hey, I should check out this new JS framework!—I strive to reduce the friction involved with setting up the project's dev environment to the absolute bare minimum possible.
steen's online burrow
Easily using uv, direnv, and minimal, consistent .envrc files
Igor's internet home page and blog
I was setting up a new Python project with direnv to manage environment variables. Suddenly python wasn’t found, even though it was definitely installed. Here’s what happened and how I fixed it. The problem Link to heading I’d been using direnv happily for months, managing API keys and secrets per project. Then I added a custom PATH in my .envrc and broke everything: # This was the problem export PATH=/some/custom/path Running which python returned nothing. Even python3 was gone. My shell couldn’t find Python at all.