Redundant Composer Module Repository

[ryantfowler]

In light of Issue 4617, it would appear that either the addition of a redundant repository or some form of high availability solution (possibly a location that caches modules, so that the modules are static and not effected with any potential issues with the main repository; the cached modules could be updated as updates are made to the main repository...this would be something that could be automated, of course) would be in order. Having a single point of failure is a high liability.

Thoughts?

Thank you for your time and consideration.

[ryantfowler]

Bump. Issue is happening again. Single point of failure for the whole community is a liability.

[IvanChepurnyi]

Just use Toran proxy for synchronization for it. it is free for personal use. Very helpful for agencies to have the local setup with it. It is 5 minutes to setup and you can create a full mirror of the repository, that automatically gets updated by cron.

The same issue is happening when you use packagist packages, as GitHub might be down from time to time. Toran Proxy serves me well for this purpose.

[ryantfowler]

@ivan, thanks for the suggestion. I think I will do that. Now what about others who don't want to do that for their individual reasons? I don't see why Magento can't set up something similar. That way all requests for packages are being read from a mirror.

[IvanChepurnyi]

@ryantfowler I agree that Magento must build highly redundant system, but even in this cases there can be network outages near your server and you might experience downtime from your region. I just suggesting you a solution, so next time you will drink a 🍺 while repo.magento.com is down and your delivery pipeline still works as expected.

[ryantfowler]

Lol. Thank you for your suggestion. I agree with your points regarding what could lead to downtime as well. And I'll take a look at Toran, but I was mainly thinking of others. Thanks again

[tanya-soroka]

Issue has been resolved. Please verify if you can sync with repo.magento.com

@IvanChepurnyi we will work on the backup on the downtime issues. Thanks

[hostep]

@tanya-soroka: maybe also consider building a status page which shows if the repository is down or not (it should be automated to work properly and don't require manual work to update the status obviously).

Because right now, if the service is down, it's sometimes hard to figure out if something is wrong on our own end, or if something is wrong with the repository. If you have a status page, we can always first verify if it's a known issue.

Also: if you are going to perform maintenance to the repository and it will go down, you can announce it beforehand on the status page for example.

[tanya-soroka]

Thanks for the suggestions. We will definitely review it.

[veloraven]

@hostep if your proposition is still actual could you please transfer it to Magento 2 Feature Requests and Improvements forum? (see details here).