From: Torbjorn T. <et...@us...> - 2005-07-26 18:45:13
|
Update of /cvsroot/jungerl/jungerl/lib/js/priv In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4980/js/priv Added Files: yaws.conf Log Message: Adding an Erlang Javascript support library. --- NEW FILE: yaws.conf --- # conf for yaws # first we have a set of globals # That apply to all virtual servers # This is the directory where all logfiles for # all virtual servers will be written logdir = /home/tobbe/js/log # This the path to a directory where additional # beam code can be placed. The daemon will add this # directory to its search path ebin_dir = /home/tobbe/js/ebin # This is a directory where application specific .hrl # files can be placed. application specifig .yaws code can # then include these .hrl files include_dir = /usr/local/lib/yaws/examples/include # This is a debug variable, possible values are http | traffic | false # It is also possible to set the trace (possibly to the tty) while # invoking yaws from the shell as in # yaws -i -T -x (see man yaws) trace = false # it is possible to have yaws start additional # application specific code at startup # # runmod = mymodule # By default yaws will copy the erlang error_log and # end write it to a wrap log called report.log (in the logdir) # this feature can be turned off. This would typically # be the case when yaws runs within another larger app copy_error_log = true # Logs are wrap logs log_wrap_size = 1000000 # Possibly resolve all hostnames in logfiles so webalizer # can produce the nice geography piechart log_resolve_hostname = false # fail completely or not if yaws fails # to bind a listen socket fail_on_bind_err = true # If yaws is started as root, it can, once it has opened # all relevant sockets for listening, change the uid to a # user with lower accessrights than root username = tobbe # If HTTP auth is used, it is possible to have a specific # auth log. auth_log = true # When we're running multiple yaws systems on the same # host, we need to give each yaws system an individual # name. Yaws will write a number of runtime files under # /tmp/yaws/${id} # The default value is "default" id = js # end then a set of virtual servers # First two virthosted servers on the same IP (0.0.0.0) # in this case, but an explicit IP can be given as well #<server struts> # port = 80 # listen = 0.0.0.0 # docroot = /home/tobbe/www #</server> <server localhost> port = 4080 listen = 0.0.0.0 dir_listings = true docroot = /home/tobbe/js/priv/docroot </server> # And then an ssl server #<server struts> # port = 443 # docroot = /tmp # listen = 0.0.0.0 # dir_listings = true # <ssl> # keyfile = /etc/yaws-key.pem # certfile = /etc/yaws-cert.pem # </ssl> #</server> |