Debugging Broken Buildpacks?
Hey all, what's the best way to debug buildpacks? I've been using the Heroku one since I migrated my app from Heroku, but it started failing recently by saying Ruby 3 didn't exist on the heroku-20 stack and to consider using heroku-20 isntead (π). I switched to nix, but the builds take over 10 minutes and seemingly fail to download nixpkgs from GitHub.
I'm guessing there isn't an ongoing issue, but I'm not sure exactly how to debug and fix these errors. Hoping for some guidance!
2 Replies
Thats kinda the reason why we have Nixpacks, Heroku can publish breaking changes and break builds upstream.
Project id please so we can debug the nix issues?
Toggling back and forth between them seemed to fix things! I was seeing the issues here: 4df77cb0-c746-47a4-9691-94b57940c859