Caching source packages stored on local git server

[fduch]

Hi all!

We are using our own git server with gitweb interface to mirror public repositories and store private repositories in our company. Than we'd like to handle packages with our own local packagist instance due to big packages amount.

The main goal is to make packages cachable and to clone git repository only once during the first package installation on the "client side" (developer's machine, ci-server, etc).
In order to do this we need archive copies of tagged versions of packages and package manager that adds dist metadata (distType, distUrl, etc) to the package info.

In case of packagist it means that corresponding VCSDriver should be able to provide dist information. Nowadays there are only two drivers doing this stuff (GitBitbucketDriver, GitHubDriver), but we can't use one of them because of handling our own git server (not bitbucket, not github). It is possible to create archives of the tagged versions for the projects on the gitweb side so it would be cool if i can create custom GitWebDriver to provide packages with dist information referenced to archives prepared with gitweb on company's git server. But there is no chance to provide such custom vcs driver without patching of composer (am i right?). So than I've also tried to "pretend" our git-storage to the local packagist by a github-server (by adding the hostname of the local git server to the list of github-domains using corresponding composer option), but it was unsuccessful because of github-related url's of the packages / dist's (obviously i can write some url rewrite rules for nginx in order to translate github-styled url's into internal ones, but it is not the best idea).

I know that in case of Satis this problem is successfully solved by archive configuration directive so i eventually can place satis in front of packagist in order to cache all the packages on satis-level, but it seems to be overcharged to have both satis and packagist simultaneously installed.

So is there any chance to deal with dist packages (and cache them) in case of composer + packagist + local git server?

[stof]

using the archive system in packagist is in the roadmap. So it will probably become available at some point

[fduch]

Thanks, @stof. Are there some common recomendations how to deal with packagist and local git server now, when archive system is not available?

[fduch]

@Seldaek, @naderman, any thoughts?

[lisachenko]

+1 for this issue, looking for the way to enable caching (serving dists) with custom git browser. @Seldaek could you suggest possible workarounds until archive system will be supported?

[naderman]

The only thing I'd currently recommend is to use satis - do you really need a full packagist setup?

[fduch]

Thanks, @naderman. Using packagist is preferable due to flexible user management and automated packages submitting support

[lisachenko]

@naderman agree with @fduch that satis is not well suited for enterprise. How can we add this functionality to the packagist?

[benchegg]

+1, is it anyway we can write a composer plug-in to support new VcsDriver?

[Seldaek]

For enterprise use there is now https://toranproxy.com which does things quite a lot better than satis and packagist for the typical redundancy/safety use cases.