Beni Gartenmann

@SamCRichard @samwhoo @ngrokHQ @simonswiss are you still looking for your next job? Sounds like you :)

Was lucky enough to meet @samwhoo last year and even more lucky to bring him onboard @ngrokHQ to write beautiful, well-considered things. Looking for someone who can help keep that high bar in video. Suggestions for devs who like to produce video content would be appreciated!

@cooperx86 Wow! That encourages me to bring my old Rails 6 code base up to 8.1 as well. Any tips and tricks?

At the weekend I brought an ancient Rails 6 app up to modern Rails 8.1 standards with all the Rails 8 bells and whistles, jQuery ripped out for Stimulus and Turbo, etc. It took two days and a lot of arguing with Claude Code but it nailed it. A job I'd been putting off for YEARS.

@aviflombaum Not sure if it's the best, but it's simple and does the job for me: github.com/hschne/puny-mo… I've deployed it as a Kamal Accessory alongside my app.

What's the best way for me to see load and resources on a server these days? Looking for a sleek and easy to setup web interface, self-host if possible.

@jackmcdade Definitely look at matthiasott.com I think you will especially like the Kontrastor 82M :) He also has a newsletter called "Own your web" in which you can find more inspiration.

Anyone know of any really really interesting personal websites? It’s time for me to redesign mine and I want it to be a living hub for all the things I’m working on and thinking about it. Need inspiration for that kind of thing!

@fractaledmind Been using @apply for years, love it!

The Tailwind community has become too dogmatic about utility-only. Tailwind is utility-FIRST, not utility-ONLY. And @​utility and @​apply are criminally underused. And here is why this matters...

@jackmcdade Wishing you luck!

So wish me luck! And if you have ideas or know of things that actually work (and don't make me cringe), I want to hear them. But like furreal, please wish me luck — I could use the replies. 😘

Going with a new profile and angle on here for the first time in forever. I think I finally found the mental modal on how everything I do, talk about, and create relates. BUILD TO LAST.

@jasonfried Didn't expect the open source part! Nice surprise :)

INTRODUCING FIZZY Have you noticed that every issue and idea tracking tool you loved slowly morphed into boring, sluggish, corporate bloatware? Trello put on 40 pounds of cruft. Jira started charging by the migraine. Asana tried to become everything to everyone. GitHub Issues slipped into a steady state of decline. The whole category is a 20 car pileup of complexity. Time to route around that mess. Today we’re introducing Fizzy. Kanban as it should be, not as it has been. Fizzy is a fresh take on cards and columns, with a few twists, human-nature inspired defaults, and a vibrant interface that’s the opposite of the bland and boring software the industry has been flinging at you for years. Kanban has been around since the 1940s, and Trello brought it into the mainstream in 2011. Since then, some version of column-based kanban-style organization has found its way into any collaboration tool worth its salt. But most have over salted the dish. What was simple is now complicated. What was clear is now cluttered. What just worked now takes work. Fizzy presses reset, reconsiders what really matters, and presents a refreshing way to kanban that just feels right. It’s friendly, colorful, straightforward, and fast as hell. We still use Basecamp for our big, intensive projects, but lately we’ve been reaching for Fizzy to run the smaller ones. It’s perfect for tracking bugs, issues, and ideas, and it shines for lighter, self-contained workflows like podcasts or video production. We didn’t expect it, but Fizzy’s so good it might even cannibalize Basecamp on the lighter side of project management. We’d be thrilled. How much is it? It’s not much for so much. Everyone gets 1000 cards for free. Beyond that, we’ll host your account for just $20/month for unlimited cards and unlimited users. One price for all and everything. No tiers, no “contact us.” No pricing chart at all — just a price tag, like on a pair of jeans. And here’s a surprise... Fizzy is open source! If you’d prefer not to pay us, or you want to customize Fizzy for your own use, you can run it yourself for free forever. Have a great idea? Submit a PR to contribute to the code base and improve the product for everyone. It’s the best of all worlds. No excuses. Every idea comes back around. It’s time for take two on kanban. Fizzy’s our hat in the ring. Let’s make this platform insanely great, together. Come on in! Visit fizzy.do

@kyrylo @TelebugsHQ So true! I'm currently also streamlining some functionality that evolved over time to use the same foundation. It's simpler for us as the solo founder, but also simpler for the user, only one interface to learn!

As a solo founder, consistency and simplicity are your biggest friends. You need to make the best of the limitations you deal with. In @TelebugsHQ, I have two different tables (Project Errors and All Errors) that show similar data, but: 1️⃣ Look different 2️⃣ Have different filters 3️⃣ Drive the same debugging decisions The only real difference is that one aggregates across all projects, the other drills into a specific one. How did we end up here? It boils down to evolving requirements over time. That's why simplicity isn't achievable in one swing. So what I'm doing is unifying the experience. The All Errors view becomes the reference, and the Project Errors table adapts to match. The benefits are glaring: ✅ Reuse the same templates ✅ Reuse the same logic for filters ✅ Fewer bugs to chase It’s very dangerous to venture onto unknown paths when you’re solo, because time is your greatest weakness. The simpler you can deliver, the faster you can move.

@jasonfried Nice! Looking forward to the same concept in Basecamp 5😉🤞

One of my favorite touches in Fizzy are how notification cards change colors when they're done. And when they're stacked up, you can see slivers of cards behind cards. The peek, we call it. This notifications stack sits in the bottom right corner of every screen. It's pictured below. Just a bit earlier today these were blue and orange and pink (each color represents a phase or column a card is in). When the card is done, it turns black. This way whenever you see a black card you know it's done. No matter the collection, black always means done. So at a glance, I can see progress without having to look any further. I know some of those cards were blue earlier and now they're black. "Stuff's getting done" is the signal that sends. And I don't have to go anywhere to know that, feel that, see that — it's always right there in my periphery. Of course I can click the stack, expand it, and see each individual notification. And I will do that later. But for now, I'm good. I got the feel of progress.

@BramJetten System tests?

Guess what I just removed from my 10+ year-old Rails app

That was an easy switch to Kamal local registry deployment! 🎉👏

@deanpcmad @tragioquievera @nateberkopec You're right, and it isn't in my setup, all running locally on the same server. But I guess you referred to the Github Actions setup.

@tragioquievera @benigartenmann @nateberkopec Having your database port open to the internet isn't a good idea...

Rails "DIYstack" (kamal, hetzner, etc) hasn't yet solved reliability and trust for the data layer. People running a business on Rails want backups, push-button recovery, zero-config HA (like Heroku PG premium). You can do a managed DB but you're stuck on hyperscalers then.

@viliusluneckas @nateberkopec Yep! I'm also using a third-party S3 compatible storage, @infomaniak, basically the Swiss Hetzner.

@benigartenmann @nateberkopec Same here. It’s a very simple an handy setup. The cherry on top - solution works with Hetzners object storage!

Somehow I didn't post in this community from the start ... thought there might be some interest, although I didn't add technical details. Maybe I'll write an article about the final setup.

automated db backups working 🎉 I've used github.com/kartoza/docker… but made my own fork to support schema-based backups, as my app is multi-tenant with a schema per tenant - will leave it running for a bit and tweak it, then see if there is interest to merge back.

background jobs working in a separate role/container. I think with this I have the full app working on a VPS deployed with Kamal 2! 🥳 Next up: getting automated database backups

Continuing my quest to get my Rails 6 app + postgres deployed with Kamal 2 today! Let's see where I end up by the end of the day.