buchanae

I initially reached for Docker actually, but when I started researching how to run it securely, I just thought "I don't need this. Systemd is already there and does all of this in an easier and more direct way".

I moved all my stuff from AWS to a Hetzner VPS recently. I don't have much, and AWS was actually cheaper, but I'm so much happier having everything in one, simple spot.

There's a gap in my knowledge so far, which I think is mirrored in this post: I have been piecing together my server by hand, and I _know_ I will regret this at some point, but I don't know how I want to solve this yet. I don't want to involve Docker in this setup. Perhaps I should go back to Saltstack or Ansible, or maybe there's something in Nix for me, or snap/flatpack maybe, I don't know. There's a good chance I'll just never solve it, but it seems like there's a gap there that's waiting for a great, simple, small solution (or it exists and I just don't know about it).

So after all these years (decades now) of learning and working in linux every, single, day, I still have a lot to learn! :D

I'm interested, tell me more. What about Oxide attracts a homelab user?

A lot of tech debt I've seen stems from people tacking things onto a loose foundation – adding API endpoints when there's no clear pattern, adding validation or defaults in different ways, organizing layers of code in various ways, multiple implementations of the same business need.

This is compounded when people come and go. The software/tech industry, in my experience, does not encourage long tenure – layoffs, reorgs, and the general trend of people hopping between employers every 2-3 years.

Startups also love the idea of building things fast and ugly, and 5 years later that leaves the company with a successful product (hopefully), a team that's grown fast (and turned over multiple times), and a shaky foundation.

Engineering generally seems open to paying down tech debt, but there's an overwhelming amount of it sometimes, and someone needs to deeply understand the problem and lay out a clear plan for taking care of it, and that takes serious effort.

I haven't written about it much yet, but atlas9.dev has an infrastructure component to it. I actually spent most of today researching and experimenting with infrastructure and I plan to write about it soon.

atlas9 is about setting up a foundation/framework for building and deploying apps that takes care of more of the common issues. Infrastructure (build, deploy, monitor, config, secrets, etc etc) is a big part of that. I've been focused on the application code lately, but I suspect infrastructure is where the meat of the problem lies.

Hm, leveraging CloudKit is smart. I am fully assimilated into the Apple world.

I'm a little wary of something watching my clipboard, honestly. A lot of passwords and sensitive information goes through there.

Drag-and-drop into a menu bar icon is super clever though.

Well done. It might be a little more than I need, but I'm cheering you on nonetheless.

I can relate to that. I have a ton of bookmarks and open tabs that I've been meaning to read for weeks or months now. I guess that's why I'm hoping a daily reading list might give me a bite-sized chunk to work through.