Re: Accessing yum-archive.postgresql.org

On Fri, 13 Dec 2019 at 03:39, Devrim Gündüz <devrim(at)gunduz(dot)org> wrote:

>
> Hi,
>
> On Thu, 2019-12-12 at 10:09 +0100, Christoph Berg wrote:
> > Re: Craig Ringer 2019-12-12 <
> > CAMsr+YEaoULxAYvJE8EfpEVga4F-nmrwm4cPPDM=QhdYRkjxBA(at)mail(dot)gmail(dot)com>
> > > I'm assuming that all directory listing is disabled?
> >
> > That's because it's all S3 buckets.
>
> Yeah :/
>

That makes sense. S3 isn't exactly helpful about these things.

> I need to invent a fix for that for the upcoming apt.pg.o archive as
> > well... hopefully putting an index.html file in there works.
>
> Please let me know if that works for you
>

For interactive use, yes. But if the infrastructure has to generate files,
then easy scriptability would be really good too. HTML isn't the greatest
for that unless you mix in XML with a secondary namespace, and then you
start upsettting browsers.

You also probably don't want to be re-writing one giant index.html or
Packages.xz or similar manifest file each time the archive is updated.

So I think side-by-side HTML and some kind of json or similar would make
sense, both generated and updated at the same time in the same job. There'd
probably want to be a master listing entry point plus sub-listings, both
for the HTML and script-friendly representations. I don't really have a
strong opinion about the format of such listings so long as there's a
browser-navigible HTML variant and something easily scripted. I'd lean
toward json since it's so widespread and convenient, but pretty much
anything right down to a tab separated flat file would do.

--
Craig Ringer http://www.2ndQuadrant.com/
2ndQuadrant - PostgreSQL Solutions for the Enterprise