Newly created Git repository with does not deploy to Netlify (error: spawn EACCES) about one-click-hugo-cms

[talves]

@DotTech I personally remove the hugo bin folder and this is one of the reasons why I would do so. You will have to run your own local version of Hugo to have the command work for development.

See my answer on StackOverflow.

[DotTech]

Thank you @talves!
Removing the bin folder solves the build issue.
I still don't understand why it does work with the cloned repository...
But at least I have a way of getting it to work now :)

[talves]

It does sound a little odd to me also.

[DotTech]

I have found a solution that allows Hugo to stay in the repo without interfering with the Netlify build:

• I added the environment variable HUGO_VERSION = "0.46" to the netlify.toml file
• I've updated gulpfile.babel.js like this:

// Replace this line:
// const hugoBin = `./bin/hugo.${process.platform === "win32" ? "exe" : process.platform}`;

// With this:
var hugoBin = `./bin/hugo.${process.platform === "win32" ? "exe" : process.platform}`;
if (process.env.HUGO_VERSION) {
  hugoBin = 'hugo'
}

That way the bin folder Hugo will be used locally and ignored during a Netlify build.
I'll try to create a pull request for this.

[talves]

This is a good way to handle it. Keeps a unique version of Hugo in each project for local and targets the correct version of Hugo for Netlify. Would allow for multiple versions to run on your local machine, when needed.

Gives me an idea to run diff versions local out of a global scope (install dir).
hugo/root/location/0.45/hugo.exe

if (process.env.HUGO_VERSION) {
  if (process.env.NODE_ENV === 'development') {
    hugoBin = path.resolve(HugoRootLocation, process.env.HUGO_VERSION, 'hugo')
  } else {
    hugoBin = 'hugo'
  }
}