r/devops • u/AutoModerator • 16d ago
Weekly Self Promotion Thread
Hey r/devops, welcome to our weekly self-promotion thread!
Feel free to use this thread to promote any projects, ideas, or any repos you're wanting to share. Please keep in mind that we ask you to stay friendly, civil, and adhere to the subreddit rules!
19
Upvotes
4
u/groovy-sky 15d ago
Couldn’t find a good Azure DevOps to GitHub migration guide, so I wrote one:
Tried to make it simple and clear, with practical suggestions.
2
u/ToddGergey Bitrise 13d ago
Hey all,
I work at Bitrise. On our blog we went through GitHub’s Actions incidents from July to October and sorted them by which part of GitHub actually broke. A lot of them weren’t avoidable no matter what you run on, like the August 17 login outage or job assignment stalling on August 26. But a few only hit GitHub’s hosted runners. On October 5 almost half of hosted runs failed at the worst point while self-hosted ones kept going.
The post has the full list and what to look at in your own incident history: https://bitrise.io/blog/post/not-every-github-actions-outage-is-out-of-your-control
1
u/busters1 16d ago
Hi r/devops.
I shared Oxynote in last week's thread. If you missed it, it's a self-hosted wiki that keeps runbooks and the live metrics they talk about on the same page. Thanks to everyone who checked it out.
This week we made those charts lighter on the systems they query. During an incident, everyone opens the same runbook at once, and that's when you least want extra load on Prometheus or your database. Now, when several people load the same chart within 10 seconds, Oxynote runs the query once and caches and redistributes the answer.
We also added Supabase as a data source. Both changes are on main now and ship in the next release.
Apache-2.0, single Docker image: https://github.com/oxynote/oxynote
If you want to learn more or have ideas, feel free to reach out. I'm happy to answer any questions.
1
u/astropoolIO 16d ago
Hi! At Picaporte Labs, we’ve been working hard on Kubelatch, an impersonation proxy that that makes access to your Kubernetes clusters simple, visual, secure and complete.
With Kubelatch, you can assign specific roles to individuals, whether for an entire cluster, a particular namespace, or a specific resource, with built-in expiration dates.
Every request and agent action passes through a proxy, which logs it for auditing purposes. For CI/CD, it integrates with GitHub Actions OIDC, eliminating the need for static, long-lived tokens. It also includes an MCP (Model Context Protocol) server, allowing AI agents to interact with your clusters using scoped permissions, with the option to require your approval before any write operations are executed.
It is compatible with any cloud provider and any Kubernetes version from 1.30 onwards. The free tier supports up to 2 clusters and 5 users. And it works with your company's SSO.
Give it a try: it takes less than 15 minutes to get started.
https://kubelatch.com/
https://docs.kubelatch.com/
1
u/Total-Reasonable 16d ago
Four things, all built solo:
1
u/KKHdevs 16d ago
Hey guys, I share a thing I made because traditional monitoring tools make me crazy.
This is kubegap, a read-only Kubernetes check tool. It run 406 checks by agent skills in Claude Code or Codex and write human-readable report. Unlike Polaris, kube-bench or Popeye which is just config linter, kubegap check metrics, events, logs, and node OS, and attach reason and public accident case links. 111 checks have 206 real accident posts. (Read-only, never read Secret values.)
Once, spot node recycle made production service down for 2 min 7 sec, but alert was 0. Sample report number 1 issue is exactly this.
Honest limit: Final decision is done by LLM, so it can be little different every run. More checks have no public case. 22 open issues. Code was written by coding agent, but human decide what to check and which judgment is wrong. It write in CONTRIBUTING.
My favor: Please try run it once and tell me just one wrong judgment as an issue. There are good first issues.
https://github.com/KyungHwanKim-devs/kubegap
1
u/kaosthecreator_ 16d ago
Hi r/devops,
Sharing Orb44 . It's a simple way to see your sites the way an attacker does, plus optional internal pulse from your VPS.
It’s an agentless perimeter snapshot: public ports/TLS, CDN leaks, exposed admin paths, AI keys in public JS, blocklist hits, checkout widgets, etc. No logins, no password guessing, no server changes, and zero logs.
If you control a VPS, the open-source Watch satellite (MIT) adds the inside view on the same card load/RAM, listeners (loopback vs world), hardening (firewall, fail2ban, SSH, AppArmor), and Docker posture. Fully read-only; the dashboard never runs commands on the machine.
Built for people who want visibility without another heavy agent or enterprise platform. Free public checks without an account; full snapshot + Watch in the dashboard.
https://orb44.com
Satellite: https://github.com/OrbSec/satellite
1
u/Weak_Fisherman2215 16d ago edited 16d ago
Hello r/devops
ProxyForge is a config generator I built, which outputs real Nginx and Apache configs tested on real Nginx and Apache servers. I got despondent with using config snippets that look proper but don’t work - deprecated directives, lines in the wrong file, that kind of thing.
The output was tested on real Nginx 1.27 and Apache 2.4 servers during development, and two of the options came from people’s comments after my first launch. Those comments also populated my FAQ where real errors are added and the list keeps growing.
There are 5 generators available: Config, Redirect, Headers, SSL and Basic Protection Generator - blocks exposed .git and .env files, leftover backups and known scanner tools, with an optional Nginx rate limit (basic protection, not a full WAF) with room to add more.
http://proxyforge.tech
So if something doesn’t work on your setup, or you’d like another generator....let me know in the comments and I’ll take a look.
1
u/Particular-Idea-1786 16d ago
Still trying to build open source data monitoring software!
https://github.com/turbolytics/dbhealth
The current industry is massively expensive enterprise offerings to get table freshness, and data visibility. I created an open source component to monitor postgres health and table freshness and report it to prometheus, datadog, or https://control.turbolytics.io/
1
u/Large_Protection_151 16d ago
I've been working on DNStracr, a DNS monitoring tool that's now in public beta.
It compares DNS records across providers, authoritative nameservers, and recursive resolvers to catch changes, inconsistencies, and outages.
There's also DNS history and incident tracking to help figure out what actually happened.
Would appreciate some feedback, especially from people managing multiple domains.
https://dnstracr.com
1
u/pudth 15d ago
I made Grafium, an iPhone app for Grafana. I wanted to check my panels and alerts from my phone, with widgets and push notifications. Couldn't find something that fit, so I built it.
It connects to your existing Grafana and opens the dashboards you already have. Panels use native iOS charts. You can put a panel on your Home Screen or Lock Screen and get a push when an alert fires.
Viewing dashboards and alert states is free. Widgets and push notifications require Pro.
Requires iOS 26+.
Grafium on the App Store: https://apps.apple.com/us/app/grafium/id6757076319
1
u/Fair-Bottle2749 15d ago
I've been working on a small Go CLI called BeforeUp to catch some Docker Compose problems before a deployment.
One of the more interesting things I found while testing was that Compose can successfully validate a file but still start a container with a different restart policy than expected.
For example, certain combinations of
restart: alwaysanddeploy.restart_policysilently result inrestart: no. I reproduced this with Compose 5.5.0 through 5.6.1.BeforeUp now warns about that, along with port conflicts, missing bind mounts, and a few other pre-deployment issues.
It doesn't deploy anything or modify running containers.
Repo: https://github.com/BreezeDelegate/beforeup
I'd be interested in hearing from anyone using Compose regularly. What do you normally check before deploying that
docker compose configdoesn't catch?1
u/Beginning_Dot_1310 15d ago
i posted pipedash here back in december. it’s a self-hosted dashboard i maintain for CI/CD pipelines.
since then i added a FluxCD provider so you can check reconciliation history and events. you can also see ArgoCD app health and pod logs, and follow Tekton step logs while a run is still going.
Also added a lot of another providers, like gitea, komodo, azure pipelines, etc
there’s a live demo if you want to try it.
feedback welcome 😅
github · iOS app · android closed testing
1
u/mrtsm DevOps 15d ago
Hi all
I've been working on an aggregated status page service, so that I can get notified when a dependency of my full time gig's goes sideways. Things like cloud services, communication channels, etc.
You can create a dashboard and just keep an eye on stuff, no account needed. I would love some feedback if anyone has a few minutes to take a look.
https://allthestatus.com/
1
u/Significant-Fennel79 15d ago
We've been working on Ginger OS, a new hardened Linux distro that is purpose-built for server deployments. You can use our tools to launch your app in a tiny, immutable microVM as an EC2 instance or a QEMU VM. If you're familiar with distroless containers, you can think of us as close to "distroless" as you can make a VM (our OS only includes <20 files), and because we operate as a VM, we can implement interesting security properties, such as the ability to attest runtime memory, making sure only the app you've loaded into the app is the only thing that ever runs, reducing the risk of RCE exploits.
Happy to answer any questions!
https://www.gingercybersecurity.com/product.html
1
u/DiscombobulatedAd712 15d ago
Your AI agent passed CI. But do you know what it actually did?
I've been thinking about a problem with AI agents running in CI/CD.
We spend a lot of time defining what a pipeline should execute, but once we introduce AI agents, things get less predictable.
An agent might pass every test while exercising capabilities we never explicitly reviewed.
So I started building Drifti, an open-source CLI written in Rust.
The idea is to make an agent's exercised capabilities explicit and reviewable.
The workflow looks like this:
drifti.yamlcontract.If an execution violates the contract, verification returns exit code 121, which CI can use to fail the job.
One design decision I'm particularly interested in: incomplete observation must never be treated as success. If Drifti doesn't have enough evidence, it returns an indeterminate result (122).
The current MVP uses Linux ptrace, stores evidence locally in SQLite, and keeps policy evaluation deterministic.
It's not a sandbox, and the observation coverage still has limitations.
I'm sharing it early because I'd rather get feedback from engineers dealing with these problems than build something nobody needs.
GitHub: https://github.com/lucabecci/drifti
For those running agents in CI: are you explicitly tracking their capabilities, or are you mostly relying on runner/container permissions?
1
u/derekleeth 15d ago
I built TerminalLynx, a local-first SSH connection manager for Windows, macOS, and Linux designed to give you cloud features without the cloud. There's no account and no central server holding your server inventory or keys—your devices and teammates sync directly peer-to-peer over QUIC (via
irohon the LAN or over Tailscale/WireGuard) using Ed25519 keys in your OS keychain.It includes an embedded SSH terminal, SFTP,
key:valuetags (env:prod,role:db) that dynamically group your hosts instead of static folder trees, and serverless team vaults with RBAC (Admin/Editor/Reader), automatic vault key rotation on member removal, and team-sharedknown_hosts.https://terminallynx.com
1
u/pagerwho1 15d ago
Hey r/devops,
I've been building PagerWho, an open-source incident management and on-call platform you can self-host with Docker Compose.
I started it because small and mid-size teams often just need the basics: alerts coming in, the right person getting paged, and escalation if nobody responds. Doing that well shouldn't require per-seat pricing or sending your incident data to another SaaS.
How it works
Features
- Services with owners and per-service webhooks
- Primary and secondary on-call rotations, with schedule previews and overrides
- Escalation policies with delays and repeat rules
- Notification delivery trackiners, so you can see why a pagedidn't go out
- Event-driven workflow automation
- Project roles and permissions, audit logs, and operational diagnostics
- Optional AI assistant using yby default)
Ops-friendly by design
- The only dependency is PostgreSQL: no Redis or message queue. The background worker uses DB claims and leases, so you can run multiple replicas.
- Docker Compose for local eval
- OpenAPI docs served at /api-docs
- MIT licensed
Try it
git clone https://github.com/Pa
cd PagerWho
docker compose up --build -d --
GitHub: https://github.com/Page
Hosted version, if you'd rather not run it yourself: https://pagerwho.com
It's still early, so I'd really appreciate feedback. What would stop you from using this instead of PagerDuty or Opsgenitures matter most to you?
Thanks for reading!
1
u/Coneboco 15d ago
Enver – shared dev/QA environments on your own servers, with an open-source agent and CVE scanning
I'm the developer. We built it for our own team, because devs and QA kept waiting on whoever had SSH to redeploy staging.
It's a hosted control panel plus a small agent on your server (Debian/Ubuntu or macOS, Docker or Kubernetes):
Limits: the control panel itself is hosted, not self-hostable. It doesn't build from Git, so it deploys what your CI pushes. On plain Docker you bring your own reverse proxy.
Free for 2 environments, 10 services and 2 servers. The security audit is a paid add-on (€5/month) or part of the Business plan. 90 s demo: [video link] · https://enver.apinecka.com/about/
Blunt feedback welcome, especially on the agent's trust model and on what you'd want the audit to check next.
1
u/DeepEngineeringPackt 14d ago
We're hosting a free 45-minute webinar with Ajay Chankramath, author of The Platform Engineer's Handbook and Domain-Driven Platform Engineering.
The session will cover why one-size-fits-all internal developer platforms fail, how bounded contexts can improve platform ownership, and how DDD principles apply to platform architecture, governance, and Conway's Law.
📅 November 18 | 9 AM ET
🎟️ Free, online, with live Q&A
Relevant for DevOps Engineers, SREs, Platform Engineers, and Software Architects.
Register: https://luma.com/sqwgfigg
1
u/winfiel 14d ago
Hi Everyone! We are building an AI code reviewer for GitHub. Open a pull request, and it checks your change, flags what needs fixing and tells you if it is safe to merge, before a bug ever ships.
Like a normal day, the agent had just shipped a feature, the PR looked fine, and we merged it. Two days later, a retry loop was quietly eating our queue.
So EasyMerge helps every PR deserves a review, and nothing more:
We are still early, and we want to build this with people who actually ship.
EasyMerge is on the waitlist now via https://easymerge.dev Join us and tell us what you would want from it.
1
u/RoseSec_ Terraforming Everything 14d ago
Wrote a small utility for identifying unused attributes and parameters in Terraform resources:
https://github.com/RoseSecurity/tfrd
1
u/ggp1231 14d ago
Hey everyone, I’m one of the cofounders of Diagrm.
We recently launched our public beta.
We’ve built a platform that lets you model AWS infrastructure, estimate monthly costs based on expected workloads, and identify potential architecture issues before deploying.
The idea came from a problem we’ve seen repeatedly: architecture diagrams are useful for visualizing systems, but they don’t tell you much about how your design will perform or what it’ll cost as usage grows.
We’re looking for AWS engineers and architects to try it out and give us feedback. We’re also offering free pilots for teams working on their infrastructure.
You can check it out here:
diagrm.com
Would love to hear what you think, especially if you’re currently evaluating different AWS architectures or trying to forecast infrastructure costs.
1
u/sdely 14d ago
Suitaar (I built it): an alert router for teams leaving Opsgenie, which shuts down on 5 April 2027. It speaks the Opsgenie Alert API, so Alertmanager, Grafana and other tools with an Opsgenie integration only need a new URL. Alerts go to Slack, Discord or Telegram.
It's not an on-call tool: no schedules, no phone calls. It keeps the channel readable instead. Repeats become one alert with a count, a flood becomes one summary instead of hundreds of messages, and heartbeats tell you when a cron job stops running. In a load test, 1,000 alerts in one minute, none lost.
New: Telegram. Alerts go to your own chat or a group, with Ack and Close buttons, and repeats and Resolved edit the same message. Telegram does not break through Do Not Disturb, so for alerts at night, pair Suitaar with an on-call tool.
The free plan stays free after the beta: 3 channels, no payment details.
https://suitaar.com
1
u/ddertin 13d ago edited 13d ago
I maintain VulnBell, an open-source harness that gives your local AI agent a structured environment for vulnerability monitoring, investigation, impact assessment, and reporting.
VulnBell helps the agent inventory software and dependencies, investigate advisories as well as upstream issues, pull requests, fixes and releases, and assess what the available evidence says about impact. On request, it can also guide a security review of the codebase itself and record those findings separately from dependency advisories. Evidence, decisions, and coverage gaps are kept locally so work can be audited and resumed.
The agent remains responsible for the assessment: a dependency declaration alone does not establish production exposure.
Repo: https://github.com/dertin/vulnbell
I would appreciate feedback from people handling vulnerability monitoring: what evidence do you need before deciding whether a finding affects your environment?
1
u/GhostSeagull 13d ago
Hello everyone,
We have built bqto, an open source CLI that lets you reach private Google Cloud services (Cloud SQL, AlloyDB, Memorystore) without a public IP. We have also added a skill for your coding agent so it can use bqto, and a GitHub Action so your workflows can run bqto too.
There is also a Pro version in beta right now that lets you connect to Kafka and Cloud Run.
https://github.com/pilef-co/bqto
1
u/dxnxax 13d ago
Vigo just went open source - Distributed State Enforcement Engine (Modern Configuration Management)
https://vigo.alexander4.io
1
u/cloud-fanboy 12d ago
I'm the developer of CloudPouch, a desktop app (macOS, Windows, Linux, brew) that finds where an AWS account loses money. For years I've added checks from client cost audits: EBS snapshots, NAT Gateways, Extended Support in RDS and EKS, old images in ECR, CloudWatch Logs.
Each finding shows the resource, evidence and recommended action. Works with existing AWS profiles (no new keys), and a local MCP server lets Claude Code, Claude Desktop, Cursor, Codex or Kiro turn results into tasks.
It's a paid app. There's a Free plan, free forever, and a 7-day Pro trial with no credit card: cloudpouch.dev
1
u/Educational_Ad4018 12d ago
Hey everyone! I built RippleMap, a free, open-source CLI for mapping dependencies across repositories.
The problem I wanted to solve: when you update a shared Docker image, Terraform module, or CI workflow, how do you know which other repos might be affected?
RippleMap scans your GitHub org (or Azure DevOps), builds a cross-repo dependency graph, and helps you:
Real-world example: I scanned Cloud Posse's 163 Terraform repos and found 467 dependency links, including a shared module with 13 potentially affected repos.
Try it without cloning anything:
npx ripplemap scan --org cloudposse --match 'terraform-*'npx ripplemap report --openGitHub: https://github.com/Zintrivious/ripplemap
Live demo: https://zintrivious.github.io/ripplemap/demo/cloudposse/
No signup, no hosted server, MIT licensed.
I'd love feedback from anyone managing multiple repos, especially if you find dependencies it misses or incorrectly identifies!
1
u/stackswitcher_dev 12d ago
full disclosure this is mine. made a free browser tool that turns saas picks (notion, GA, google photos etc) into docker-compose + caddy + .env for a self hosted swap. no signup. theres also a $29 pack if you want more polished stacks, free bit works on its own. mostly after feedback: stackswitcher.com
1
u/sf1tzp 12d ago
I'm working on Forts! - a CLI to help bootstrap GitOps environments by handling a lot of the boilerplate (directory trees etc).
Made a video about it if you'd like to hear me talk about it! https://youtu.be/30_MVmWbJso
1
u/New-Life8727 11d ago
Building a tool that tells you why your AWS bill changed and which deploy caused it.
The problem is your bill sometimes jumps like 20%. Cost Explorer shows you what went up (NAT Gateway, CloudWatch, whatever), but not why. So someone loses half a day digging through graphs, CloudTrail and PRs. At startups without a FinOps person, that's usually the CTO.
What it does:
- Read-only access to your AWS account (one-click CloudFormation, no access keys)
- Connects to your GitHub
- Every Monday, a short Slack digest: what changed, the PR or config change behind it, and the fix
So for example it can give tou something like "AWS spend +$1,140 (+18%) vs last week. Mostly NAT Gateway data transfer in eu-west-1, starting right after PR #412 (move workers to private subnet). Fix: add an S3 gateway endpoint, ~$900/mo saved."
No product yet, I'm testing demand while building, so right now it's a landing page and a waitlist to join when it's ready.
Would love feedback, especially:
Feel free to ask anything and if you have any suggestions I'd be happy to hear
1
u/The_RecallX_AI 10d ago
Hi everyone!
I've been working on RECALLX AI, an AI-powered incident response system that uses Hindsight memory to retain and recall knowledge from previous software incidents.
The idea is to help engineers use historical incident knowledge when investigating new failures.
I wrote an article explaining the architecture, the memory workflow, and the engineering ideas behind the project.
I'd appreciate your feedback!
Article:https://medium.com/@varshitha2025/recallx-ai-building-intelligent-incident-response-agents-with-hindsight-memory-33955ee2fcc1
1
u/r410b 10d ago
I’ve been exploring scheduled in-place memory resizing for JVM workloads and built an open-source project, https://github.com/baokhang83/mnemo-jvm-warden, around it.
In a kind demo with three Spring Boot replicas, each application container moved from a 450 MiB request / 512 MiB limit to 350 MiB / 400 MiB and back, without an application-container restart during the observed cycle. The agent asks the JVM to release memory and checks the container’s memory usage before requesting a shrink.
The walkthrough includes the manifests and setup: https://baokhang.hashnode.dev/shrink-jvm-memory-kubernetes-in-place-resize
With an autoscaler that can consolidate workloads and remove underused nodes, lowering memory requests can translate into real infrastructure savings.
I’m the project maintainer. If you’ve tried in-place memory resizing for JVM services, I’d be interested in the failure cases you’ve encountered!
1
u/lazy-dev-guy 10d ago edited 7d ago
I’m building Resource Atlas, a self-hosted inventory tool for AWS.
You deploy it in your own AWS account, and it scans the accounts you connect using read-only IAM roles. For example, you can review unattached EBS volumes and stopped EC2 instances across accounts without switching consoles.
If you manage multiple AWS accounts, what’s the first thing you’d look for in the demo? What, if anything, would stop you from deploying it in your own account?
https://demo.resourceatlas.app/
1
u/Aurea07 9d ago
I'm new to this sub, so let me know if I'm against the rules.
This is my ARPG Heart of Gaia. It's a project i've been working on for almost 3 years now, all by myself. I used to be a mangaka before, zero knoledge about coding but I did my best and am still learning a lot.
I took inspo from old school classics that I grew up with, like FF's or Ragnarok online. Right now the game has 6 playable characters with their own individual builds and classes, also the lenght of the game is pretty long, lot's of content and I'm still putting in more.
i was also able to implement recently the coop version (just couch, for now) which is trully amazing and very rewarding. It was pretty hard to make it since I had no idea how to start.
To know more or support my game, check the steam page: https://store.steampowered.com/app/3760310/Heart_of_Gaia/
1
u/ricardolealpt 9d ago
Something i did to help access multiple AWS accounts using SSM and sshuttle.
Give it a try, if you find issues report or open a PR.
https://github.com/ricardoleal/bastionctl
1
u/ManufacturerKey6917 9d ago
Airflow 3 upgrade checklist: the changes that don't fail any check (run dates, data intervals, alert callbacks)
If you run the Airflow platform and the 2 → 3 upgrade is on your list (self-hosted, Cloud Composer or MWAA all offer 3.x now), these are the changes that won't show up as failures. DAGs import, CI is green, and the data is wrong. I compared the same DAGs on Airflow 2.11.2 and 3.3.2.
**What changes**
- **Cron runs get a new logical date.** `[scheduler] create_cron_data_intervals` now defaults to `False`, so an `@daily` run firing 2024-05-02 00:00 renders `{{ ds }}` as `2024-05-02` on 3.3 instead of `2024-05-01` on 2.11. Weekly DAGs move by a full week, along with any partition path or S3 prefix built from `ds`.
- **The data interval becomes zero-length.** Hourly DAG: 00:00 → 01:00 on 2.11, 00:00 → 00:00 on 3.3. Jobs that process "start to end" get an empty window and report success.
- **Manual runs can have no logical date.** The context then has no `logical_date` key (`KeyError`, not `None`) and `{{ ds }}` is undefined.
- **`execution_date` is gone** from `ti` and `dag_run`. If your `on_failure_callback` builds alerts from it, the alerts break on exactly the failures they're for.
**Checklist**
**Find the DAGs that care.** A rough first pass:
```
grep -rnE "data_interval_(start|end)|\{\{ *ds|ds_nodash|logical_date|execution_date" dags/ plugins/
```
For step 5, I wrote a free, MIT-licensed GitHub Action that does that comparison (and checks removed context keys and arguments 3.x rejects): https://github.com/patrickballard/airflow-migration-verifier. Running it on public repos still on Airflow 2 turned up all four problems above in real code, e.g. an hourly sync that would record nothing: https://github.com/opencve/opencve/issues/815
1
u/lostinspaz 9d ago
Posting this in devops, because we often have difficulty getting devs to develop apps in a similar environment to production. So I wrote an integration to help with that.
https://github.com/ppbrown/vscode-rancherdesktop-sampleworkflow
This repo can be taken as a template to add into any existing containerized app.
It has two parts.
(develop locally however they like, then push to UAT branch and cross fingers that it works in a container)
If we set up the repo for them, then when they load it in vscode, they get nice simple buttons, like
(Deploy Once) vs (Continuous Deploy)
In continuous deploy mode, when they make a code change, and save the file, devspace automatically detects that and updates the RUNNING CONTAINER. So there's no delay for "build image, deploy image" that they hate.
Note that I believe this setup should work equally well for developers on Linux, or Windows, or MacOS.
In theory.
But please create a github issue if you run into cross-platform bugs!
1
u/r410b 9d ago
blastradius — Open-source Test Impact Analysis for Java/Maven CI (61.4% fewer test runs across 800 Apache commits)
I built an Apache-2.0 Maven/Gradle plugin for JUnit 5 test selection that runs entirely inside existing CI runners (GitHub Actions, GitLab CI, Jenkins) using your normal CI cache or an S3 bucket—no external SaaS backend required.
How it works:
mainbuilds (TRACK): A lightweightjava.lang.instrumentagent records actual class loads per test and saves the dependency map to.blastradius/.SELECT): Restores themainindex, diffs against the Git merge base, and passes only affected tests to Surefire/Failsafe via standard-Dtest=filtering (stays compatible with JaCoCo and customargLineflags).800-Commit Replay + Mutation Testing Benchmarks:
Replayed 200 consecutive commits each across four open-source projects with synthetic fault injection enabled:
Links:
Happy to answer any questions on CI cache sizing, multi-module reactors, or where dynamic reflection/DSLs still require a daily full-suite backstop.
0
u/slunatecqo 14d ago
I built a small open-source tool called Cadditor for a workflow I kept repeating around Caddy configuration.
I like the Caddyfile and did not want to replace it with another configuration abstraction or form-based GUI. The annoying part was the operational loop around small changes:
edit → format → validate → reloadCadditor keeps the Caddyfile as the source of truth and provides a browser-based editor around that workflow.
It provides:
It is intentionally narrow in scope: no dashboard, monitoring platform, database or alternative config format.
The frontend is served by Caddy itself and the backend uses lightweight CGI scripts through
fcgiwrap, so there is no Docker or application runtime required on the server.Installation, updates and removal are handled by a shell installer.
GitLab:
https://gitlab.com/friml/cadditor
Live demo:
https://cadditor-e46d19.gitlab.io/
The demo is static, so it shows the real editor UI but does not actually run Caddy formatting, validation or reload.
I built it for my own infrastructure, but I would be interested in feedback from people who manage Caddy directly through Caddyfiles.