Hi Rich,
I really appreciate you looking into it and confirming the issue so quickly. It's great to know a ticket is already in the works. I'll keep an eye out for the fix in ProGet 2024.39.
Thanks again for your help!
– Matthias
Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Hi Rich,
I really appreciate you looking into it and confirming the issue so quickly. It's great to know a ticket is already in the works. I'll keep an eye out for the fix in ProGet 2024.39.
Thanks again for your help!
– Matthias
Hi there,
I'm using ProGet to host a Composer feed and I've run into a problem when using packages that provide vendor binaries like PHPStan.
The package metadata ProGet delivers at [FEED]/p2/phpstan/phpstan.json
is missing the "bin"
key that defines the vendor binaries.
That means that Composer will not create links to these binaries in vendor/bin
, and calling them using e.g. vendor/bin/phpstan
does not work.
I made sure that the composer.json
in the imported package contains the "bin"
key. It also doesn't matter if I add the package through the browser or via the drop path of the feed.
Thank you for your time.
-- Matthias
According to https://docs.inedo.com/docs/proget/feeds/other-types the Composer feed type is planned for a maintenance release of ProGet 2024, which is great news!
We're currently using Satis for PHP packages alongside ProGet (for NuGet, npm, Python). Working with Satis is a bit cumbersome, that's why we would very much prefer using ProGet for PHP packages, too.
Satis downloads the distribution zips for all packages and generates a static site with package metadata and the zips. I guess ProGet will handle Composer feeds in a similar fashion?
Feel free to reach out to me via email if you need further feedback or beta testers for the Composer feed type.