Closed scruti closed 8 years ago
Interesting. I'll have to read about it a bit more, I don't have much time now.
@ukd1 @smathieu @paul: thoughts?
FYI, we just decided to deprecate Fourchette. You can (and probably should) use the Heroku review apps instead which was inspired by Fourchette.
https://devcenter.heroku.com/articles/github-integration-review-apps
Thanks!
Closing this, due to deprecation of Fourchette! So long and thanks for all the fish!
Resolves rainforestapp/fourchette#24
Trying to use Fourchette with our Rails app, I run in a recurrent error: Fork app was created, DB data was copied, PR message was generated, but the generated fork was showing a standard "Welcome to Heroku app..." message.
Checking logs I found there was an error during the Tarball process. I spent one day trying everything. Checking hooks, tracing the generated urls through Fourchette methods calls, checking the Heroku's API call, deleting the Fourchette app and configuring it again... Nothing worked, we always had the same problem. Though maybe was a naming problem, but running an
heroku run 'ls tmp'
wasn't showing any tarball file.Finally I found the cause:
This is a
tar
command error, doesn't seem to be too serious issue since is related to file reading and seems to appear randomly, and I can guess that is related to generation on tarball inside the same folder that we're compressing. So I read about how to solve it: http://www.ensode.net/roller/dheffelfinger/entry/tar_failing_with_error_message About the--ignore-failed-read
flag don't worry, is not a "I will ignore everything", it just:After found that I tested it aliasing
tar
totar --ignore-failed-read
with a callback at our Fourchette app:Since then it's working! Fourchette is generating correctly the forks for our PRs and we had a little party in the office :tada:
I marked that it resolves the closed Issue rainforestapp/fourchette#24 , because even he's complaining about Node.js build, actually the cause of his build failing was the same as ours:
Our full trace: