Releases: totten/pogo
Releases · totten/pogo
Release v0.5.0
- Allow the
--dl
and#!depdir
paths to use more variables - Generate more helper scripts (useful for exporting/debugging as full project)
- Fix handling of 'pogo --phar --out=subdir/plainname'
Release v0.4.1
Do not participate in Symfony's SHELL_VERBOSITY
.
Release v0.4.0
Update compatibility for PHP 8.1 and PHP 8.2. Update dependencies. Drop PHP 5.6.
Release v0.3.0
Add the phar
subcommand. This will generate an executable PHAR archive with bundled dependencies. Example workflow:
$ pogo --phar my-script.php
Loading composer repositories with package information
Updating dependencies (including require-dev)
...
Generating my-script.phar from my-script.php
$ ./my-script.phar dave
good morning: dave
Release v0.2.4
Improve support for debugging pogo-scripts in IDE:
- Add the
dbg
command (pogo --dbg myfile.php
) which runs the script in a more debuggable way:- Launch in the
require
mode (which avoids extraneous subprocesses and preserves code-locations for breakpoints) - Place downloaded PHP assets in a folder adjacent to
myfile.php
- Launch in the
composer
subprocesses shouldn't use XDebug (unless they've opted-in)
Release v0.2.3
Add support for setting the default location of the downloaded dependencies via pragma, e.g.
#!depdir <path>
#!depdir /tmp/foo
#!depdir ../var/cache/foo
#!depdir .deps
Release v0.2.2
Fix injection of pogo_*()
functions when using local
runner with PHAR based build.
Release v0.2.1
Update argv
handling in local
runners to work with symfony/console
-based scripts.
Release v0.2.0
Rework all runners. Now, the choice is between:
isolate
: The target script runs in a separate PHP process frompogo
. This type of usage has one generally-good implementation (PrependRunner
) based onphp -d auto_prepend_file=...
.local
: The target script runs in the same PHP process aspogo
. This has two implementations (RequireRunner
andEvalRunner
), which differ in quality of support for backtraces/debugging/shebangs.
Release v0.1.1
- Add support for
--dl=_SCRIPT_DIR/foo/bar
. This is useful if you (e.g.) have a git repo with a dozen distinct scripts, and you want all of them to put there builds in an adjacent folder. - Add runtime helper
pogo_script_dir()