Is there any way to read env vars from a .env file?

[svanharmelen]

I've noticed #226 but I'm not able to get cargo watch to use my .env file. My setup involves a workspace, so next to placing the .env file in the root of the crate I'm trying to watch I also tried to place it in root of the workspace. But it didn't work in either of the cases...

Tried to search the docs/repo, but other then the one issue I can't seem to find much to go on. Would be really, really nice to be able to use my .env file, as I need quite a few vars to be set.

Thanks!

[passcod]

Not yet!

[svanharmelen]

Wow, your fast 😃 My next question was going to be if you are open for a PR to support it and then I was going try and make some coming weekend... But I guess I don't have to anymore ❤️

One additional question after looking at the PR; would it be possible revert the logic using the same style as the --no-dot-ignores and --no-vcs-ignores flags? So on by default if an .env file is in the current working directory. And then maybe keep the --env-file flag for if you want to point to a custom file.

IMHO that would make the PR "feature complete" in terms of .env file support 😊

[passcod]

No, reading the .env by default would be unexpected, I think. Generally that's done by the application in development, not by the process parent. One advantage to doing it in the application is that it's reloaded on each run, whereas this option by necessity only loads it once at instantiation.

[svanharmelen]

That's indeed a fair point! Then indeed the flag you proposed is a good alternative that would work fine for us 👍🏻

[passcod]

Released in 8.3.0

[svanharmelen]

Thank you very much for the quick response and implementation!! Going to try it right away...