![mirrorsync ports mirrorsync ports](https://fe0153bcde9fb4ea238c-1715965f9bf3500addbed7446461b9bc.ssl.cf1.rackcdn.com/1FMCU0GX9DUA47011/e888f80954fd7455b0b0bc38b1e8a3e7.jpg)
![mirrorsync ports mirrorsync ports](https://5f1bb0893a8eaac9f250-9c053a30993a6e83a51a30cda4e16bfc.ssl.cf1.rackcdn.com/1FMCU0H96DUD66558/0791a252f29aa72bc04223ea4c35fd71.jpg)
I hope the following will help avoid this trouble for anyone else.
MIRRORSYNC PORTS HOW TO
It seemed to fit the bill exactly.īut there was a problem: documentation on how to actually run Mirrorbits was sparse, so it took quite a bit of trial-and-error to determine how to use it. Mirrorbits is a Go program with a single goal: provide a way to distribute requests from a single central repository to multiple geo-diverse repositories, based on the client’s GeoIP information, handling availability and freshness seamlessly. So one of their talented developers created a solution: Mirrorbits. VideoLAN, creators of the fantastic VLC Media Player, had the same issue of distributing files. Many years before, another FLOSS project had encountered the same problem. I wanted something we could control, and I went looking for a solution - how to effectively create a CDN for file downloads. We had to come up with a better solution.Īs a DIYer at heart, and leading a project built by and for DIYers, I wasn’t content to simply throw CloudFlare in front of the repo - my concerns with that provider notwithstanding.
MIRRORSYNC PORTS DOWNLOAD
The main complaint was abysmally slow download speeds, and occasionally even full-on timeouts. And users, especially users in Europe and Asia, were having trouble downloading our releases. Jellyfin is a global project, and while I’m personally located in Ontario, Canada, the very vast majority of our users are not. This server, located on Digital Ocean in the Toronto zone, housed both the build process as well as our main repository, served directly via NGiNX.īut this release was the first where we noticed a problem. Prelude - Pre-10.6.0īefore our 10.6.0 release, we had a fairly simple repository setup: everything would build on a VPS, running Debian, called build1, in response to a GitHub web-hook. And both for those interested, and for those supporting other similar projects, I’d like to share how we do it. But at Jellyfin, we needed something more robust, something able to handle our needs more elegantly than GitHub or a basic web server could. For many projects, distributing binary assets is easy: put the files on GitHub and you’re done.