Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:125991
Content-Type: multipart/alternative;
 boundary="------------slupVtSl00WZG4DpAAnunlmD"
Message-ID: <6ee2c71d-11e6-453f-b7e2-c94b131ad844@scriptfusion.com>
Date: Tue, 19 Nov 2024 12:59:36 +0000
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PHP-DEV] Better development streamlining of the built-in server
To: internals@lists.php.net
References: <ad167a80-89eb-4f42-b61d-56b4fb2ff780@email.android.com>
Content-Language: en-GB
In-Reply-To: <ad167a80-89eb-4f42-b61d-56b4fb2ff780@email.android.com>
From: bilge@scriptfusion.com (Bilge)

This is a multi-part message in MIME format.
--------------slupVtSl00WZG4DpAAnunlmD
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 19/11/2024 12:52, John D'Orazio wrote:
> My point is, would the built-in server ever be used for anything other 
> than local development? If not, then it would be a simple convenience 
> to developers to have an automatic environment variable of 
> "development" when launching the built-in server. Instead of manually 
> creating this environment variable, it would just be there.

As a matter of best practice, an application should not need to know 
which environment it is running in, let alone be designed specifically 
to respond to the PHP built-in server.

Cheers,
Bilge

--------------slupVtSl00WZG4DpAAnunlmD
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <div class="moz-cite-prefix">On 19/11/2024 12:52, John D'Orazio
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:ad167a80-89eb-4f42-b61d-56b4fb2ff780@email.android.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">
        <div dir="auto">
          <div class="gmail_extra" dir="auto">My point is, would the
            built-in server ever be used for anything other than local
            development? If not, then it would be a simple convenience
            to developers to have an automatic environment variable of
            "development" when launching the built-in server. Instead of
            manually creating this environment variable, it would just
            be there.</div>
        </div>
      </div>
    </blockquote>
    <p>As a matter of best practice, an application should not need to
      know which environment it is running in, let alone be designed
      specifically to respond to the PHP built-in server.</p>
    <p>Cheers,<br>
      Bilge<br>
    </p>
  </body>
</html>

--------------slupVtSl00WZG4DpAAnunlmD--