You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Question
I tried a simple mirrorbits server based on the sample configuration and go checked the source code, then I found the local repository(configured via Repository) is only used for checksum and scaning mirror repos, not for download directly. Therefore I have a question regarding this. What's the correct case for using mirrobits?
This is what I have in mind, considering I have a main repo which will rysnc artificats to A B C three mirror repos. I can deploy the mirrorbits along with main repo but exposed via another port and use mirrorbit to route requests to mirror repos or fallback to the main repo?
The text was updated successfully, but these errors were encountered:
Mirrorbits is intended to be a download redirector. You can of course install it on a different port on the primary mirror. Assume that example.com is a mirror that serves its files via HTTPS on port 443. Then you can install Mirrorbits on the same server on a different port, for example 8080, and add https://example.com/ and possibly other mirrors to it. Download requests on port 8080 will then be redirected to one of the mirrors, including http://example.com/.
Question
I tried a simple mirrorbits server based on the sample configuration and go checked the source code, then I found the local repository(configured via
Repository
) is only used for checksum and scaning mirror repos, not for download directly. Therefore I have a question regarding this. What's the correct case for using mirrobits?This is what I have in mind, considering I have a main repo which will rysnc artificats to A B C three mirror repos. I can deploy the mirrorbits along with main repo but exposed via another port and use mirrorbit to route requests to mirror repos or fallback to the main repo?
The text was updated successfully, but these errors were encountered: