Opened 2 years ago

Last modified 6 days ago

#14188 new enhancement

Haiku Package Repository Mirrors

Reported by: kallisti5 Owned by: bonefish
Priority: normal Milestone: Unscheduled
Component: Servers/package_daemon Version: R1/Development
Keywords: mirrors Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by jessicah)

I've placed a simple csv onto our "central" haikuports repository with a listing of known / trusted mirrors.

http://eu.hpkg.haiku-os.org/haikuports/master/repository/x86_64/current/mirrors.txt

Proposed Format:

country,city,mirror provider,mirror provider website,mirror location

I just used the information SourceForge provided about mirrors years ago as a template. Let me know if anyone has alternate ideas/changes/additions.

Ubuntu / Debian used to (and still do?) have a tool to show the "fastest mirror provider" to your location. At minimum though we might just want to "give users a choice"

We already have the app to manage repositories... maybe it could check the "original repository" for a mirrors file and provide the user some options to use?

Change History (3)

comment:1 by jessicah, 2 years ago

Description: modified (diff)

Added .txt extension to URL, so it displays in browser rather than being downloaded automatically.

comment:2 by ozzmosis, 14 months ago

I'm only getting about 160Kbyte/sec from the eu.hpkg.haiku-os.org repository. I was hoping I could switch to a faster mirror, and through Googling discovered mirrors.txt, but evidently cdn.haiku.nz/haikuports/x86_64 is not current, and cdn.nyc1.terarocket.io does not resolve.

comment:3 by apl-haiku, 6 days ago

Worth noting that HDS also manages a list of mirrors. The API for this is documented (see "Get All Repositories' Details") so that the Haiku desktop would be able to obtain the mirror data relatively easily. There is an already built web user-interface for managing the list of mirrors and the HDS system will automatically update the identifier field in the records if this changes in the remote system. HDS's production of this data is cached and honours the standard If-Modified-Since header. A JSON schema for the response of this API is available.

Note: See TracTickets for help on using tickets.