Calling netlify sites inside ~ causes error about cli

[loicteixeira]

I ran into the same issue running netlify deploy.

Deploying folder: /app/var/build
{ Error: EISDIR: illegal operation on a directory, read
    at Object.fs.readSync (fs.js:675:18)
    at tryReadSync (fs.js:540:20)
    at Object.fs.readFileSync (fs.js:583:19)
    at readLocalConfig (/app/node_modules/netlify-cli/lib/settings/config.js:19:2)
    at Config.writeLocalConfig (/app/node_modules/netlify-cli/lib/settings/config.js:72:15)
    at /app/node_modules/netlify-cli/lib/commands/deploy.js:116:16
    at tryCatchReject (/app/node_modules/when/lib/makePromise.js:845:30)
    at runContinuation1 (/app/node_modules/when/lib/makePromise.js:804:4)
    at Fulfilled.when (/app/node_modules/when/lib/makePromise.js:592:4)
    at Pending.run (/app/node_modules/when/lib/makePromise.js:483:13) errno: -21, code: 'EISDIR', syscall: 'read' }
Error during deploy:  EISDIR: illegal operation on a directory, read

I believe it is because netlify first saves the global config at ~/.netlify/config (so ~/.netlify/ is a directory) and then try to save the local config at ~/.netlify (as a file). Unfortunately, as you can see the paths are currently hardcoded so there's not much we can do unless the package is updated to make sure the paths don't clash or, the user can supply custom config paths

[bcomnes]

This should be addressed in the upcoming 2.0.0 release.