(PH)ing (I)s (N)ot (G)NU make; it's a PHP project build system or build tool based on Apache Ant. You can do anything with it that you could do with a traditional build system like GNU make, and its use of simple XML build files and extensible PHP "task" classes make it an easy-to-use and highly flexible build framework.
Features include running PHPUnit tests (including test result and coverage reports), file transformations (e.g. token replacement, XSLT transformation, Smarty template transformations), file system operations, interactive build support, SQL execution, SVN/GIT operations, tools for creating PEAR packages, documentation generation (DocBlox, PhpDocumentor) and much, much more.
If you find yourself writing custom scripts to handle the packaging, deploying, or testing of your applications, then we suggest looking at Phing. Phing comes packaged with numerous out-of-the-box operation modules (tasks), and an easy-to-use OO model to extend or add your own custom tasks.
Phing provides the following features:
- Simple XML buildfiles
- Rich set of provided tasks
- Easily extendable via PHP classes
- Platform-independent: works on UNIX, Windows, Mac OSX
Details of the latest version can be found on the Phing homepage https://www.phing.info/.
Phing 3.x is compatible with PHP 5.6 and higher.
- Composer
The preferred method to install Phing is through Composer.
Add phing/phing to the
require-dev or require section of your project's composer.json
configuration file, and run 'composer install':
{
"require-dev": {
"phing/phing": "3.0.x-dev"
}
}
- Phar
Download the Phar archive. The archive can then be executed by running:
$ php phing-latest.phar
To successfully run all Phing tests, the following conditions have to be met:
- PEAR installed, channel "pear.phing.info" discovered
- Packages "python-docutils" and "subversion" installed
- php.ini setting "phar.readonly" set to "Off"
Then, perform the following steps (on a clone/fork of Phing):
$ composer install
$ cd test
$ ../bin/phing
Documentation is available in various formats in the docs/docbook5/en/output directory (generated from DocBook sources located in docs/docbook5/en/source).
For online documentation, you can also visit the Phing website: https://www.phing.info/
This software is licensed under the terms you may find in the file named "LICENSE" in this directory.
Thank you for using PHING!
- Twitter: @phingofficial
- Website: https://www.phing.info
- Slack: https://www.phing.info/slack/
- IRC: Freenode, #phing
- GitHub: https://www.github.com/phingofficial/phing
- E-mail: [email protected] (mailing list)
We welcome contributions! Please keep your pull requests clean and concise: squash commits, don't introduce unnecessary (whitespace) changes, use verbose commit messages.
Phing's source code is formatted according to the PSR-2 standard.
If you like Phing, we accept donations through Flattr. All donations will be used to help cover the costs for hosting the Phing site.
If you are contributing code to the Phing project and want to use PhpStorm for development feel free to ask Michiel (mrook AT php DOT net) for our Open Source License.
Proud to use: