##The plugin-controller is for specific dotCMS plugin configuration.  Usually this file is intended for 
##dotCMS plugin developers to do things like add custom hooks or control the cms filter. All the 
##possible properties are listed in the hello.world sample.
##Typically plugin specific configuration is done in the plugin.properties. 
##This is where a plugin specifies its own properties

##This is for sevlets. A plugin can add exclusions so that the filter will not fire on them and redirect away
cmsfilter.servlet.exclusions=

contentletapi.prehooks=com.dotmarketing.plugins.hello.world.HelloWorldContentletPreHook

contentletapi.posthooks= 

###Use this property to make your plugin deploy to WEB-INF/lib.  By default it deploys to common/lib/ext  
###which is the common loader but in in front of /common/lib which is where most dotCMS code lives.  
deploy_to_app_classloader=false

###Use this property to make your plugin deploy to /plugin/plugins_id/ backend folder your plugin/dotcms/<files> , in the especified host.  By default it created  
###on the default host. If is set, you could specified one or more host using comma separeted hostname.
##hosts.name=test4.dotcms.org,test2.dotcms.org