File: puppetmaster.README.debian

package info (click to toggle)
puppet 3.7.2-4%2Bdeb8u1
  • links: PTS, VCS
  • area: main
  • in suites: jessie
  • size: 18,912 kB
  • ctags: 13,168
  • sloc: ruby: 210,410; sh: 2,050; xml: 1,554; lisp: 300; makefile: 142; python: 108; sql: 103; yacc: 72
file content (16 lines) | stat: -rw-r--r-- 774 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
By default, the puppetmaster package is configured in
/etc/default/puppetmaster to utilize the webrick server included in
the application. This server is single-threaded, very slow and tends
to fall over when you get close to 30 nodes. You will start to see
connection-reset or End-of-file errors when this happens.

You will want to a server that can scale better than webrick, such as
Passenger (aka. mod_rails), or mongrel, both with a front-end
web-proxy such as apache.

If you would like to run Passenger (aka. mod_rails) with apache install the
puppetmaster-passenger package. It will automatically setup an apache2 virtual
host that will run puppetmaster under Passenger.

For more information:
http://projects.reductivelabs.com/projects/puppet/wiki/Using_Passenger