-
Notifications
You must be signed in to change notification settings - Fork 175
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
Env file not loaded when specified full-path #49
Comments
Does ${PWD} contain a space? |
No it does not - the example above was in tested in |
Question, what platform are you trying this on? I wasn't able to duplicate this on my Arch box or my Windows machine. That's not entirely true, I was able to replicate it on Windows inside of cygwin, but nowhere else. |
I tested this in Ubuntu 14.04 in Vagrant (and in an Ubuntu 14.04 Docker container where I first encountered the problem, and was able to replicate it in a VM). Note that I also tried typing out the complete path (so it's not the ${PWD} substitution) |
Mind including the output for the following commands:
Also try: |
I can reproduce this on Mac OS X Yosemite 10.10.5. Works (i.e. spits out the ADMIN keys I expect):
Doesn't work:
|
Ah, this works for me in 4eaf541, can you push a release? |
On Linux, using version 0.15.0, when you specify the full-path to the environment file to load, it fails. When specifying a relative path, it works:
ProcFile.test:
testenv:
Starting with these files normally just works:
When Specifying full-path for the env file, the environment variables are not loaded:
This used to work correctly in 0.13.1
The text was updated successfully, but these errors were encountered: