-
Notifications
You must be signed in to change notification settings - Fork 184
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
src/xbps/repositories/mirrors: move most mirror docs to xmirror
- Loading branch information
1 parent
037e4d3
commit 96bb2af
Showing
1 changed file
with
8 additions
and
78 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,86 +1,16 @@ | ||
| # Mirrors | ||
|
|
||
| Void Linux maintains mirrors in several geographic regions for you to use. A | ||
| fresh install will default to using the master mirror in Europe, but you may | ||
| also [select a different mirror](./changing.md) manually. | ||
| Void Linux maintains mirrors in several geographic regions for users. A fresh | ||
| install will default to | ||
| [repo-default.voidlinux.org](https://repo-default.voidlinux.org), which may map | ||
| to any Tier 1 mirror, but you may have a better experience by [selecting a | ||
| different | ||
| mirror](https://docs.voidlinux.org/xbps/repositories/mirrors/changing.html). | ||
|
|
||
| ## Tier 1 mirrors | ||
|
|
||
| Tier 1 mirrors are maintained by the Void Linux Infrastructure Team. These | ||
| mirrors sync directly from the build-master and will always have the latest | ||
| packages available. | ||
|
|
||
| By default XBPS will reach out to <https://repo-default.voidlinux.org> which may | ||
| map to any tier 1 mirror. | ||
|
|
||
| <!-- Order alphabetically by: (1) Region, (2) Country, (3) City/State/Province/etc, (4) URL --> | ||
|
|
||
| | Repository | Region | Location | | ||
| |------------------------------------------------|---------------|--------------------| | ||
| | <https://repo-fastly.voidlinux.org/> | Global | Fastly Global CDN | | ||
| | <https://repo-fi.voidlinux.org/> | Europe | Helsinki, Finland | | ||
| | <https://repo-de.voidlinux.org/> | Europe | Frankfurt, Germany | | ||
| | <https://mirrors.servercentral.com/voidlinux/> | North America | Chicago, USA | | ||
| <!-- | <https://repo-us.voidlinux.org/> | North America | Kansas City, USA | --> | ||
|
|
||
| ## Tier 2 mirrors | ||
|
|
||
| Tier 2 mirrors sync from a nearby Tier 1 mirror when possible. These mirrors are | ||
| not managed by Void and do not have any guarantees of freshness or completeness | ||
| of packages, nor are they required to sync every available architecture or | ||
| sub-repository. | ||
|
|
||
| ### Globally-available mirrors | ||
|
|
||
| <!-- Order alphabetically by: (1) Region, (2) Country, (3) City/State/Province/etc, (4) URL --> | ||
|
|
||
| | Repository | Region | Location | | ||
| |----------------------------------------------------|---------------|------------------------| | ||
| | <https://mirror.ps.kz/voidlinux/> | Asia | Almaty, Kazakhstan | | ||
| | <https://mirror.nju.edu.cn/voidlinux/> | Asia | China | | ||
| | <https://mirrors.bfsu.edu.cn/voidlinux/> | Asia | Beijing, China | | ||
| | <https://mirrors.cnnic.cn/voidlinux/> | Asia | Beijing, China | | ||
| | <https://mirrors.tuna.tsinghua.edu.cn/voidlinux/> | Asia | Beijing, China | | ||
| | <https://mirror.sjtu.edu.cn/voidlinux/> | Asia | Shanghai, China | | ||
| | <https://repo.jing.rocks/voidlinux/> | Asia | Tokyo, Japan | | ||
| | <https://void.webconverger.org/> | Asia | Singapore | | ||
| | <http://ftp.dk.xemacs.org/voidlinux/> | Europe | Denmark | | ||
| | <https://mirrors.dotsrc.org/voidlinux/> | Europe | Denmark | | ||
| | <https://ftp.cc.uoc.gr/mirrors/linux/voidlinux/> | Europe | Greece | | ||
| | <https://quantum-mirror.hu/mirrors/pub/voidlinux/> | Europe | Hungary | | ||
| | <https://voidlinux.mirror.garr.it/> | Europe | Italy | | ||
| | <https://void.cijber.net/> | Europe | Amsterdam, Netherlands | | ||
| | <https://void.sakamoto.pl/> | Europe | Warsaw, Poland | | ||
| | <http://ftp.debian.ru/mirrors/voidlinux/> | Europe | Russia | | ||
| | <https://mirror.yandex.ru/mirrors/voidlinux/> | Europe | Russia | | ||
| | <https://ftp.lysator.liu.se/pub/voidlinux/> | Europe | Sweden | | ||
| | <https://mirror.accum.se/mirror/voidlinux/> | Europe | Sweden | | ||
| | <https://mirror.puzzle.ch/voidlinux/> | Europe | Bern, Switzerland | | ||
| | <https://mirror.vofr.net/voidlinux/> | North America | California, USA | | ||
| | <https://mirror2.sandyriver.net/pub/voidlinux/> | North America | Kentucky, USA | | ||
| | <https://mirror.clarkson.edu/voidlinux/> | North America | New York, USA | | ||
| | <https://mirror.aarnet.edu.au/pub/voidlinux/> | Oceania | Canberra, Australia | | ||
| | <https://ftp.swin.edu.au/voidlinux/> | Oceania | Melbourne, Australia | | ||
| | <https://voidlinux.com.br/repo/> | South America | Ouro Preto, Brazil | | ||
| | <http://void.chililinux.com/voidlinux/> | South America | Pimenta Bueno, Brazil | | ||
| See [xmirror.voidlinux.org](https://xmirror.voidlinux.org) for more information | ||
| and a list of available mirrors. | ||
|
|
||
| ## Tor Mirrors | ||
|
|
||
| Void Linux is also mirrored on the Tor network. See [Using Tor | ||
| Mirrors](./tor.md) for more information. | ||
|
|
||
| ## Creating a mirror | ||
|
|
||
| If you'd like to set up a mirror, and are confident you can keep it reasonably | ||
| up-to-date, follow one of the many guides available for mirroring with | ||
| [rsync(1)](https://man.voidlinux.org/rsync.1), then submit a pull request to | ||
| [the void-docs repository](https://github.com/void-linux/void-docs) to add your | ||
| mirror to the appropriate mirror table on this page. | ||
|
|
||
| A full mirror requires around 1TB of storage. It is also possible to mirror only | ||
| part of the repositories. Excluding debug packages is one way of decreasing the | ||
| load on the Tier 1 mirrors, with low impact on users. | ||
|
|
||
| Please keep in mind that we pay bandwidth for all data sent out from the Tier 1 | ||
| mirrors. You can respect this by only mirroring if your use case for your mirror | ||
| will offset the network throughput consumed by your mirror syncing. |