Project:Mirror Group

From Adélie Linux

The Mirror Group is responsible for maintaining rsync infrastructure and stratum 1 mirrors. This group is also responsible for determining which stratum 2 mirrors are officially listed and maintaining documentation for stratum 2 mirror owners.

Project members

Stratum 1 mirrors

All Stratum 1 mirrors are on the round-robin. You should never need to connect to these manually.

North America

IBM POWER9 @ 3.8 GHz; 1 GB RAM; 1 TB NVMe; Adélie Linux + lighttpd
Comments: This is the master mirror server (where new packages and updates are uploaded), located in the US. It is also the official rsync server, which other mirrors use for synchronisation.
AMD Opteron(tm) @ 3.00GHz; 96 GB RAM; Alpine Linux 3.8 + lighttpd
Comments: Mirror server in Pennsylvania, US, generously hosted by Zach van Rijn. Primary server for North America.


  • (kelsey)
Intel(R) Xeon(R) @ 2.40GHz; 512 MB RAM; Adélie Linux + Apache 2.6
Comments: This is the primary mirror for Europe, located in Amsterdam, NL. It was the first production Adélie Linux server ever installed.

Stratum 2 mirrors

These mirrors are not directly controlled by Adélie Linux. Nevertheless, they serve a vital role in ensuring that our stratum 1 mirrors are not overloaded, and we are very grateful to the administrators of these sites.

North America

8-core Intel(R) Xeon(R); 192 GB RAM; 300 TB disk
Comments: Located in Chicago, IL, US.

Stratum 3 mirrors

Unofficial, private, home, or internal mirrors are considered "stratum 3" mirrors. We do not list these as they are not public and cannot be used by others. If you have a large number of computers – whether you have a home lab, a networked office, or are a school MIS director – you may benefit from running your own stratum 3 mirror. This will allow you to keep a copy of all packages locally; you will only have to update your mirror, and then all your other computers will be able to fetch packages from your internal mirror. This results in fewer connect time charges, lower bandwidth usage, and faster updates.

Notice: A single architecture-version pair (for example, 1.0 for x86_64) can use more than 20 GB of disk space. An entire release (1.0 for all architectures) can reach 100 GB or more. Ensure that your candidate system has enough disk space for the packages you want to mirror.

Setting up a mirror

Ensure that you have rsync and a cron runner installed. If you're using Adélie, simply run:

   # apk add rsync fcron

Create a new user that has write access to the location that you wish to use for mirror storage. We recommend a path such as /srv/mirror, and configuring your Web server to share that path. Log in as that user.

Run the following command to begin an initial sync run:

   $ rsync --recursive --times --links --hard-links --delete-after rsync:// /srv/www/distfiles/

You may prepend --verbose to the argument list if you want to watch progress. This is **not recommended** in the actual cron job, as the cron logs will grow large very quickly.

Run the following command to edit the crontab file:

   $ crontab -e

Add the rsync command to the mirror user's crontab file. Please use a random number between 0 and 60 for the minute; this will ensure that the master mirror is not overloaded by many mirrors running a synchronisation at the same time.