ENOENT error on both nodester and heroku about wheat

[woloski]

to workaround you could execute spawn a child process and execute git pack-refs before the sever starts.
I'm wondering how you are running it in ec2? do you expose the repo and push there? how you do that?
I'm running it in Windows Azure and I had to setup a bare repo on startup and create a post-hook on github pointing to my blog to trigger a fetch to update. Am I missing something?

[aaronfay]

I believe this issue is related to creationix/node-git#6, although the pull request hasn't been accepted yet. I'm experiencing the exact error deploying to Heroku.

EDIT
I take back my comment, the issue on Heroku seems to be more complex, as the dyno /app folder is not the 'gitFolder' git-fs is expecting, so a few files are missing, as well as related repo information. At this point I'm not sure there's an easy fix for this, as Heroku's deployment seems to obscure the actual cloned repository. Restarts also appear to wipe out any files written to the app folder as well.

[aaronfay]

After a little more research, it appears this issue cannot be fixed. The actual files deployed on a Heroku dyno instance are only the project files without the .git folder. A wheat dependency (git-fs) is expecting to find the .git repo in place so it can read shasums (see https://github.com/creationix/node-git/blob/master/lib/git-fs.js#L115). At this point 'gitDir' is the project directory, and neither the 'packed-refs' or 'HEAD' files exist. Even if they did, they wouldn't have the proper content, I suspect.