title: Puma without nginx - multiple ruby applications on the same IP:PORT
body: <p>Nginx importance in production was normally based on its ability to serve slow clients; In the setup of RESTful API it seems to be an unnecessary layer to the production stack, especially as Puma (unlike the widely used unicorn can handle nginx work). </p>
  
  <blockquote>
    <p>Puma can allow multiple slow clients to connect without requiring a worker to be blocked on the request transaction. Because of this, Puma handles slow clients gracefully. Heroku recommends Puma for use in scenarios where you expect slow clients.
    <a href="https://devcenter.heroku.com/articles/deploying-rails-applications-with-the-puma-web-server#slow-clients" rel="noreferrer">ref</a></p>
  </blockquote>
  
  <p>How to enable Puma to serve multiple ruby applications on the same port without using nginx as a reverse proxy?</p>