Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:128688
Content-Type: text/plain; charset=utf-8; format=flowed
Message-ID: <1757711671678.1086196219.1095125491@yahoo.de>
To: s.sayakci@gmail.com
Cc: internals@lists.php.net
Subject: Re: [PHP-DEV] Environment Variable based PHP Extension loading
Date: Fri, 12 Sep 2025 21:21:11 +0000
In-Reply-To: <CAA6rDWBCqMGg-KF59ENkDb+D4GZMHfkurWRned1cjdcZ6mDmww@mail.gmail.com>
References: <CAA6rDWBCqMGg-KF59ENkDb+D4GZMHfkurWRned1cjdcZ6mDmww@mail.gmail.com>
User-Agent: Vivaldi Mail/7.5.3735.66
Content-Transfer-Encoding: 7bit
Precedence: list
MIME-Version: 1.0
From: hanskrentel@yahoo.de (Hans Krentel)




On Friday 12 September 2025 22:13:04 (+02:00), Soner Sayakci wrote:

 > Hey,
 > 
 > I would like to load PHP extensions by environment variables in a
 > containerized environment. All existing solutions are moving files in an
 > entrypoint and this does not work for read-only containers. Why this?
 > Extensions like Blackfire/XDebug/OpenTelemetry/Tideways do not like each 
to
 > run at the same time, and having to build less containers simplifies a 
lot.
 > 
 > It's already possible to use environment variables in the php.ini like 
so:
 > 
 > extension=${PHP_PROFILER}
 > 
 > So it's possible to toggle the extensions already, the only thing that 
is
 > not working is passing an empty string (I don't want any profiler). Then 
we
 > get warnings like: Warning: PHP Startup: Unable to load dynamic library 
'"

A warning is only a warning. You likely want to see it if the parameter is 
empty as it is *likely* unexpected.

 > 
 > Therefore I opened a pull request to ignore extension entries with empty
 > strings, so this works with that case too. Looking for feedback in the 
pull
 > request https://github.com/php/php-src/pull/19816

Commented there with the long version + a small nitpick as your report is 
wrong for the directive and the extensions you reference above: Those are 
all Zend extensions, not just ordinariy extensions. However: If you provie 
a non-zero-length-string for an extension you get a much more enhanced 
diagnostic message about which files have tried. In your empty string case, 
not more files have been tried. So please feel free to add more rationale 
what kind of issue is causing you the warning.

Otherwise I'm not really booked on the fact that providing an empty 
directive value per an ini file can astute a non-warning on any directive 
that configures the PHP runtime.

Especially as you give the use-case of a build procedure here, double check 
you're not trying to solve a problem in your build procedure by 
(needlessly) suppressing PHP binary diagnostics --- you should be able to 
suppress on your end given the SUCCESS exit code.

What do you think=

-- hakre