Servers configuration files

Erlang Web framework can be run on top of both Inets and Yaws web servers. The configuration files for both servers are copied from the eptic/priv/ directory to config/ in the root folder of the project.

Inets

Inets configuration files are by default config/inets.conf and config/inets_https.conf: the configuration details can be found on the official documentation pages: http://www.erlang.org/doc/man/httpd.html. The only difference is the node running mode. In case of running the node in the standard mode (single_node - without cache) there should be e_mod_inets callback module placed in the Modules section. Otherwise (in the frontend and single_node_with_cache mode - in backend mode the web server does not start) - instead of e_mod_inets - e_fe_mod_inets should be put.

Yaws

Yaws configuration is stored inside the config/yaws.conf file: the detailed documentation can be found on http://yaws.hyber.org/yman.yaws?page=yaws.conf. Like in the Inets, when node is running in the mode without cache support, arg_rewrite_mod should be set to e_mod_yaws and appmods to <app, e_mod_yaws>. Otherwise (single_node_with_cache and frontend mode) - they should be set to e_fe_mod_yaws.

EWGI

While running with EWGI-compliant mode, special config files are beeing used. In fact the files created have the ewgi_ prefix. So config file for inets would then be: config/ewgi_inets.conf and config/ewgi_inets_https.conf. Running on Mochiweb (only in interactive mode) doesn't require any config files to be created, as parameters to the Mochiweb server are applied directly from the bin/start_interactive script, and it is the place where you should put any changes (for instance regarding port number, etc.).