Put a one-line description of your project here.
Follow the steps in this section to complete the customization of your new project.
Enable those services shown below that have not already been configured:
Feature | Setup |
---|---|
Collaborative repository | DONE |
Linux permutation testing | DONE |
Windows testing | DONE |
Static analysis | DONE |
Code coverage | Enable Coveralls |
Package manager | Register with Packagist |
Dependency updates | Enable Dependencies.io |
To customize the name of your commandline tool:
- Rename the file
example
(the executable / front controller) - Replace any
example
orexample.phar
in box.json.dist and .gitignore with the desired name for your phar
To automatically attach a .phar (or some other build result) to every GitHub release:
- Run
travis setup releases
and answer the prompts. Answer "yes" to all yes/no questions. - Edit resulting
.travis.yml
file to include the missingskip_cleanup:
andtags:
directives.
When you are done, the deploy:
section should look something like this:
deploy:
provider: releases
api_key:
secure: KmKwmt...[REDACTED]...LlE=
file: example.phar
skip_cleanup: true
on:
tags: true
repo: greg-1-anderson/starter-test-65
The secure:
line should be filled in by travis setup releases
.
Once you have finished setting up your project, delete this section and fill out the other sections of this README.
Explain how to get a copy of this project up and running on a new user's local machine.
See deployment for notes on how to deploy the project on a live system.
List the things that are needed to install the software and how to install them. For most PHP projects, it should usually be sufficient to run:
composer install
If you wish to build the phar for this project, install the box
phar builder via:
composer phar:install-tools
Provide a step by step series of examples that show how to install this project.
Say what the step will be. If the phar for this project is the primary output, and not a mere development utility, then perhaps the first step will be to build the phar:
composer phar:build
It may then be sufficient to install via:
cp example.phar /usr/local/bin
End with an example of getting some data out of the system or using it for a little demo.
The test suite may be run locally by way of some simple composer scripts:
Test | Command |
---|---|
Run all tests | composer test |
PHPUnit tests | composer unit |
PHP linter | composer lint |
Code style | composer cs |
Fix style errors | composer cbf |
Add additional notes about how to deploy this on a live system.
If your project has been set up to automatically deploy its .phar with every GitHub release, then you will be able to deploy by the following procedure:
- Edit the
VERSION
file to contain the version to release, and commit the change. - Run
composer release
Include all that apply:
Please read CONTRIBUTING.md for details on the process for submitting pull requests to us.
We use SemVer for versioning. For the versions available, see the tags on this repository.
- Greg Anderson - created project from template.
See also the list of contributors who participated in this project.
This project is licensed under the MIT License - see the LICENSE file for details
- Hat tip to anyone who's code was used
- Inspiration
- etc
- Thanks to PurpleBooth for the example README template