repman-io
Packagist.org files should be fetched via repo.packagist.org
I have noticed in our logs that repman queries a lot of /p2/foo/bar.json files on the main packagist.org domain. Due to some optimization on our end we will need to stop serving those files at some point on the main domain.
The correct domain to use for metadata as per the docs is repo.packagist.org. Please update your default configs so that it fetches from the correct domain as it will eventually stop working otherwise.
Also, for anyone reading this using Repman.. Please don't. Right now Repman is one of the main user agent we see doing requests, but that's only coming from a few IPs.. So it seems to me like repman is doing mirroring in a very inefficient way that produces a lot of load on our servers for the benefit of few people.
Using Private Packagist if you want to have a mirror (and more features) or the official packagist.org repository would be much better for everyone, and you'd get maintained software too.
There is also a free Packeton if you want to have a mirror. It makes fewer requests via repo.packagist.org and use https://packagist.org/metadata/changes.json?since=16142636710498 API
Also, for anyone reading this using Repman.. Please don't. Right now Repman is one of the main user agent we see doing requests, but that's only coming from a few IPs.. So it seems to me like repman is doing mirroring in a very inefficient way that produces a lot of load on our servers for the benefit of few people.
Using Private Packagist if you want to have a mirror (and more features) or the official packagist.org repository would be much better for everyone, and you'd get maintained software too.
I can appreciate the request, but I feel the need to point out that you're asking folks to go from a totally free solution that covers the majority of what most people need to a solution that could cost thousands a year (ex: self-hosted).
@swichers Talk to us about pricing if that's the only problem, but you also get maintained software and a lot more features than repman.
And if that's still not for you then run repman without the packagist.org mirroring if that's possible at all, because as it is repman causes us extra cost and possibly service degradation for others, so your company can host their mirror without paying a dime. We also provide packagist.org as a free service for the whole community and need to ensure quality.
I'm just pointing out an issue with your messaging. It's going to be a hard sell to get people to migrate from free to expensive when the proposition is how the migration benefits a third party.
Well the proposition is you get something that works, vs staying on broken software. Apparently yes that has a cost, because this repo ended up EOL - I can only imagine that is in part because it wasn't paying the bills.
Thank you for reporting the problem, as soon as I find time I will try to fix it.
Well the proposition is you get something that works, vs staying on broken software
Another solution would be to simply propose a solution or open a PR.
