Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move to phive to install dev toolings #125

Open
shochdoerfer opened this issue Oct 21, 2018 · 1 comment
Open

Move to phive to install dev toolings #125

shochdoerfer opened this issue Oct 21, 2018 · 1 comment

Comments

@shochdoerfer
Copy link
Member

We should make use of PHIVE to install dev toolings like phpstan, phpdocumentor, php-coveralls.

@heiglandreas
Copy link
Member

I'm currently more inclined to use tm/tooly-composer-script as

  1. that is configured using the already used composer.json (so one config file less in the already cluttered main directory)
  2. it can load all required tools and not a subset of tools that the folks of PHIVE have whitelisted (OK. Phive seems to be able to install any tool using a fixed URL, but then it's not better than curl, so why use another tool. And signature-validation then has to be done manually)

Verification against a signature is done by both tools.

And in combination with the getlatestassets-API it is possible to specify exactly which version of the tools you explicitly want for tools that have their releases hosted on github.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants