---
title: "#rails articles | Hashnode"
description: "Explore 443 articles tagged #rails on Hashnode. Tutorials, guides, and how-tos from the community."
url: "https://hashnode.com/tag/rails"
---

Tag

# #rails

443 posts · 437 followers

[Yashika Vijayvargiya](https://hashnode.com/@railswithyashika) · [Nov 2](https://hashnode.com/posts/rate-limiting-in-rails-8-1-protect-your-apis-without-rack-attack/6ae83a6e77071272c3b17320)

### [Rate Limiting in Rails 8.1: Protect Your APIs Without Rack::Attack](https://railswithyashika.hashnode.dev/rate-limiting-in-rails-8-1-protect-your-apis-without-rack-attack?utm_source=hashnode&utm_medium=feed)

Learn Rails 8.1 rate limiting with practical examples. Explore rate\_limit, custom responses, user-based limits, shared scopes, Redis, and Rack::Attack.

8 min read · [railswithyashika.hashnode.dev](https://railswithyashika.hashnode.dev/rate-limiting-in-rails-8-1-protect-your-apis-without-rack-attack?utm_source=hashnode&utm_medium=feed)

[Josef Strzibny](https://hashnode.com/@strzibny) · [Oct 24](https://hashnode.com/posts/rubyllm-2-x-whats-new-for-your-agents/6adc87515d80815369b421bf)

### [RubyLLM 2.x: What's new for your agents](https://serpapi.hashnode.dev/rubyllm-2-x-whats-new-for-your-agents?utm_source=hashnode&utm_medium=feed)

RubyLLM 2.0 and 2.1 bring a lot of improvements to building agents. You can run the agent loop one step at a time, tools can now wait for a human to approve them and agents can live in the database and therefore survive a restart.

11 min read · [serpapi.hashnode.dev](https://serpapi.hashnode.dev/rubyllm-2-x-whats-new-for-your-agents?utm_source=hashnode&utm_medium=feed)

[Sina Rezaei](https://hashnode.com/@sinarezaei) · [Oct 8](https://hashnode.com/posts/getting-to-know-yourself-understanding-self-in-ruby/6ac79716e5e77d89a128dc50)

### [Getting to Know Yourself: Understanding self in Ruby](https://sinarezaei.hashnode.dev/getting-to-know-yourself-understanding-self-in-ruby?utm_source=hashnode&utm_medium=feed)

Learn how self works in Ruby through objects, scope, and method context.

9 min read · [sinarezaei.hashnode.dev](https://sinarezaei.hashnode.dev/getting-to-know-yourself-understanding-self-in-ruby?utm_source=hashnode&utm_medium=feed)

[Yashika Vijayvargiya](https://hashnode.com/@railswithyashika) · [Sep 22](https://hashnode.com/posts/your-rails-transaction-rolled-back-what-happened-to-the-api-call-email-or-job/6ab251a16e85f876461bce8e)

### [Your Rails Transaction Rolled Back. What Happened to the API Call, Email, or Job?](https://railswithyashika.hashnode.dev/your-rails-transaction-rolled-back-what-happened-to-the-api-call-email-or-job?utm_source=hashnode&utm_medium=feed)

Learn why HTTP requests, emails, and background jobs can become unsafe inside Rails database transactions, and how TransactionGuard detects these side effects.

10 min read · [railswithyashika.hashnode.dev](https://railswithyashika.hashnode.dev/your-rails-transaction-rolled-back-what-happened-to-the-api-call-email-or-job?utm_source=hashnode&utm_medium=feed)

[Chetan s](https://hashnode.com/@mirova) · [Sep 15](https://hashnode.com/posts/what-i-learned-strapping-ai-agents-onto-a-nine-year-old-rails-app/6aa973fab24a4c4fc2d0b377)

### [What I learned strapping AI agents onto a nine year old Rails app](https://buildstuff.hashnode.dev/what-i-learned-strapping-ai-agents-onto-a-nine-year-old-rails-app?utm_source=hashnode&utm_medium=feed)

Nine years of Rails kept breaking our AI agents. The fix wasn't a better model, it was a harness: blocking hooks, a lint ratchet, fresh subagents.

9 min read · [buildstuff.hashnode.dev](https://buildstuff.hashnode.dev/what-i-learned-strapping-ai-agents-onto-a-nine-year-old-rails-app?utm_source=hashnode&utm_medium=feed)

[2](https://hashnode.com/posts/what-i-learned-strapping-ai-agents-onto-a-nine-year-old-rails-app/6aa973fab24a4c4fc2d0b377)

[Shipeasy](https://hashnode.com/@shipeasy) · [Aug 20](https://hashnode.com/posts/ops-queue-for-agents-turning-every-failure-into-a-fixable-ticket/6a865671e3c611164ff3dfa0)

### [Ops queue for agents — turning every failure into a fixable ticket](https://shipeasy.hashnode.dev/ops-queue-for-agents-turning-every-failure-into-a-fixable-ticket?utm_source=hashnode&utm_medium=feed)

At Shipeasy, every production signal that matters becomes a ticket that an agent can act on — no human triage in between. Not a log line. Not a Slack message that scrolls past. A first-class work item

4 min read · [shipeasy.hashnode.dev](https://shipeasy.hashnode.dev/ops-queue-for-agents-turning-every-failure-into-a-fixable-ticket?utm_source=hashnode&utm_medium=feed)

[Shipeasy](https://hashnode.com/@shipeasy) · [Aug 20](https://hashnode.com/posts/when-a-build-breaks-the-bug-fixes-itself/6a86560d342c2ea543799c67)

### [When a build breaks, the bug fixes itself](https://shipeasy.hashnode.dev/when-a-build-breaks-the-bug-fixes-itself?utm_source=hashnode&utm_medium=feed)

We stopped babysitting CI failures. Now a red build files its own bug — and an AI agent picks it up and ships the fix. PROBLEM — A failed build told no one Our CI would fail, and then… nothing would h

6 min read · [shipeasy.hashnode.dev](https://shipeasy.hashnode.dev/when-a-build-breaks-the-bug-fixes-itself?utm_source=hashnode&utm_medium=feed)

[ZeroDrop](https://hashnode.com/@zerodrop) · [Aug 3](https://hashnode.com/posts/rspec-email-testing-without-mailcatcher/6a7112fe2a90e09faa18e149)

### [RSpec Email Testing Without MailCatcher](https://zerodrop.hashnode.dev/rspec-email-testing-without-mailcatcher?utm_source=hashnode&utm_medium=feed)

Test signup, OTP, and magic-link flows in RSpec with no local mail server. No MailCatcher daemon, no regex — just real email verification in CI.

6 min read · [zerodrop.hashnode.dev](https://zerodrop.hashnode.dev/rspec-email-testing-without-mailcatcher?utm_source=hashnode&utm_medium=feed)

[Josef Strzibny](https://hashnode.com/@strzibny) · [Aug 1](https://hashnode.com/posts/why-is-ruby-on-rails-a-great-fit-for-ai-agents/6a6dbb3dd24222b35c8b10e3)

### [Why is Ruby on Rails a great fit for AI agents](https://serpapi.hashnode.dev/why-is-ruby-on-rails-a-great-fit-for-ai-agents?utm_source=hashnode&utm_medium=feed)

Ruby on Rails happens to excel at all things that matter in agentic programming. Token efficiency, predictability, and ecosystem ergonomics makes Rails one of the best choice for robots as it once was for humans.

24 min read · [serpapi.hashnode.dev](https://serpapi.hashnode.dev/why-is-ruby-on-rails-a-great-fit-for-ai-agents?utm_source=hashnode&utm_medium=feed)

[Jeremy Longshore](https://hashnode.com/@jeremylongshore) · [Jul 1](https://hashnode.com/posts/deep-dive-part-1-the-safety-architecture-of-letting-ai-agents-touch-your-production-rails-database-mr1lxvxn/6a449f04e2745faf1ca298d0)

### [Deep Dive Part 1: The Safety Architecture of Letting AI Agents Touch Your Production Rails Database](https://jeremylongshore.hashnode.dev/deep-dive-part-1-the-safety-architecture-of-letting-ai-agents-touch-your-production-rails-database-mr1lxvxn?utm_source=hashnode&utm_medium=feed)

When a language-model agent needs to debug a production issue, it faces a dilemma: either it has no access to live data (useless), or it gets a Rails console (dangerous). There is no safe middle groun

16 min read · [jeremylongshore.hashnode.dev](https://jeremylongshore.hashnode.dev/deep-dive-part-1-the-safety-architecture-of-letting-ai-agents-touch-your-production-rails-database-mr1lxvxn?utm_source=hashnode&utm_medium=feed)
