Zeppelin Configs

The files in the repository are the configs used by Zeppelin in both our testing guild as well as The Coding Den itself.

Updating these files won't update the configuration of the bot. These are merely here to allow for collaborative editing and history keeping for the configuration.

A custom config assembler has also been built to allow us to split the configuration into multiple files, instead of one huge monolithic block of YAML.

For more information regarding specific settings, please refer to the Zeppelin documentation.

Structure

The configuration is structured as follows:

• /config: Configuration container directory.
  • globals.yml: Global variable declarations that are persistent across environments.
  • /[environment name]: The configuration container for a given environment (currently main and test, after our guilds).
    • core.yml: Top-level configuration excluding the plugins section, like prefix and levels.
    • constants.yml: Environment-specific variable definitions. Variable definitions in this file that overlap with globals.yml will take precedence.
    • /plugins: Plugin configurations.
      • [plugin name].yml: Configuration for this specific plugin.

Compiling production configuration

To compile the production configuration (after having installed dependencies), run npm run build.

To print verbose logging information like detailed stack traces, supply the -v option.

(Note: If running via NPM, you will need to supply additional options as -- -v.)

Compiled configuration will be outputted into the out directory with files named as [environment name].yml.