We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider an app with an index.js and a Procfile with contents like:
index.js
Procfile
worker: node index.js
When running a build with heroku/builder:24, this results an image with two processes:
heroku/builder:24
web: node index.js worker: bash -c node index.js
This is probably unexpected for the user. There is an extra process, and the extra web process is unlikely to accept http connections anyway.
web
My feeling is that we should probably avoid adding processes if we know the the procfile buildpack was detected and is part of the build plan.
The text was updated successfully, but these errors were encountered:
Related issue: heroku/buildpacks-go#85
Sorry, something went wrong.
No branches or pull requests
Consider an app with an
index.js
and aProcfile
with contents like:When running a build with
heroku/builder:24
, this results an image with two processes:This is probably unexpected for the user. There is an extra process, and the extra
web
process is unlikely to accept http connections anyway.My feeling is that we should probably avoid adding processes if we know the the procfile buildpack was detected and is part of the build plan.
The text was updated successfully, but these errors were encountered: