Env file not loaded when specified full-path

[ddollar]

Env file not loaded when specified full-path

[ddollar]

Does ${PWD} contain a space?

[bartmeuris]

No it does not - the example above was in tested in /home/vagrant

[tehbilly]

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.

[bartmeuris]

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)

[jmervine]

Mind including the output for the following commands:

1. echo $PWD
2. pwd
3. echo "forego start -f ProcFile.test -e ${PWD}/testenv" << redundant, but still

Also try: forego start -f ProcFile.test -e /home/vagrant/testenv (per your comments above).

[paulmelnikow]

I can reproduce this on Mac OS X Yosemite 10.10.5.

Works (i.e. spits out the ADMIN keys I expect):

forego run -e .env env | grep ADMIN
forego run -e ./.env env | grep ADMIN

Doesn't work:

forego run -e ~/.code/core/.env env | grep ADMIN
forego run -e /Users/pnm/code/core/.env env | grep ADMIN

$ echo "$PWD"
/Users/pnm/code/core
$ pwd
/Users/pnm/code/core
$ forego run -e ${PWD}/.env env | grep ADMIN
$ forego run -e /Users/pnm/code/core/.env env | grep ADMIN

[paulmelnikow]

Ah, this works for me in 4eaf541, can you push a release?