Re: TerraSync / CDN hosting

Okie dokie. Thanks so much for the information.

If there's anything I can do to help, let me know.

Best,

--
Josh Davidson
________________________________
From: James Turner <[email protected]>
Sent: Friday, 10 July 2026 11:10:04
To: FlightGear developers discussions <[email protected]>
Subject: Re: [Flightgear-devel] TerraSync / CDN hosting



On 10 Jul 2026, at 14:45, Josh Davidson <[email protected]> wrote:

James - thanks for that breakdown, makes much more sense now!


Thanks to some final fixes from Torsten D, things should be working again now, except WS3 on next.

The medium term plan is to change the client code to look for ‘dirindex’ (instead of .dirindex), going forward, and adjust the CDN edge rules to redirect requests for the old name. However, we will need some shenanigans so plain / file mirrors (eg, TerraMaster or Bittorent) include both the old and new names, to ensure those sources work with current and legacy clients.


Out of curiosity what is the storage requirement of terrasync? I might have enough room on my server to mirror it.


It’s currently:

92GB for WS2 (over 1.8 million files)
137GB for OSM2City (over 62k files, yay for tarballs and efficiency…)
248GB for WS3 *but* with some duplication of the WS2 data (for Airports / Objects)

It’s likely the WS3 number will increase as we add more high-res landcover sources outside Europe, and I have no idea how much an OSM-for-WS3 will increase.

At present, we don’t actually need more mirrors, since the CDN has global coverage, and should be ‘fastest’ for basically anyone except for use cases where access to global data-centers is restricted. (And of course there are some places where that is the case….)

Kind regards,
James

_______________________________________________
Flightgear-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/flightgear-devel