Changes between Version 26 and Version 27 of Mirroring


Ignore:
Timestamp:
Jul 29, 2020, 5:45:26 AM (4 years ago)
Author:
ryandesign (Ryan Carsten Schmidt)
Comment:

Rename OS X to macOS

Legend:

Unmodified
Added
Removed
Modified

  • Mirroring

    v26 v27  
    2626Running a MacPorts mirror will use a possibly significant amount of bandwidth. One of our servers in California, for example, served around 250GB of data via http and another 70GB of data via rsync per day. For http traffic, MacPorts chooses the closest mirror automatically, so how much traffic your mirror sees depends on the number of MacPorts users for whom your mirror is the closest. Ensure you have the permission of your network provider to run such a mirror, and that this amount of traffic will not be a problem for you.
    2727
    28 You'll need a server with at least 1.5 TB of available disk space on a case-sensitive filesystem. You'll need a web server on port 80 such as Apache httpd or nginx on which you can configure new virtual hosts, and the rsync daemon running on port 873. The server should have a hostname and a static IPv4 address. IPv6 access is welcomed but is not required. The server must respond to pings. The server does not need to be running OS X and does not need to have MacPorts installed.
     28You'll need a server with at least 1.5 TB of available disk space on a case-sensitive filesystem. You'll need a web server on port 80 such as Apache httpd or nginx on which you can configure new virtual hosts, and the rsync daemon running on port 873. The server should have a hostname and a static IPv4 address. IPv6 access is welcomed but is not required. The server must respond to pings. The server does not need to be running macOS and does not need to have MacPorts installed.
    2929
    3030== Rsync modules
    … …  
    3232The MacPorts files are distributed in four rsync modules. You should usually mirror all of them.
    3333
    34 * **packages** contains precompiled archives of each MacPorts port for several OS X versions. This is the largest module, around 1.2 TB. Mirroring this module will provide the greatest benefit to MacPorts users near you since it lets them automatically receive these large files more quickly.
     34* **packages** contains precompiled archives of each MacPorts port for several macOS versions. This is the largest module, around 1.2 TB. Mirroring this module will provide the greatest benefit to MacPorts users near you since it lets them automatically receive these large files more quickly.
    3535* **distfiles** contains the source code tarballs from which the precompiled archives were created. There are some ports that cannot legally be distributed as binaries, so those must build from these source files on the user's computer. This is the second-largest module, around 250 GB. **Note:** this module used to be called ''mpdistfiles''. If you are mirroring ''mpdistfiles'', please switch to mirroring ''distfiles''. If your local module is called ''mpdistfiles'', please rename it to ''distfiles'' and let us know so that we can update mirror_sites.tcl.
    3636* **release** contains the latest released version of the MacPorts base source code which users update by running `sudo port selfupdate`, as well as the collection of Portfiles—the text files MacPorts reads that tell it how to install each port—which users update by running `sudo port sync`. Users near you can manually configure MacPorts to user your mirror for faster speed. This small module has a size of less than 1 GB.