Macports rsync code#

Macports rsync code#

distfiles contains the source code tarballs from which the precompiled archives were created.

Mirroring this data will provide the greatest benefit to MacPorts users near you since it lets them automatically receive these large files more quickly. This is the largest directory, currently around 1.2 TB.

packages contains precompiled archives of each MacPorts port for several macOS versions.

The four directories contain the following data: Note: We also offer those four directories as separate rsync modules, however they are deprecated. If you prefer to copy only a subset of our content, you can mirror the packages, distfiles, release and/or trunk subdirectories of the macports module (into a macports rsync module on your server). We recommend you copy all of our content by mirroring our macports rsync module, and we recommend you republish this on your server in a macports rsync module. The server does not need to be running macOS and does not need to have MacPorts installed. IPv6 access is welcomed but is not required. The server should have a hostname and a static IPv4 address.

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. You'll need a server with at least 2 TB of available disk space on a case-sensitive filesystem. 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. 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. One of our servers in California, for example, served around 250GB of data via http and another 70GB of data via rsync per day. Running a MacPorts mirror will use a possibly significant amount of bandwidth. If in the future you wish to temporarily or permanently discontinue providing your mirror, please let us know so that we can make the appropriate changes. We reserve the right to refuse a request to become a mirror for any reason, or to remove existing mirrors from use at any time and without notice. Meanwhile you can follow the rest of these instructions to get your mirror ready. We will review your request to become a mirror and will let you know if there are any problems. We will list this information on our mirrors page. Your mirror's upstream Internet connection speed and whether or not your mirror supports IPv6.We will list this on our mirrors page and MacPorts users might report problems to this address. The email address of the server's administrator.Whether your server can be accessed over only http or only https or both.We will create new hostnames abc.xy., abc.xy. and abc.xy. (where 'abc' is your airport code and 'xy' is your country code) CNAMEd to your existing hostname. You may provide the coordinates of the above airport if you don't want to be more specific. GPS coordinates of your mirror's approximate location that we may display on a map.The airport code and country code will become your MacPorts mirror name. The city, state/province and ISO 3166-1 alpha-2 country code where your mirror is located and the IATA airport code of the closest airport.The name and web page URL of the organization providing the mirror, so that we can credit you properly.Please tell us the following information:

If you find inaccuracies in these instructions or have other comments or questions, please let us know by contacting portmgr.įirst, please contact portmgr to let us know you would like to create a mirror. Making MacPorts content available in more locations makes MacPorts faster.

Thank you for your interest in providing a public MacPorts mirror server to join our existing list of mirrors.