|
From: Torsten D. <to...@t3...> - 2024-01-08 16:26:14
|
Speaking as someone who has collected/inherited bits and pieces of "hey,
this looks easy"
data and infrastructure ideas over the last decade or so:
Terrasyncing ws3.0 is straightforward and our DNS resolver system is
ready for it.
So, "this looks easy". However, keep in mind that for making this
"official", I strongly
recommend thinking about some kind of process to
* create and allow updates of the scenery sometimes
* do this even if the original creator has left the project
* incorporate changes into existing scenery (doing this manually gets
boring over time)
* work in coexistance with existing processes, think of the scenery
database e.g.
* manage expectations from our users
None of these should hold you back collecting and hosting the data in
the way you mentioned.
You can start right away with your server, add the .dirindex files and
make people use your T/S
mirror by setting the correct property on startup.
But please think carefully about the above mentioned items (and maybe
some more) before
going large scale.
Greetings and wishing you all a late happy new year!
Torsten
Am 08.01.24 um 16:17 schrieb merspieler:
> Hey,
>
> Since there's now more and more WS3.0 scenery out there,
> would it make sense to start having terrasync for WS3.0?
>
> I'd be happy to host this as long as people send me the
> scenery already packaged so I only need to update the root
> dirindex files (don't wanna run dir index generation over
> loads of stuff or do packaging up the files my self)
>
> Also (iirc James mentioned that this might be possible) what
> about loading the tgx/tgz files directly instead of unpacking
> them onto disk?
> Would save me from doubling the data, cause I then don't have
> to have it once packed for the mirror and once unpacked for use.
> Instead I could, just like with ws2.0 terrasync use the same
> thing for both.
>
>
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
> |