Providers

rCTF uses a pluggable provider system, so you can swap implementations for major platform features. Each provider is configured with a name and an options object in your configuration.

Provider format#

All providers follow the same configuration pattern:

providerField:
  name: provider-type/provider-name
  options:
    key: value

The name identifies which implementation to load, and options is passed directly to the provider’s constructor. Most providers also support environment variable fallbacks for their options.

Available providers#

Providers marked as “None (disabled)” are optional features. The platform functions without them, but the associated features will be unavailable.

* Unlike the other providers, message providers are not selected by a top-level config field. They are nested inside each blood bot destination entry, so the same deployment can post to multiple destinations using different providers.