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

"Supported Tools" section #138

Open
MacDada opened this issue Jul 24, 2023 · 4 comments
Open

"Supported Tools" section #138

MacDada opened this issue Jul 24, 2023 · 4 comments

Comments

@MacDada
Copy link

MacDada commented Jul 24, 2023

Many famous PHP tools can already be installed via PhiVE […] .... and many more!

So, the questions is: which ones exactly? Or: how do I find out?

I mean: it is my question, but also a suggestion to add the answer to the website ;-)

@theseer
Copy link
Member

theseer commented Jul 24, 2023

Valid Point.

But not easy to answer a question: As PHIVE deliberately does not have a central registry, there is no way to know what tools are "supported" per se. You can install everytihng via url, github- or gitlab project refeence ( e,g. vendor/project).

We also do have an alias-database - where phive list would dump all - but that's only those that bothered to register an alias.

So what would you suggest would be the best way to pro-actively answer your question on the website?

@MacDada
Copy link
Author

MacDada commented Jul 24, 2023

what would you suggest would be the best way to pro-actively answer your question on the website?

Just mention exactly what you answered me :)

  • Check the built–in alias database: phive list.
  • Check at your favourite tool website if it supports Phive (does it need to support it "proactively" somehow? I still don't know that).
  • Install anything via url, github/gitlab project reference (e,g. vendor/project).

@theseer
Copy link
Member

theseer commented Jul 24, 2023

Check at your favourite tool website if it supports Phive (does it need to support it "proactively" somehow? I still don't know that).

Nothing phive specifc actually. When using github/gitlab, it needs to provide a .phar on for a release as an attachment - obviously, otherwise phive can't do anything. And it should provide a .phar.asc with a valid signature, which would require a publicly available public gpg key (preferably on keys.openpgp.org). "Should" as one could install unsigned phars (when persuade phive with --force-accept-unsigned , but that almost kills the point of using phive ;)

I'll try to update the website later today:)

@MacDada
Copy link
Author

MacDada commented Jul 24, 2023

I'll try to update the website later today:)

Cool, thanks for your explanations and the Phive itself :) I'm pretty sure it has its place in the PHP tool env, it just needs to be a bit more polished, so that it's actually easier to understand and use the tool than to work without it :D

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