Back
Rails
Mentioned in 324 todos by 73 makers.
Mentions over time
Loading...
Sentiment
Loading...
Praised in 10.5% of mentions (site average 9.9%), complaints in 3.7% (average 3.7%).
What makers are doing
Loading...
Often used together with
Do you make Rails?
See everything makers say about it: every mention with praise and complaints, sentiment trends, weekly email digests, and CSV export.
Explore InsightsRecent todos mentioning Rails
#spg
- docs: enforce SLC across v1-v4 plans (remove teaser, simplify v2 tiers, scope v3 to one placement)
- Create logo, add favicons
- Comment out unused RailsFast demo sections in hero and landing page instead of removing them.
- Add Pip-Boy palette CSS variables, sticky bracket navbar, and full-bleed terminal hero.
- Fix active tab to Pip-Boy bracket: corner ticks via text-masked full-width top border.
- Restyle footer to Pip-Boy status-bar: translucent green panels, terminal font, green text
- Register Lexend for body copy; keep Monofonto on headings and terminal chrome
Replace Devise with Rails 8 authentication to simplify code a lot (you might need to log in again, but hopefully everything else still works 🤞)
#wip
I just witnessed OpenClaw go through our Rails admin interface without any special affordances. This means we don't need special APIs anymore for our agents in the very near future.
Im probably going to switch to SQLite for my Rails work now. AI and Worktrees and Postgres are not a great mix. Unless I can figure out how to create a Postgres DB based on a branch name. Anyone else have this figured out?
- Create new Rails app
- Initialise Git repo
- Set up RSpec + FactoryBot + Shoulda Matchers
#splittu
Now that the new
#telebugs version is out, I can focus on
#telesink.
The goal is to build an MVP that’s good enough to launch.
It doesn’t need to be pretty or complete, but it must do one thing well: display real-time events in a feed.
I’m still deciding on the tech stack. Rails is a no-brainer, but the database is trickier. As much as I’d like to use SQLite, my gut says PostgreSQL is the safer choice.
The reason is SaaS support. SQLite won’t scale well here, and ActiveRecord Tenanted being abandoned rules it out for me. If this were a self-hosted-first app like Telebugs, SQLite would be perfect. But it isn’t.
Do some internal refactors which in turn broke parts of the site, but I couldn't deploy a fix because I accidentally upgraded to the connection_pool 3.x gem which does not work with the latest Rails version
#wip
Bug fixing in Company Campaigns creation. Preparing for stages rollout of the new Rails gift card redeem API
#mygoo