Ignore directory .env, keep searching

[joneskoo]

Without this, autoenv thinks a directory is a file and
asks to allow executing it. Autoenv only works for
regular files.

URL: http://www.gnu.org/software/bash/manual/html_node/Bash-Conditional-Expressions.html

[joneskoo]

@flebel I'm not sure about that. I prefer actually getting an error if .env turned unreadable.

If .env is a directory, I think it makes sense to ignore it as it, duh, isn't an env-file. When the permissions don't allow reading it, I think including a parent .env file instead without error could be confusing. In that case it's better to be explicit and show that there was a permissions issue. Besides if permissions were later changed, a different env-file would be found. After my pull request, with unreadable file:

grant:~ joneskoo $ cd test
shasum: /Users/joneskoo/test/.env: 
-bash: /Users/joneskoo/test/.env: Permission denied

I think this is reasonable.

If .env is a directory, it is silently ignored and the parent directory is searched for an env-file recursively like the .env directory didn't exist.

[dasJ]

+1

[kennethreitz]

✨ 🍰 ✨