(01-01-2025, 08:37 AM)sanuske4 Wrote: Local non-ARM Windows version simply crashes out when attempting to run. File placed in C:\Users\XXXXX\AppData\Local\Discovery Freelancer 5.00.8. Tested under EXE subdirectory as well. When ran through CMD returns error:
C:\Users\XXXXXXX\AppData\Local\Discovery Freelancer 5.00.8>darkstat-windows-amd64.exe
panic: failed to read file from embeded fs of files\docs_coordinates_in_trade_routes.png
...
I reproduced the error. It shall be fixed. adding into priority todo list to take care of it.
Funny filesystem differences between Linux and Windows hmm. probably just a matter of fixing paths \ to // Task fl-darkstat#74 is registered
(01-01-2025, 08:37 AM)sanuske4 Wrote: Local non-ARM Windows version simply crashes out when attempting to run. File placed in C:\Users\XXXXX\AppData\Local\Discovery Freelancer 5.00.8. Tested under EXE subdirectory as well. When ran through CMD returns error:
C:\Users\XXXXXXX\AppData\Local\Discovery Freelancer 5.00.8>darkstat-windows-amd64.exe
panic: failed to read file from embeded fs of files\docs_coordinates_in_trade_routes.png
...
I reproduced the error. It shall be fixed. adding into priority todo list to take care of it.
Funny filesystem differences between Linux and Windows hmm. probably just a matter of fixing paths \ to // Task fl-darkstat#74 is registered
All endpoints where designed to share data in Bulk, as fast as possible, but with some reasonability to pulled data size
Exposed every entity basically almost as darkstat has tabs for.
the json API is cross language friendly format, but if you utilize Golang, there is extra option of hooking yourself to RPC way to Pull data in addition (this one has sort of always correct client library avaiable to just import code)
The json API and RPC are both available through https. Plus you can always run darkstat locally, in this case you can get 3 times performance boost to pull data by using Unix Sockets if it is running on Linux!