AWE config file manual

This doc explains the meaning and default values of the fields in awe config files (server and client).

Sample server cfg template:

https://github.com/MG-RAST/AWE/blob/master/templates/awes.cfg.template

Sample client cfg template:

https://github.com/MG-RAST/AWE/blob/master/templates/awec.cfg.template

Section	Field	Meaning	Default (or e.g.)
[Directories]	site	the path to the website	e.g. $GOPATH/src/github.com/MG-RAST/AWE/site
[Directories]	data	a file path for store some system related data (job script, cached data, etc)	e.g. /mnt/data/awe/data
[Directories]	logs	a path for storing logs	e.g. /mnt/data/awe/logs
[server]	perf_log_workunit	collecting performance log per workunit	true
[server]	max_work_failure	workunit failure threshold to suspend a job	3
[server]	max_client_failure	consecutive client failure threshold to suspend a client	5
[client]	workpath	the root dir for workunit working dirs	e.g. /mnt/data/awe/work (need a certain mount of disk space to hold input/output data
[client]	supported_apps	supported application list	“”
[client]	app_path	the file path of supported app	can be overwritten by “supported_apps”
[client]	clientgroup	group name	“”
[client]	serverurl	awe-server api url	“” (mandatory)
[client]	print_app_msg	collect stdout/stderr for apps	true
[client]	auto_clean_dir	delete workunit directory to save space after completion	true
[client]	worker_overlap	overlap client side computation and data movement	false