Slow response from getcomposer.org breaking deployments

142 Views Asked by At

It seems that getcomposer.org is responding very slowly today. This is breaking deployments that have reasonable timeouts for various steps. Is there a fallback or alternate address?

1

There are 1 best solutions below

0
On BEST ANSWER

Getcomposer.org should not impact your deployment, however if getcomposer.org is slow, most likely packagist.org is also affected, which hosts the package information.

If you directly use the projects from Packagist, your deployments not only depend on packagist.org being up, and available, but the hosting site for the projects you depend on (most likely Github or Bitbucket). This is probably not the best option, if it's important for you to be able to deploy independently of the status of these sites.

You can run a local Satis instance to avoid depending on packagist.org. If you want to stop depending on Github or Bitbucket as well, then you could host a private copy of the repositories for your dependencies, and provide your private repositories in your private Satis instance you can be self sufficient and disable using Packagist in your composer.json.

If you have a local Satis instance, you have to update it periodically to be able to update your dependencies. If you self host the repositories as well, then you will need to pull from upstream and update Satis before you are able to run composer update.

For information on Satis check https://getcomposer.org/doc/articles/handling-private-packages-with-satis.md.