TIL that #phive https://github.com/phar-io/phive is part of @ddev π³ How AWESOME is that!? <3
cc @theseer
@heiglandreas @naderman @Schrank @packagist Which versions of the dev tools do I need to install to be able to use them without composer? Dev tools via composer is a convenience on installation, but can become a pain if new packages get blocked because dev tools have a certain package with a constrain.
I had a few issues with #phive in CI some years ago. I should give it a try again.
TIL that #phive https://github.com/phar-io/phive is part of @ddev π³ How AWESOME is that!? <3
cc @theseer
Half of my CI jobs fail due to "Trying to connect to keys.openpgp.org" when using #Phive to download tools.
I would use #Psalm as a Composer dependency, if I could, but it depends on an older version of #AMPHP than my project uses, so I'm installing it with Phive.
But this intermittent error is frustrating me. π€¬
@ramsey @OndrejMirtes Imho there are three options:
1) you install somehow the plugins and have some kind of autoloading before running phar (I have no clue how to do this)
2) you have a directory `tools` or something with a composer.json for your tools, so you are independent of your project composer
3) you compile your own phar files (which is like 2) but with more hassle :D)
Good luck and I'm happy to read the blog article!
P.S. #phive without plugin is awesome π
I want to try to get past this, so I'm going to bite the bullet and finally learn how to use #Phive.
If I install #PsalmPHP or #PHPStan via Phive, how to I install plugins like psalm/plugin-phpunit and phpstan/phpstan-phpunit. I can't use `composer require` on these, since they also require the "parent" packages.
@theseer, any pointers?
Parramatta Library is quite an amazing building now π
I got phive on it
Grab your phars that you need
I got phive on it.
Not messin with deps conflict sh*t
I got phive on it
If security concerns let you bide
I got #phive on it.
It has verifications deep inside