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
Set WEB_CONCURRENCY_SET_BY=heroku/ruby if WEB_CONCURRENCY gets auto-set (heroku#1700)
* Set WEB_CONCURRENCY_SET_BY=heroku/ruby if WEB_CONCURRENCY gets auto-set
The Ruby buildpack sets the `WEB_CONCURRENCY` env var at app boot based on the
current dyno size if the (deprecated) `SENSIBLE_DEFAULTS` mode is enabled, 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/ruby` to allow the app, other boot time
scripts, or humans more easily differentiate between a user and a buildpack
provided `WEB_CONCURRENCY` (and 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
to ignore `WEB_CONCURRENCY` in cases 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-nodejs#932heroku/heroku-buildpack-python#2015
GUS-W-20882005
* Track SENSIBLE_DEFAULTS usage
This feature is deprecated, let's see how many people still rely on it.
---------
Signed-off-by: Richard Schneeman <rschneeman@salesforce.com>
Co-authored-by: Richard Schneeman <rschneeman@salesforce.com>
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
+
- Set `WEB_CONCURRENCY_SET_BY=heroku/ruby` if `WEB_CONCURRENCY` gets set in (deprecated) `SENSIBLE_DEFAULTS` mode (https://github.com/heroku/heroku-buildpack-ruby/pull/1700)
5
6
- Default Node.js version now 24.13.0 (https://github.com/heroku/heroku-buildpack-ruby/pull/1704)
setup_profiled(ruby_layer_path: "$HOME",gem_layer_path: "$HOME",ruby_version: @ruby_version,default_config_vars: default_config_vars)# $HOME is set to /app at run time
116
+
setup_profiled(ruby_layer_path: "$HOME",gem_layer_path: "$HOME",ruby_version: @ruby_version,default_config_vars: default_config_vars,report: @report)# $HOME is set to /app at run time
add_to_profiled(web_concurrency,filename: "WEB_CONCURRENCY.sh",mode: "w")# always write that file, even if its empty (meaning no defaults apply), for interop with other buildpacks - and we overwrite the file rather than appending (which is the default)
setup_profiled(ruby_layer_path: "$HOME",gem_layer_path: "$HOME",ruby_version: @ruby_version,default_config_vars: default_config_vars)# $HOME is set to /app at run time
18
+
setup_profiled(ruby_layer_path: "$HOME",gem_layer_path: "$HOME",ruby_version: @ruby_version,default_config_vars: default_config_vars,report: @report)# $HOME is set to /app at run time
0 commit comments