Inability to run env-cmd without npx in Ubuntu 18.04 about env-cmd HOT 4 CLOSED

One more thing I found, is that if I attempt to run with npx and an absolute file path, I get the same error.

I also changed the permissions so that anyone can view and edit both the directory and file. And there was no change in behavior.

from env-cmd.

A quick note, I was able to get it running using npx and the default .env file location.

from env-cmd.

After a few attempts I was unable to reproduce your issue. The the permission errors sound like either incorrect permissions on the files themselves or maybe env-cmd was globally installed by accident and that global install location is having permissions issues. Honestly, when it comes to permission errors there are a million different things it could be. Glad you found some way to make it work 😄

Tested this out in docker on ubuntu 18.04 with default apt-get installs of both nodejs and npm:

Thank you for reporting this. There might be something to this as you are not the first to report similar permission issues in linux (#33). Both of these issues might be related, but I have not been able to reproduce either case. Thank you also for cross-posting from SO. I honestly never check SO, though I probably should from time-to-time now that the lib is getting a bit more popular.

from env-cmd.

Closing due to inactivity and an inability to reproduce this issue at this time.

from env-cmd.