Replies: 1 comment
-
Thanks for the edit! This got me running, but my previous issues still come up when trying to run a test of notifications on heroku. Any luck with figuring this out? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Was able to get it working on Heroku by doing the following:
Procfile
in the root directory of the project and add the following line:worker: npm run start:production
We use
worker
or else Heroku will timeout by attempting to bind to aport
. Also notice we're using thestart:production
target. When you push to Heroku, your code is already compiled bytsc
.puppeteer
args in themain
function inindex.ts
Manually add
https://github.com/jontewks/puppeteer-heroku-buildpack
to the "buildpacks" listOriginally posted by @gperl27 in #497 (comment)
Hello,
After following the tuto to deploy on heroku, i have this error when i run the job:
Run echo | docker login ghcr.io -u $GITHUB_ACTOR --password-stdin
Error: Cannot perform an interactive login from a non TTY device
Error: Process completed with exit code 1.
Do you have any idea why ? i thought i can just run the app on the console (btw i used the worker dyno formation) but i have this :
2020-12-13T00:10:31.700851+00:00 app[worker.1]: Calling _exit(1). Core file will not be generated.
2020-12-13T00:10:31.700851+00:00 app[worker.1]:
2020-12-13T00:10:31.700852+00:00 app[worker.1]:
2020-12-13T00:10:31.700852+00:00 app[worker.1]: TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md
2020-12-13T00:10:31.700853+00:00 app[worker.1]: {
2020-12-13T00:10:31.700861+00:00 app[worker.1]: "stack": "Error: Failed to launch the browser process!\n[1213/001031.207622:FATAL:zygote_host_impl_linux.cc(117)] No usable sandbox!
but i update the puppeteer :( i'm lost
Beta Was this translation helpful? Give feedback.
All reactions