thanks for posting the resolution! I did not know about that difference in behavior for the .slugignore file (that's going in my notes).
I also have not played around with making a buildpack yet, so my note on that is "you can create a custom buildpack to help you debug issues". Actually, if you don't mind pushing that verbose buildpack out to github, I'd love to check it out, and see how it works. I've been helping students with a variety of technical backgrounds with their heroku deployments, and sometimes they get themselves into some interesting situations that are not easy to tease out at first, and having a verbose buildpack like this might really cut down on the amount of time spent trying to 'guess' at what the issue is. Also, I wonder what questions we could have asked you that would have lead us to your .slugignore situation. "Do you have any other projects using these tools that are working ok?" Followed by "What is different about this project vs. those?" "If you create a new project from scratch, using the same versions of these tools, do you have the same problem?" Thanks again for posting the outcome, its enormously valuable for the rest of us. On Thu, Mar 22, 2012 at 10:16 PM, Andrew Lorente <[email protected]>wrote: > haha YES, simulsolve > > > On Thu, Mar 22, 2012 at 8:13 PM, Karl <[email protected]> wrote: > >> Well, I figured it out. The problem is with my .slugignore file. In >> .slugignore I had: >> >> spec/**/* >> >> assets/**/* >> >> >> Why? I used to keep some photoshop files in there. But the /assets folder >> doen't exist any more. >> >> The problem? It appears that when .slugignore is processed is does NOT >> behave like .gitignore and in my case above it ignored *all* *folders*with >> the name of 'assets', >> *all* *files* with the name of 'assets', regardless of location. Thus >> public/assets and all it's contents were removed from the slug before asset >> compilation, thus it didn't detect manifest.yml because it was removed. >> >> The only way I was able to figure this out was by creating a custom >> buildback with copious 'puts' to watch what was happening during the entire >> slug compilation process. Man, what a waste of too, too many hours. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Heroku" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/heroku/-/mmahX0niEnUJ. >> >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/heroku?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- Thanks, -John -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
