OnCall published

I published a chunk of software, OnCall (v2), written for work. It uses basic-ass PHP with builtin packages because the environment hosting it is a dark-site, which prevents the easy inclusion of any libraries or frameworks that would have made this much easier, i.e. Django. The application itself is a ground up replacement for a predecessor written by the co-worker who trained me up on our Linux foot print, but has since been unable to maintain it due to their workload. As such, the database design, attribute names, and even layout are heavily influenced by this predecessor. I tried to follow the original as much as possible to encourage ease of use for employees while adding functionality, such as being able to make edits directly through the web app and building the entire schedule template system.

It's the first bit of PHP programming I've done in quite a while (about 12 years or more?) so is messy as hell, but it's functional. Technically the project is under active maintenance and development, but realistically that's entirely dependent upon having enough free time to actually work on it. Future developments will be ported to this public version for as long as I maintain the project.

I've also been writing up a few API clients for relaying metrics and alerts from our appliance based systems (Rubrik, Nutanix, HPE Synergy/Composer2) over to our Prometheus monitoring system. Due to the dark-site infrastructure, we have no access to public tools and I don't want to trust community maintained projects (which would require requesting security audits for every updated release and manually applying said updates). I've been writing these in PowerShell script predominantly because most of our systems run Windows Server (goddesses help me) so I try to make things that can natively run on the jumphosts with both access to the target appliances and the Prometheus ingestion. I'll work on porting those over to public distribution.