RVS_MediaServer VS octo

Well, these ones aren't "half-baked," but they are no longer being maintained (archived):

[0] https://github.com/RiftValleySoftware/RVS_IPAddress

[1] https://github.com/RiftValleySoftware/RVS_ParseXMLDuration

[2] https://github.com/RiftValleySoftware/RVS_ONVIF

This project is unfinished (I just walked away from it, as it wasn't really giving me what I wanted):

[3] https://github.com/RiftValleySoftware/RVS_GTDriver

This one is "half-baked," I believe. I never really took it particularly far:

[4] https://github.com/RiftValleySoftware/RVS_MediaServer

I did something similar for Mac, a while back[0]. I never really developed it much farther, because of the latency issues. Since it was for surveillance cameras, that was a showstopper.

[0] https://github.com/RiftValleySoftware/RVS_MediaServer

https://github.com/quadnix/octo

I have been trying to release this for some time now. Its a wrapper on top of cloud technologies, like AWS, so developers don’t have to understand low level devops operations.

Much like AWS CDK or Terraform, but build around familiar concepts like Server, Environment, Deployment, Regions, etc.

Its a framework that allows you to write your infrastructure in code, and an example in English would be like,

Hey Octo, build me a region in US East with QA and Staging environment. Build my Backend repo, publish my docker image, and run it in QA, then promote to Staging.

Of course this would be written in code, which would roughly be about 10-20 lines of code, easily testable, and easy to understand.