Support `.env` files from the VSCode Extension

[Lagoja]

[hbouhadji]

+1 please

[mohsenari]

@hbouhadji I can add this fairly quick. Can you expand on what is your desired outcome with regards to .env files and the vscode extension?

[hbouhadji]

@mohsenari

Pretty much like said in this command -> https://github.com/jetify-com/devbox/issues/407#issuecomment-1670640386

I want to add variables to a .env file like this:

NGINX_WEB_PORT=8081
NGINX_WEB_ROOT=../../../devbox.d/web

and be able to run devbox services up without having to specify the --env-file for each command or using direnv

maybe by adding a env_file to the devbox.json ?

I don't use vscode specifically but since #407 is closed i though this issue represent my need the most

[hbouhadji]

The end goal is to let my collaborators overwrite some vars if needed with a not versioned file (like the web_port)