The Antidote platform is composed of two services:
Antidote-Core is where the real work gets done in the Antidote project. It's responsible for taking in lesson definitions via a YAML file and any configs, scripts, etc used in the lesson, and providing them to the front-end via its API.
Antidote is configured through a YAML file. Since typically Antidote is deployed within Kubernetes, the ideal way to do this is through a ConfigMap.
If you're using antidote-selfmedicate to spin up an instance of Antidote yourself, a configuration file is provided for you.
(should have a sample config file in the antidote-core repo, and just link to it here)