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
Currently, the buildpack always install both apache and nginx, even though each app will use only one of them, increasing the slug size for nothing. It would be great if the unused one could be skipped during the install.
I see 2 alternatives:
the nice one: automatically detect which server is used based on the commands used in the Procfile
the manual one: allow configuring somewhere (maybe a setting in the extra section in composer.json) which server should be installed (defaulting to install both if this is not configured)
The text was updated successfully, but these errors were encountered:
The issue with approach 1 is that a lot of users have custom startup scripts, compound commands, etc, so there'd always have to be an alternative way.
I too have been thinking about an extra entry, but I am also looking into it for the in-progress PHP CNB, where we can maybe have users control this via project.toml metadata instead (and actually have the web servers supplied by a separate buildpack that gets used automatically but can also be combined with e.g. other language buildpacks).
Currently, the buildpack always install both
apache
andnginx
, even though each app will use only one of them, increasing the slug size for nothing. It would be great if the unused one could be skipped during the install.I see 2 alternatives:
extra
section in composer.json) which server should be installed (defaulting to install both if this is not configured)The text was updated successfully, but these errors were encountered: