First test of new Oar server success only a few bugs to sort yay. I tried on region with not much, created oar of 5522 assets in 9.2 seconds resulting file 377mb
oar server is independent and runs separate from opensim server, handles REST commands. example
# curl -s -X POST 127.0.0.1:6010/archive \
-H 'Content-Type: application/json' \
-d '{"regionId":"a90db57d-a6e4-498f-b40c-4faaf00b3dd7","regionName":"Holoneon","sizeX":512,"sizeY":512}'
[returns job id]
{"jobId":"ca00aaa7-1615-4532-af9c-669453233903"}
[get status of ongoing/complete job]
# curl 127.0.0.1:6010/jobs/ca00aaa7-1615-4532-af9c-669453233903
{
"jobId":"ca00aaa7-1615-4532-af9c-669453233903",
"state":"done","elapsedSeconds":9.2,
"queuedUtc":"2026-07-10T15:59:12.0319843Z",
"fileSizeBytes":394976391,
"fileName":"Holoneon-20260710-155912.oar",
"filePath":"/opt/OarServ/Holoneon-20260710-155912.oar",
"objects":51,
"assetsWritten":5522,
"missingAssets":0,
"error":null
}
if you know how the oar module works in opensim server, batch process 100 assets at a time with callbacks that clobber the CPU and take ages to complete.
separating oar creating from opensim service gives us opportunity to be fast :) since regions run in RAM we have to trigger a disk sync with 'backup' or restart the region first.
| Fred Beckhusen: convoar is great but command line only wotks on Loonix. 47 minutes ago |