Mot
does your `package.json` have a hardcoded `-f .env.production` in your start scripts?
Can you add the --debug flag and see what added detail that gets you? Doesnt seem like this is dotenvx behavior but maybe this is some crazy edge case.
strange. will take a look. you ran this in JavaScript frontend or Node.js?
thank you for catching this. fix happening here: https://github.com/dotenvx/dotenvx/pull/352
released as `1.10.2`. let me know if you still run into any issues, but i think you should be good now.
i can't reproduce this yet. where is your gitleaks installed - can you run `which gitleaks` ? also, if you run `gitleaks detect -v 2>&1` directly, what output do you...
going to close this as i cannot reproduce. let me know if you find out more @BenJackGill and can share and we can re-open.
> but it doesn't feel great to specify the environment twice this way in the case that you already have set that variable. In fact, in some situations that stage...
@ameduza can you describe how you host projectA right now and plan to host projectB? i can answer better based on that. if it's cloud hosting this shouldn't be a...
> The only solution I can imagine for me would be to store private keys in .env.keys files for both projects and include file location into the run command. Yes,...