Closed asmeurer closed 1 year ago
Ah, this accidentally leaked the access token (GitHub automatically revoked it). I'll need to regenerate it if I ever get either render or Heroku working again.
They were able to fix the internal error. Now the render deploy fails with
Dec 9 03:03:10 PM Dockerfile.render:25
Dec 9 03:03:10 PM --------------------
Dec 9 03:03:10 PM 23 | # in place. We then run the apply-buildpacks.py script here because, unlike our
Dec 9 03:03:10 PM 24 | # `v2` image, this allows us to expose build-time env vars to your app.
Dec 9 03:03:10 PM 25 | >>> RUN /render/build-scripts/apply-buildpacks.py ${HEROKU_STACK}
Dec 9 03:03:10 PM 26 |
Dec 9 03:03:10 PM 27 | # We strongly recommend that you package a Procfile with your application, but
Dec 9 03:03:10 PM --------------------
Dec 9 03:03:10 PM error: failed to solve: process "/bin/bash -c /render/build-scripts/apply-buildpacks.py ${HEROKU_STACK}" did not complete successfully: exit code: 1
Not sure what is going on there.
replit seems to be working for now. But I think if we decide to stick with it we will need to implement logging manually.
I missed the relevant part of the build log which was higher up. I needed to update the Python version. The deploy is working now. I need to add credentials to render to see if it will work.
I've successfully moved the live bot from Heroku to Render. Assuming there are no issues in the next few days I am going to merge this.
The deploy failed because of some render error. There doesn't seem to be any sort of log for why it failed. It says it's an internal error, suggesting it's a problem on their side.