[wp-trac] [WordPress Trac] #62132: Make wordpress.org API connections for updates, plugins and themes configurable to a different location

[WordPress Trac]

#62132: Make wordpress.org API connections for updates, plugins and themes
configurable to a different location
-----------------------------+----------------------------
 Reporter:  jamesking56      |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  WordPress.org
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+----------------------------
Changes (by Clorith):

 * milestone:  Awaiting Review => WordPress.org


Comment:

 While possible to do with the HTTP API filter, that feels like a crutch in
 this case.

 Referencing the more recent statement from Matt about the risk to
 WordPress.org over time, and the global impact it would have on sites and
 services using WordPress if the site were to go away, I think it's
 reasonable to implement something here that would facilitate the easy
 switching of sources, either by hosts, or by site owners them selves.

 Given the current state, implementing a means to easily run your own
 mirrors would also be a show of good faith, which I think would be valued
 by many. If there's agreement that my thoughts here make sense, I'd be
 happy to milestone it for 6.8, and help anyone wanting to work on it, land
 it.

 For a first iteration, and probably a good place to start as early as for
 6.8, I would like to see a common filter for just the `api.wordpress.org`
 address to be controllable with a mirror that answers to the same API
 requests.

 By doing this as a filter, and not a constant, you could pass the full
 query as context and allow the filter to modify the URL based on the
 intent, as that would cover both use cases without over-complicating the
 basic implementation.

 This could either be a filtered function reused throughout core, or a
 filter in the HTTP API wrapper so that we only need to maintain a single
 location, without needing to go through the source and modify all existing
 links.

 The upside to this is that it would simplify the process for hosts to
 create their own mirrors to reduce load on WordPress.org as a whole, and
 improve performance. Yes many hosts proxy requests there as is, but this
 would give the smaller ones with less resources that same starting point.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62132#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform