-
Notifications
You must be signed in to change notification settings - Fork 431
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot get Shell-expanded strings working but falls short for me by design anyway #2240
Comments
Can you use unexport ENV |
Thanks for your response. Well, any interaction manually managing shell vars is what I am avoiding for the same reason: it means humans making mistakes from settings which are out of sight in a terminal session on their machine. We can assume we already have indicated what env we intend with afeldkamp's example I understand the |
Oh, one other thing, you can override just variables on the command line by putting the overrides after just ENV=dev test In the above command, |
Thanks for your reply. I don't see how I can load an environment file globally using that: This example by afeldkamp is an example of what I am looking for. It feels like to me that
Maybe I could call another recipe in the dependency of every recipe to set up variables for global env settings... IDK if that would work. Overall, variable scope limitations are coming up against |
Ah, sorry, you're right. Yah, just environment variables won't work there. Can you do |
Thanks for help with a good option; I will try it. |
Like many have requested, I am looking for a tool that is configurable globally per environment.
I have just v1.30 on Mac OS arm M1
As in this discussion this justfile fails:
error: Dotenv file not found
I see that implementation wasn't taken, now, still opting for
x${VAR}
- but the ask was for just vars and there is an important distinction.One issue I am attempting to solve with
just
is to get away from explicitly handling environment variables.Having them in a include file is fine, but I absolutely do not want to have to define them in my shell, before executing
just
nor do I want to do funny things with them at all likeMYENV=dev just test
What I want to do with a command line is this:
just test dev
or at least
just test -e dev
Inside the just file I don't mind environment variables - I just don't want to pollute my shell, and then accidentally burn down prod one day b/c of an env var left about.
There is a real economy in the expressive form I am looking for which
just
is ever so close to supporting, butjust
doesn't.Thanks.
The text was updated successfully, but these errors were encountered: