This is a great question. For the launch this is by repo, which is okay for our organization because our four pods each have their own codebase. We look at DORA at a team level, and if the metrics aren't where they need to be we dig into the lower level to see where friction is. Are tickets not where they need to be? Too large? ? Is a developer struggling with a particular work etc.
I'll put a feature on the roadmap (first user item that came from feedback thank you) that lets you aggregate multiple repos together for that use case!!! Super helpful and quite easy to accomplish.
I just released Are We Deploying in beta — built on my belief in DORA Metrics. I've been running engineering teams for 15 years, and I believe in these metrics for engineering health over crap like burn down, and story points.
The app currently supports GitHub and Uptime Robot, my personal stack, and the tools where I work. A feedback widget is live with the app. Give me the Good, bad, integration requests, anything. I want to hear it all. Thanks for looking.
One of the many use cases, but basically yes. Other use cases: Home automation, remote backups, media servers, photo libraries, AI assistants... you name it!
It's a vpn from the original definition before vpn meant a proxy to get around geoblocks. I use tailscale for my home servers, my routers, for servers I have in other houses all behind NAT. I have half a dozen raspberry pi print servers in two warehouses also behind NAT and they can connect to each other and I can connect to them from CGNAT
Eizo CS2740, really happy with them. Weird anecdote: they weren't available in the US at the time yet, so I got them off amazon.co.jp, and it was the most impressive thoughtful multi-layer cardboard packaging I ever got from any reseller. Probably my disdain for Amazon worker treatment and appreciation for Japanese care no matter what, all standing there in one impressive confusing package.
I use an APC with a management cable, triggers graceful shutdown and startup on reconnection. It also e-mails me and stores a log. I prefer this approach so 99% of ecosystem isn't on the server, you can let your server do server things and not be the battery police.
shutdowns can be done in software like 'sudo systemctl halt', so it doesn't need a line straight to the motherboard. That's the desired path because it lets running applications gracefully close and finish writing to disk.
I'll put a feature on the roadmap (first user item that came from feedback thank you) that lets you aggregate multiple repos together for that use case!!! Super helpful and quite easy to accomplish.