From reading about Omarchy and community reactions it sounds like DHH is a successful grifter, milking money from corps with pictures of agentic promised land. HOWEVER grift will go bust at some point: does anyone remember SaaSpocalipse that did not materialize,along with numerous articles from people with degrees pointing out that there’s no data supporting claim that AI is actually making money for it’s peddlers or consumers. AI grifts will continue until “market” will finally acknowledge it for what it is (it’s just a new shiny tool, no more) and all the myths go bust and investors will want their money back. So - yes money got “stolen” from actual OSS projects that keep world’s lights on, yes vibecoding has not been proven to scale or endure multiple decades like Debian, Gentoo, Fedora etc. so it’ll collapse from technical standpoint, but it WILL collapse unless DHH will start applying those grants towards hiring engineers. Token money are not worth paper they are printed on so everybody just chill and let this trainwreck go off the cliff on it’s own. Shame DO got into it though… but for all the major cloud platforms who isn’t supporting fascism? What differs is the scale.

if you care to walk “on the wild side” I’d say use LVM, create one big volume covering entire drive then do 50G for / and 20G for /home . I use ext4 since it offers live resize2fs. So the drill is: you set up OS etc. and whenevr you get closer ti the allocated limit bump it by 5G with lvresize + resize2fs which allows you to “grow into” your setup. Also allows snapshots of running OS in cases of iffy updates OR parallel second distro install with subsequent distro removal and space still being at your disposal after it’s gone. BTRFS is fun but offers less flexibility than LVM IMO.

Try either one and see for yourself. I would recommend to partition carefully isolating /home so that you can wipe distro but keep your files and settings. Distro pick is rather personal thing - folks find their groove in various ways. I’m on Fedora and have been with Fedora for ages, never owned Windows machine so I’m not your average user, BUT looking at self-starters today I do see a lot more gravitating towards Fedora whereas previously I saw more Ubuntu jumps. YMMV, but distro-hopping is not a bad thing. Partition wisely and pains of distro-hopping won’t be as pronounced 😃

exactly that. It’s about personal attachment of sorts. If you don’t feel passionate about it chances of you sticking around are slim. Depending on what your setup is - attempt to expand range of OpenSource tools you use daily, and in the process you may find tools that look great to you but lack function or polish or something else, so that would be the first “dive” and from there it would be easier to expand further

both

thank you folks. Your input gives me a decent starting point. I’ll start digging based on info/experiences shared, maybe I can find someone locally selling old GPU with enough ram for cheap

well, I intend on scavenging for parts as I can’t really afford today’s prices. And since I don’t really know what should I grab as minimum specs I don’t even know what to look for. I could try to look for old(er) gaming rigs people sell or maybe there are some business workstations that may be sold in bulk. Either way, knowing what’s the minimum viable set of specs for running qwen or claude locally would be helpful

I’ve got some circa 2010 cards laying about with a 32Gb server that already has 8Gb carved out for TrueNAS, so essentially I could squeeze 16-24Gb out of it, but it’s an older i5 Intel CPU

My opinion is that of the two Postres is more “adult”. So if you want to"just wing it" MariaDB would work, but if you’re serious Postgres is a better choice. However Postgres also requires better understanding of you setup etc. So it’s a ROI game - what’s more important to your project, how complex your DB is, what are the requirements for availability, transaction security etc. There is no “better” or “worse” there’s “feasible” and “prohibitive” 😉

I’m not convinced what you run into is a specific podman issue. It’s a resource issue and configuration issue likely. “vanila” podman with proper rootless containers will run as much workload as machine can handle from my experience. My company costomers seem to be running production workloads with it just fine.

Oh wait, by rootless container you really meant running podman rootless? still don’t see an issue though. What specifically are you doing? I mean, what’s the configuration and what’s the workload?

@mgdigital, first thing I’be noticed: reliance on “heavier” database stack (pg + redis), at least from the first glance at docker-compose. My suggestion would be to have an option for minimalist setup with sqlite and without redis if possible. That would work better for those of us flying with minimal hardware (rpi, old PC and such).