The Phar Installation and Verification Environment (PHIVE)
Installation and verification of phar distributed PHP applications has never been this easy!
Adding all the required tools like PHPUnit, PHPMD and phpDox in their matching versions to a project used to be a lot of repetitive work: Started by finding the download URL, figuring out what the actually correct and matching version is followed by verifying the sha1 and gpg signatures and making the archive executable. And of course you'd have to repeat this very thing for every tool needed.
Alternatively, you could have used composer. And cluttered your project's dependencies with the ones of your tools. And fight their potential dependency conflicts.
No more! Now you can rely on PHIVE to install and manage your project's tooling needs without all the hassle and without cluttered dependencies!
Installation of PHIVE is easy and about the last time you have to do anything phar related manually. Grab your copy of PHIVE from the releases section at our GitHub page or follow these simple steps:
wget -O phive.phar "https://phar.io/releases/phive.phar" wget -O phive.phar.asc "https://phar.io/releases/phive.phar.asc" gpg --keyserver hkps.pool.sks-keyservers.net --recv-keys 0x9D8A98B29B2D5D79 gpg --verify phive.phar.asc phive.phar rm phive.phar.asc chmod +x phive.phar mv phive.phar /usr/local/bin/phive
Once installed, PHIVE is ready for action. Some example invocations are shown below:
phive install phpunit phive install --copy phpdox phive install phpdox bin/phpdox phive install https://phar.phpunit.de/phpunit-4.8.6.phar phive install --temporary [email protected]~5.0 phive update phive update --prefer-offline phive update phpunit
How it works
PHIVE makes installation easy by downloading the phar archive from the given location, including the verification of the certificate supplied by the server. Once downloaded, the archive's SHA1/SHA256/SHA512 hash is verified and so its OpenPGP/GnuPG or OpenSSL signature.
Instead of redownloading the same phar multiple times, the archive is kept at a shared location (by default in
and only a symbolic link is created for the project. You can of course also explicitly request a copy of the phar to
be made in favor of symbolic links (use
PHIVE and phar.io are open source projects released under the BSD license. You are welcome to join the development team!
*Note that all licence references and agreements mentioned in the Phive README section above are relevant to that project's source code only.