Wok is loading the root configuration for every plugin, so there is no need to keep it in kimchi.conf file. Also the Kimchi configuration file should only contain data that can be edited by user, which is not the case of the cherrypy configuration. Signed-off-by: Aline Manera <alinefm@linux.vnet.ibm.com> --- kimchi.conf | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/kimchi.conf b/kimchi.conf index 9e0f20d..c451703 100644 --- a/kimchi.conf +++ b/kimchi.conf @@ -15,16 +15,3 @@ SERIAL_CONSOLE_TIMEOUT = 120 # Automatically create ISO pool on server start up create_iso_pool = True - -[/] -tools.trailing_slash.on = False -request.methods_with_bodies = ('POST', 'PUT') -tools.nocache.on = True -tools.proxy.on = True -tools.sessions.on = True -tools.sessions.name = 'wok' -tools.sessions.secure = True -tools.sessions.httponly = True -tools.sessions.locking = 'explicit' -tools.sessions.storage_type = 'ram' -tools.sessions.timeout = 10 -- 2.5.5