-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto-detect config file #438
Comments
Looks like puma changes the default development logging when started this way:
but not when we start it via |
Any thoughts about setting puma as the default server, a la unicorn-rails? We love it. https://github.com/samuelkadolph/unicorn-rails/blob/master/lib/unicorn/rails.rb#L35 |
Would that require a separate gem, puma-rails or similar? Or something into Rails, like how Rails will pick up Thin automatically? I would love to see the latter. |
I'd prefer not to require a separate gem. I don't know why an app would have multiple app servers bundled but maybe there's a rare edge case. |
@mperham With regards to setting Puma as the default, Rack will find puma automatically already (rack/rack@e6284a3). Do you think more is needed? |
Sounds good, we're probably on an old rack version. |
If I run
bin/puma
, I'd like it to auto-detect and useconfig/puma.rb
to configure and boot Rails. I'm trying to reduce development friction as much as possible, making the command as easy as possible to start. Runningbin/rails
makes WEBrick easy but we want to test locally with puma where possible. This will make puma one character simpler than WEBrick, thus winning the battle of the development servers. QEDThe text was updated successfully, but these errors were encountered: