5 # first we have a set of globals
6 # That apply to all virtual servers
9 # This is the directory where all logfiles for
10 # all virtual servers will be written
12 logdir = /usr/local/var/log/yaws
14 # This the path to a directory where additional
15 # beam code can be placed. The daemon will add this
16 # directory to its search path
18 ebin_dir = /usr/local/lib/yaws/examples/ebin
21 # This is a directory where application specific .hrl
22 # files can be placed. application specifig .yaws code can
23 # then include these .hrl files
25 include_dir = /usr/local/lib/yaws/examples/include
31 # This is a debug variable, possible values are http | traffic | false
32 # It is also possible to set the trace (possibly to the tty) while
33 # invoking yaws from the shell as in
34 # yaws -i -T -x (see man yaws)
42 # it is possible to have yaws start additional
43 # application specific code at startup
48 # By default yaws will copy the erlang error_log and
49 # end write it to a wrap log called report.log (in the logdir)
50 # this feature can be turned off. This would typically
51 # be the case when yaws runs within another larger app
58 log_wrap_size = 1000000
61 # Possibly resolve all hostnames in logfiles so webalizer
62 # can produce the nice geography piechart
64 log_resolve_hostname = false
68 # fail completely or not if yaws fails
69 # to bind a listen socket
70 fail_on_bind_err = true
74 # If yaws is started as root, it can, once it has opened
75 # all relevant sockets for listening, change the uid to a
76 # user with lower accessrights than root
81 # If HTTP auth is used, it is possible to have a specific
87 # When we're running multiple yaws systems on the same
88 # host, we need to give each yaws system an individual
89 # name. Yaws will write a number of runtime files under
91 # The default value is "default"
97 # earlier versions of Yaws picked the first virtual host
98 # in a list of hosts with the same IP/PORT when the Host:
99 # header doesn't match any name on any Host
100 # This is often nice in testing environments but not
101 # acceptable in real live hosting scenarios
103 pick_first_virthost_on_nomatch = true
106 # All unices are broken since it's not possible to bind to
107 # a privileged port (< 1024) unless uid==0
108 # There is a contrib in jungerl which makes it possible by means
109 # of an external setuid root programm called fdsrv to listen to
110 # to privileged port.
111 # If we use this feature, it requires fdsrv to be properly installed.
112 # Doesn't yet work with SSL.
119 # end then a set of virtual servers
120 # First two virthosted servers on the same IP (0.0.0.0)
121 # in this case, but an explicit IP can be given as well
123 #<server sean.desk.hq.powerset.com>
126 # docroot = /usr/local/var/yaws/www
133 # dir_listings = true
146 docroot = /Users/tom/dev/git/fuzed/helloworld/public
147 appmods = <pathelem, myappmod>
148 errormod_404 = myappmod
154 docroot = /Users/tom/dev/git/fuzed/helloworld/public
155 errormod_404 = test_rails_handler
158 # And then an ssl server
160 #<server sean.desk.hq.powerset.com>
164 # dir_listings = true
166 # keyfile = /usr/local/etc/yaws-key.pem
167 # certfile = /usr/local/etc/yaws-cert.pem