Re: Better development streamlining of the built-in server
| From: | John D'Orazio | Date: | Tue, 19 Nov 2024 13:26:13 +0000 |
| Subject: | Re: Better development streamlining of the built-in server | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-125992@lists.php.net to get a copy of this message | ||
I don't understand why an application should not know which environment it is running in? You
should be able to instruct a frontend where to look for a backend, depending on the environment it
is running in. What best practice are you referring to? And may I ask why the PHP built-in server
was created in the first place, if we already have Apache and Nginx server environments? Is it not a
convenient for development environments?On Nov 19, 2024 1:59 PM, Bilge
<bilge@scriptfusion.com> wrote:
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