3 ms·
> the default Heroku server There is no "default Heroku server" you get exactly what you specify. If you specify nothing you get what Rails runs by default whi
by thinkbohemian 13y ago
> the default Heroku server
There is no "default Heroku server" you get exactly what you specify. If you specify nothing you get what Rails runs by default which is webrick and happens to be awful in production. It's not that "Heroku has a bad default" here but rather Rails' default web server is not intended to run in Production. Most of our docs try to emphasize that you should be using another server other than webrick. Some people want to just bang out a proof of concept and not worry about configuring Puma or Unicorn, for them webrick is fine.
- derwiki 13y agoSorry, that's what I meant. Thanks for the detailed description of what I should have said.
- thinkbohemian 13y agoI understood the simplification to be for clarity of your point, not a misunderstanding. I just wanted to clear it up for any other readers :)
- rubiquity 13y agoDoes Heroku reach out to people that are running WEBrick in production? Or do you have a report or something showing how many are running WEBrick in production? I agree that it takes a lot of ignoring of warnings and documentation to run WEBrick in production, and Heroku's docs do a great job educating people, but nonetheless I meet people (usually 1-2 people startups where tech founder isn't very strong) that are running WEBrick in prod :(
- thinkbohemian 13y agoWe tend to make side optimization recommendations whenever we notice something is wrong and you open a support ticket. We could add it to the warnings at the end, but I can safely say most people don't read them. Still worth having for those that don't, good suggestion.