To customize clowder you can put all configuration changes in a folder called custom inside the clowder folder. If you are working on the source code this folder is excluded from git so you can use that also to customize your development environment, and not accidentally commit changes to either play.plugins or application.conf. If you make any changes to the files in the custom folder you will need to restart the application (both in production and development).
The play.plugins file is used to enable plugins. You can only enable plugins, you can not disable plugins. This is one of the reasons why we minimize the number plugins that are enabled by default. For example most instances at NCSA will have the following plugins enabled.
The custom.conf file is used to override any of the changes in the application.conf or any included conf files (such as securesocial.conf). One change every instance of clowder should do is to modify the commKey and application.secret. Common changes we do is to modify clowder to use a directory on disk to store all blobs instead of storing them in mongo. Following is an example that we use for some of the instances we have at NCSA.
This allows to translate or customize certain aspects of clowder. All messages in clowder are in english and are as messages.default. Unfortunatly it is not possible to use messages.default to use for translations since it falls back to those embedded in the clowder jar files. To update the messages in english, you can use messages.en. The default is for clowder to only know about english, this can be changed in your custom.conf with
The public folder is place where you can place customizations for previews, as well as new stylesheets. To add a new stylesheet you should place it in the
public/stylesheets/themes/ folder. The name should be <something>.min.css or <something>.css. The user will at this point see in their customization settings the option to select <something> as their new theme to be used.
To add new previews you can put them in the