wangi left a comment (openstreetmap/openstreetmap-website#7208)
> So you can't actually reuse the existing `overpass_url` setting in the way
> you're doing here because that is already in use to configure the overpass
> query endpoint used by the query tool and that might not be (and is not in
> our production use case) a public server that can be used on the export page.
Understood, OSM uses an internal Overpass server for the query functionality so
it can be dedicated to that role and not subject to the load balancing of
external Overpass servers.
I can certainly rework this to add a `export_overpass_url` setting. However
would there be any desire to cover the other third-party URLs used by by the
export functionality with settings too? I had assumed I would face an uphill
struggle if I had proposed this originally, hence I just focussed on the one
which, incorrectly, had an existing setting in place.
- `export_overpass_url`: `https://overpass-api.de/api/map`
- `export_planet_url`: `https://planet.openstreetmap.org/`
- `export_geofabrik_url`: `https://download.geofabrik.de/`
- `export_other_url`: `https://wiki.openstreetmap.org/wiki/Download`
I had planned to handle these outwith the OSM codebase for my use-case, but
personally do see a benefit of moving hardcoded URLs out of the code and into
settings.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/7208#issuecomment-4886562021
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/pull/7208/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
