15

I'm using Rails 4 with subdomains, and now switched from Unicorn to Puma. Seems to work fine, but when I try to start "rails s" I get:

Rails 4.2.0 application starting in development on http://localhost:3000

I need to run the following

rails s -p 3000 -b lvh.me

to get:

Rails 4.2.0 application starting in development on http://lvh.me:3000

Is there a way to make 'rails s' always to start lvh.me automatically? Used to work like that for me before switching to Puma.

userden
  • 1,615
  • 6
  • 26
  • 50

1 Answers1

27

Rails provide only one way to specify binding host (through -b, --binding argument).

So, I think you have only one simple and appropriate way to resolve your problem. You should create bash/sh alias for running Rails:

alias lvh='rails s -p 3000 -b lvh.me'
Maxim
  • 9,701
  • 5
  • 60
  • 108