---
title: "Discussion on \"The PORT Trap: Why rails s Silently Drops Your Puma Bind Directives\" | Hashnode"
description: "Discussion on \"The PORT Trap: Why rails s Silently Drops Your Puma Bind Directives\". How Puma Reads Its Config\nPuma's configuration lives in config/puma.rb. When Puma starts directly (via bundle exec puma), it reads this file and applies every directive — port, bind, threads, etc. — e"
url: "https://hashnode.com/posts/the-port-trap-why-rails-s-silently-drops-your-puma-bind-directives/69c581ec10e664c5da1a73d5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [The PORT Trap: Why rails s Silently Drops Your Puma Bind Directives](https://blog.clearstack.io/the-port-trap-why-rails-s-silently-drops-your-puma-bind-directives?utm_source=hashnode&utm_medium=feed)

How Puma Reads Its Config Puma's configuration lives in config/puma.rb. When Puma starts directly (via bundle exec puma), it reads this file and applies every directive — port, bind, threads, etc. — e

Mar 26 · 6 min read · blog.clearstack.io  
Read the article

-   [#rails](https://hashnode.com/tag/rails)
-   [#ruby](https://hashnode.com/tag/ruby)
-   [#puma](https://hashnode.com/tag/puma)
-   [#overmind](https://hashnode.com/tag/overmind)
-   [#foreman](https://hashnode.com/tag/foreman)

## Written by

[Ajaya Agrawalla](https://hashnode.com/@ajayaa)

@ajayaa

  
[View profile](https://hashnode.com/@ajayaa)

Ruby

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
