You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Python buildpack sets the `WEB_CONCURRENCY` env var at app boot
based on the current dyno size, so long as the user hasn't specified
a custom value via the app's config vars.
Now, in addition to setting the `WEB_CONCURRENCY` env var, the buildpack
will also set `WEB_CONCURRENCY_SET_BY=heroku/python` to allow the app,
other boot time scripts, or humans more easily differentiate between
user and buildpack provided `WEB_CONCURRENCY` values (plus determine
which buildpack actually set it).
In addition to assisting with debugging, this allows for UX improvements
in other buildpacks such as the PHP buildpack, which can now check for
`WEB_CONCURRENCY_SET_BY` in its boot time Apache/Nginx `heroku-php-...`
scripts - helping detect the case where users have ordered the buildpacks
on their app in the wrong order. (The "primary" language is supposed to be
listed last, otherwise the wrong concurrency value will be used.)
See also:
- heroku/heroku-buildpack-php#883
- heroku/heroku-buildpack-nodejs#932
- heroku/heroku-buildpack-ruby#1700GUS-W-20866598.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,7 @@
2
2
3
3
## [Unreleased]
4
4
5
+
- The web server concurrency calculation profile script now sets the env var `WEB_CONCURRENCY_SET_BY="heroku/python"` if `WEB_CONCURRENCY` was set automatically by the buildpack. ([#2015](https://github.com/heroku/heroku-buildpack-python/pull/2015))
0 commit comments