Releases: PhpGt/Server
Multi-threaded server
Better debug setup
This is a minor patch release. For users that do not have the xdebug.conf file loaded by default in the php.ini setup for speed reasons, this adds the debug/profile ini flags by default.
Included in this release also is the compatibility with IPv6 addresses.
What's Changed
- IPv6 filtering by @g105b in #13
- build: hard dependencies by @g105b in #14
- Set up debugging properly by @g105b in #15
Full Changelog: v1.1.3...v1.1.4
Enable Xdebug with --debug flag
This release exposes the --debug
flag, which in turn sets the -dzend_extension=xdebug.so
ini setting when executing the server process.
Cli namespace standardisation
This patch release simply refactors the namespace that holds the Cli Commands from Command
to Cli
for consistency with other repositories.
Debugger, CI and type safety
It's now possible to enable XDebug straight from a command line argument --debug
.
Now as standard all PHP.Gt repositories follow phpstan level 6 analysis, all type safety has been addressed.
Upgrades to the CI runners.
PHP 7.4 compatibility
Since the introduction of PHP 7.4, the way sub-processes are handled in PHP is a lot cleaner and more manageable. This release upgrades to the new execution model, which means that if the serve
command is executed from within another PHP process, the server will no longer be left hanging after the parent process is terminated.
Stable release
There hasn't been much development on this repository because it has such a simple responsibility: to run the inbuilt PHP webserver, using go.php
as the router script.
It's been included in the PHP.Gt/Installer package for months now, so a stable release is due to unlock WebEngine's stable v3 release.
Working prototype
There is very little responsibility to the preamble to v1 of this repository; the server script simply calls PHP's inbuilt server using php -S 0.0.0.0:8080
, with a few settings wrapped using Gt/Cli.
There are plans for implementing a PSR compatible Http Server in this repository, but until then, no further features are planned in the v1 release, so unless any bugs are detected with this implementation, a v1 release will be made when the next product running WebEngine is complete and deployed, as another real-world test.