Feature #12193
Puppet should warn when a master is launched under WEBrick.
| Status: | Investigating | Start date: | 01/26/2012 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected Puppet version: | Branch: | |||
| Keywords: | ||||
| Votes: | 0 |
Description
It’s not uncommon for me to encounter people using WEBrick in production and ask about its inability to scale. They just haven’t been exposed to why this is a bad idea.
My proposal is that when a puppet master is started with WEBrick, Puppet should present a warning such as the following: A Puppet Master has just been started under the WEBrick web server which is meant solely for development and/or experimentation. If you intend this Master for production use, please visit http://docs.puppetlabs.com/guides/scaling.html.
History
Updated by Daniel Pittman 4 months ago
- Status changed from Unreviewed to Rejected
Ryan Coleman wrote:
It’s not uncommon for me to encounter people using WEBrick in production and ask about its inability to scale. They just haven’t been exposed to why this is a bad idea.
My proposal is that when a puppet master is started with WEBrick, Puppet should present a warning such as the following: A Puppet Master has just been started under the WEBrick web server which is meant solely for development and/or experimentation. If you intend this Master for production use, please visit http://docs.puppetlabs.com/guides/scaling.html.
We are more likely to drop the WEBrick based default “master” mode in favour of only working under Rack. (Which, if people really want to use WEBrick, they can, because rackup supports it).
Updated by Nigel Kersten 4 months ago
- Status changed from Rejected to Investigating
Hang on Daniel.
The original goal does not deserve outright rejection.
We need to inform users when they’re using a master in a certain context that will not scale that they are doing so.