tfenv VS nodeenv

You'll need the correct version of Terraform (the version of Terraform used for apply can be found in terraform_version at the beginning of the .tfstate file), to switch between versions I recommend tfenv.

For almost four years I'd been using a Macbook as my main work machine. One quality of life tool I'd gotten used to was tfenv, a lovely little tool for managing terraform versions & quickly switching between them.

For example terraform state files often have non backwards compatible changes. You should consider using something like tfenv so everyone on your team has identical versions of terraform.

I'm using the tool tfenv to manage Terraform versions. Other tools can do that. You can use asdf, too. I saw that asdf can do more than manage Terraform versions.

Documentacion TFENV

git clone https://github.com/tfutils/tfenv.git ~/.tfenv export PATH="$HOME/.tfenv/bin:$PATH" # install to appropriate shell startup file, e.g. $HOME/.bashrc echo 'export PATH="$HOME/.tfenv/bin:$PATH"' >> ~/.profile

This must be something new, because I had to install nodeenv to manage NPM dependencies in a project-specific way: https://github.com/ekalinin/nodeenv

I have a Python-based web app that I'm trying to package as a setuptools package so that it can be installed using pip and/or python setup.py xxxxx. This web app also contains static files for a React front end. I use webpack (and therefore node.js) to generate the JavaScript bundle for the website. I'm trying to figure out the most pythonic way to package this. From googling around a bit, I found nodeenv which seems relevant.

Maybe nodeenv?

- Node: https://github.com/ekalinin/nodeenv