not that likely to get an answer as it’s really a support call, not a bug/task.
The first question is about proper documentation of all the stuff we’ve been discussing in this thread, so one would think that’s a valid task. It doesn’t seem right that closer.lua, for example, is undocumented. Either it’s not meant for public use (and I am not an intended user), or there should be something out there that explains how to use it. I’m not looking for much; just some basic info that covers the various things I’ve had to piece together from mailing lists and Google. there’s no mirroring, if you install to lots of machines your download time will be slow. You could automate it though, do something like D/L, upload to your own bucket, do an s3 GET. Yeah, this is what I’m probably going to do eventually—just use my own S3 bucket. It’s disappointing that, at least as far as I can tell, the Apache foundation doesn’t have a fast CDN or something like that to serve its files. So users like me are left needing to come up with their own solution if they regularly download Apache software to many machines in an automated fashion. Now, perhaps Apache mirrors are not meant to be used in this way. Perhaps they’re just meant for people to do the one-off download to their personal machines and that’s it. That’s totally fine! But that goes back to my first question from the ticket—there should be a simple doc that spells this out for us if that’s the case: “Don’t use the mirror network for automated provisioning/deployments.” That would suffice. But as things stand now, I have to guess and wonder at this stuff. Nick On Thu, Dec 24, 2015 at 5:43 AM Steve Loughran <ste...@hortonworks.com> wrote: > > On 24 Dec 2015, at 05:59, Nicholas Chammas <nicholas.cham...@gmail.com> > wrote: > > FYI: I opened an INFRA ticket with questions about how best to use the > Apache mirror network. > > https://issues.apache.org/jira/browse/INFRA-10999 > > Nick > > > > not that likely to get an answer as it's really a support call, not a > bug/task. You never know though. > > There's another way to get at binaries, which is check them out direct > from SVN > > https://dist.apache.org/repos/dist/release/ > > This is a direct view into how you release things in the ASF (you just > create a new dir under your project, copy the files and then do an svn > commit; I believe the replicated servers may just do svn update on their > local cache. > > there's no mirroring, if you install to lots of machines your download > time will be slow. You could automate it though, do something like D/L, > upload to your own bucket, do an s3 GET. >
