P H I N G
Thank you for using PHING!
(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 unit tests (including test result and coverage reports), file transformations (e.g. token replacement, XSLT transformation, template transformations), file system operations, interactive build support, SQL execution, Git/Subversion operations, tools for creating PEAR packages, documentation generation (PhpDocumentor, ApiGen) 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. Pre-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
- Works on Linux, Mac & Windows
- No required external dependencies
- Runs great on PHP 7
The Latest Version
Details of the latest version can be found on the Phing homepage
https://www.phing.info/.
Supported PHP versions
Phing 3.x is compatible with PHP 7.1 and higher.
Installation
- 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
- Docker (experimental)
The official Phing Docker image can be found on Docker Hub.
To execute Phing inside a container and execute build.xml located in /home/user, run the following:
$ docker run --rm -v /home/user:/opt phing/phing:3.0 -f /opt/build.xml
Documentation
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/
Donations
Developing and maintaining Phing has cost many hours over the years. If you want to show your appreciation, you can use one of the following methods to donate something to the project maintainer, Michiel Rook:
Thank you!
Contributing
We love contributions!
Help us spot & fix bugs
We greatly appreciate it when users report issues or come up with feature requests. However, there are a few guidelines you should observe before submitting a new issue:
- Make sure the issue has not already been submitted, by searching through the list of (closed) issues.
- Support and installation questions should be asked on Twitter, Slack or IRC, not filed as issues.
- Give a good description of the problem, this also includes the necessary steps to reproduce the problem!
- If you have a solution - please tell us! This doesn't have to be code. We appreciate any snippets, thoughts, ideas, etc that can help us resolve the issue.
Issues can be reported on GitHub.
Pull requests
The best way to submit code to Phing is to make a Pull Request on GitHub.
Please help us merge your contribution quickly and keep your pull requests clean and concise: squash commits and don't introduce unnecessary (whitespace) changes.
Phing's source code is formatted according to the PSR-2 standard.
Running the (unit) tests
If you'd like to contribute code to Phing, please make sure you run the tests before submitting your pull request. 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
Licensing
This software is licensed under the terms you may find in the file
named "LICENSE" in this directory.
Proud to use:
