NRE Labs
  • Welcome!
  • Creating and Contributing
    • First Steps
    • Open a Pull Request
    • Preview Your Changes
    • Review and Merge
  • Other Resources
    • Curriculum Quality Standards
    • Curriculum Release Process
    • NRE Labs Endpoint Images
    • Git Tips
    • Jupyter Notebooks
    • Tips and FAQs
  • Antidote
    • Architecture
      • Antidote Services
      • Lesson Directory Mapping
      • Lesson Networking
    • The Antidote CLI
      • Create Curriculum Resources
      • Validating an Existing Curriculum
    • Object Reference
      • Images
      • Lessons
        • Authors
        • Stages
        • Endpoints
        • Presentations
        • Connections
        • Endpoint Configuration
      • Collections
    • Development
      • Antidote Release Process
  • Misc
    • Tools for Presenters
    • Help! I'm Not A Developer!
    • (Legacy) Local Preview
Powered by GitBook
On this page

Was this helpful?

  1. Antidote
  2. Architecture

Antidote Services

The Antidote platform is composed of two services:

  • antidote-web

  • antidoted

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.

Configuring Antidote

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)

PreviousArchitectureNextLesson Directory Mapping

Last updated 5 years ago

Was this helpful?