I released kamal-backup today.
There are Kamal accessories for database backups. None do Active Storage. None use restic. None ship restores, drills, or evidence for security reviews.
So I built one.
https://t.co/U9QuGBLvMW
I've been seeing a lot of "claude just killed our startup" type posts.
important reminder: build for normies. don't build for ai native people setting up openclaw and living in Claude Code everyday
lots of opportunities out there.
if you build for ai native folks, you better be focused on data moats or something extremely defensible (if you can find it)
@ben_makes_stuff@Steelcase I have a Steelcase Gesture, going on maybe 8+ years old. My only gripe, is their replacement parts network is complete shit. Parts should be more available, I shouldn't have to go through a separate retail network.
🚂 Announcing ClaudeOnRails!
Hey everyone! Just released a gem that might change how you build Rails apps. ClaudeOnRails creates a swarm of specialized AI agents for your Rails project:
• Architect (coordinates everything)
• Models, Controllers, Views specialists
• Testing expert
• Services, Background Jobs
• DevOps
Instead of manually switching contexts, you just describe what you want in natural language. The swarm automatically implements across all layers following Rails best practices.
gem 'claude-on-rails'
rails generate claude_on_rails:swarm
claude-swarm
Then once in the console say something like: "Create a shopping cart with Stripe integration"
Boom. Models, controllers, views, tests, service objects - all coordinated automatically. Brand new and still experimental but should already be useful, especially if you've been looking for an excuse to try agent swarms.
Would love feedback from the community!
👉 https://t.co/bryAIq1gJQ
@kyrylo@igor_alexandrov I'd probably allow it to be chosen in an admin/users/show page. But, interactively you could allow a dropdown, unless users can have multiple roles 😅
@jkostolansky@coorasse@robzolkos This is the way. Just setup CI/CD, push branch, merge branch, let the worker do the deploy for you, wait for the green check mark. And you're live!
@leenyburger Yes, using web-components. For signing/authorization each service has an API that the widget hits to verify.
I've moved to a client-repo / rails-app-repo setup for both. The client side stuff lives on S3.
For frontend if it's not vanilla JS boilerplate setup, I use Svelte.