Posts made by dubrsl_1715

@stevedennis said in PHP Composer feed connect to vcs type repository or how to upload:

A "pointer to a Git commit" seems convenient at first, but there's a good reason that many ecosystems (including Composer) have moved away from it

I haven't heard anything about this. Can you show me proof?

-- ultimately it's just not scalable and doesn't handle team workflows very effectively.

So you're saying that keeping everything in zip archives is better than keeping it in git? Did I understand you correctly? (The question is related to Composer)

I don't agree with the workflow you propose regarding composer. We won't be able to use ProGet without additional git integration. And if I additionally have to maintain and develop software that will provide seamless git integration, then the question arises: why should I pay for ProGet?
There may be other benefits of ProGet. I am continuing the test implementation.

Hi,

I'm trying to migrate our php composer repositories to ProGet. We currently use satis for private repositories. And I'm having problems.

Composer can receive packages from VCS repositories https://getcomposer.org/doc/05-repositories.md#vcs. And this is convenient for private repositories. In ProGet I did not find such type of connector for composer. :(

This is due to the fact that ProGet receives metadata from composer.json, which should be in a zip archive https://docs.inedo.com/docs/proget/feeds/composer. And if all other metadata can be kept there, then specifying the version in composer.json and committing to git is not convenient. And usually no one does this. There are many branches, tags and composer works fine without a version in composer.json. Repackaging a zip archive, as suggested in the documentation, is also not possible, because its hash will differ from the one in git. And changing the hash leads to recreating composer.lock.
Specifying the version in the archive name is also not an option. The version format is much wider than the file name format. I have branches and tags that have / in their name.

Is it possible to upload metadata separately from the archive?
Or maybe you can suggest another solution?

Thank you!