34
54
2
CryptoJS 3.x AES encryption/decryption on client side with Javascript and on server side with PHP
Better Battlelog legacy code and legacy website. It was fun :)
A zero dependency, cross browser library to easily get or set/manipulate form input values as/from a json object.
Optimized fuzzy omnibox history search for chrome - Like firefox quick history search
Events
updated logo added forceOpened parameter to sidebar
working on the docs
working on docs removed unnecessary install steps for builds
Setting custom PHP Path, especially used for process-isolation in PhpUnit
I run PHPUnit 10 unit tests with process-isolation. I have a custom PHP script ona custom path (which enables xdebug and run as different user by passing it through various su commands). I can start the tests with this custom binary, but all subsquent tests fail, because PhpUnit runs each test isolated, but with the default binary path, which do not have the required parameter and preparations properly set.
I need to define a PHP binary path in PhpUnit which will be used by PhpUnit, instead of the default from the OS.
I have found a way locally, with introducing a constant PHPUNIT_PHP_BINARY_PATH and adding the following code before the line in https://github.com/sebastianbergmann/environment/blob/6b148eed05f3c7a66923242a333b19653323368a/src/Runtime.php#L92
if (defined('PHPUNIT_PHP_BINARY_PATH')) {
self::$binary = escapeshellarg(PHPUNIT_PHP_BINARY_PATH);
self::$initialized = true;
return self::$binary;
}
Maybe this would be better to utilize with a cmdline parameter to make sure it's set before any code is executed.
I would really appriciate this customization for more flexible way to interact with process isolation.
Setting custom PHP Path, especially used for process-isolation in PhpUnit
Ok. Thanks for that fast answer.
Setting custom PHP Path, especially used for process-isolation in PhpUnit
I run PHPUnit 10 unit tests with process-isolation. I have a custom PHP script ona custom path (which enables xdebug and run as different user by passing it through various su commands). I can start the tests with this custom binary, but all subsquent tests fail, because PhpUnit runs each test isolated, but with the default binary path, which do not have the required parameter and preparations properly set.
I need to define a PHP binary path in PhpUnit which will be used by PhpUnit, instead of the default from the OS.
I have found a way locally, with introducing a constant PHPUNIT_PHP_BINARY_PATH and adding the following code before the line in https://github.com/sebastianbergmann/environment/blob/6b148eed05f3c7a66923242a333b19653323368a/src/Runtime.php#L92
if (defined('PHPUNIT_PHP_BINARY_PATH')) {
self::$binary = escapeshellarg(PHPUNIT_PHP_BINARY_PATH);
self::$initialized = true;
return self::$binary;
}
Maybe this would be better to utilize with a cmdline parameter to make sure it's set before any code is executed.
I would really appriciate this customization for more flexible way to interact with process isolation.
updates for 4.0.0-alpha.1
updated readme
added right sidebar for docs
include FramelixDocs into build removed unused script parameters
added docs and starter module fixed and optimized a lot in build, test and deploy process removed unused stuff from core
optimized build process for dev image
fixed hardcoded image name
fixed hardcoded image name
streamlined build process streamlined test process reimplemented docker push added dev image to docker hub use dev image in github tests
fixed expires headers when cachable files are served via php backend
fixed playwright test message
fixed phpunit tests because of wrong permissions for files
fixed phpunit tests because of wrong permissions for files
fixed phpunit tests because of wrong permissions for files
fixed phpunit tests because of wrong permissions for files
changed test order to fix issues with failed phpunit tests because of no setup
fixed missing /run/php folder stop container if php-fpm couldn't be started
initial
improved build process for more speed
