Hi Daniel,

On 09/29/2015 09:30 PM, Daniel Reurich wrote:
> On 30/09/15 02:15, tilt! wrote:
>> Suppose at some point a new mirror had to be set up (for example
>> in Australia).
>>
>> Is the mirror then just a copy of a directory - for example,
>> "/dists/devuan" on an FTP or HTTP server - or does it require actively
>> running software for self-maintainance (like the "rebuild" operation
>> you have described)?
>>
> Only for the /devuan repo. The /merged repo uses url rewriting to
> refer to /devuan, deb-multimedia, and debian using amprolla.
> So you will need to replicate packages.devuan.org/devuan and run
> amprolla which does the url rewriting and will need to be configured
> to redirect to your nearest upstream mirrors.

Ok, because i got an inquiry on #devuan asking if there is or will be
a mirror in AARNET (Australian Research and Education Network).

Users in there are very bandwidth-limited, i.e. they need stuff to be
inside the AARNET network.

AARNET runs a mirror of lots of free software at

http://mirror.aarnet.edu.au/

They claim to be liberal about what they consider for mirroring, but my
understanding is that it has to be a "passive" directory of data; an active
software can not be run there, unless we find volunteers maintaining it.

Again, main goal of that mirror was for users to have the bulk of the
traffic inside AARNET, which is free for them; therefore, if a mirror can
host all the .deb, while some external site hosts generated Packages files,
my guess is, that would not be a showstopper.

Also, i bring this forth to discussion on an exemplary basis, and to further
my understanding of how Devuan mirroring works.

Best regards,
T.