i have never used the env section in cargo. I just use .env files as its what i am used to, and they work the same way across the programming languages i work with day to day (js, c# and rust). One thing i can think of where .env probably has an advantage is for local overrides or additions. Then you can wire up .env.local and have it be ignored by version control. That way, you or your team mates, dont accidentally check in your personal development settings.
This is so cool. Thank you so much.
Thanks for watching :)
Great teching rust video dude. I am waiting you add the login and register too for this one 😂
haha ey, im working on it. Need to write the article first 🙈
I think the docker run command needs -p 5432:5432, or at least mine did.
Yeah one need to map the inside port to the outside port to reach it. Sorry for being unclear and thanks for clarifying 👊
Is there a meaningful difference between using dotenvy and just adding .cargo/config.toml with an [env] section?
i have never used the env section in cargo. I just use .env files as its what i am used to, and they work the same way across the programming languages i work with day to day (js, c# and rust). One thing i can think of where .env probably has an advantage is for local overrides or additions. Then you can wire up .env.local and have it be ignored by version control. That way, you or your team mates, dont accidentally check in your personal development settings.