Skip to content
← Back to writing

July 20, 2025

Back at it

Five months. That is how long the repo sat untouched. I opened the project, read my own code like it was written by someone else, and started tearing apart the auth system.

The last commit was February 4. Today is July 20. I opened the project, read my own code like it was written by someone else, and started tearing apart the auth system.

The real git log: nine commits on July 20 — the auth overhaul, users.json, sessions.json, the CORS fix, Authentik config — and directly beneath them the last commit before the gap, February 4.

The overhaul

The authentication I built in January was barely authentication. It worked for a demo. It did not work for anything you would let other people use. So I gutted it. New auth flow, new session management, users.json and sessions.json for persistence. CORS configuration that actually respects the origin header instead of just saying yes to everything.

I added Authentik support because I run Authentik on my homelab and maintaining two login systems made no sense.

CORS, again

My screenshot archive has a browser console full of CORS errors. Another shows the same errors under a different configuration attempt. The last one, fixed.png, is just a clean console with no red.

Three screenshots. That is the entire debugging story, and the commit messages do not say much more.

The commit that finally resolved it just says "finally." No description. No details.

More templates, more structure

I added more app templates. Wrote a SECURITY.md. Created a proper branching strategy because I kept breaking things on main. Started a tasks.md to track what needed to happen next, which is the most PM thing I have ever done on a personal project.

The repo is starting to look like something real, with structure and documentation and a roadmap, not a weekend hack or a side project that will rot.

The split

My days are full. I am still managing 12 Scrum teams at Neptune. The kind of days where you come home and do not want to think about process or stakeholders or status reports for at least an hour.

So I open VS Code and I work on HomelabARR instead. It is the opposite of my day job. Nobody is asking me for a status update. Nobody needs a RACI matrix, and I just write code and watch the containers deploy.

I am splitting my time between the job and this project. The feeling at work has shifted. I do not know what is going to happen, but I have learned to trust that feeling, so I am building.

What is here now

HomelabARR has auth that works. CORS that works. A growing list of templates. A Discord. A container image on GHCR, health checks, and a security policy.

It is a tool I built for my own homelab that other people might want to use, not a product or a company. That is enough for a Sunday evening in July.

mjashley.com