Endpoints <endpoints>
provide a basis for creating an interactive learning experience. However, there's no interactivity unless those Endpoints are made accessible somehow to the learner. Enter Presentations.name
- The name of the presentation. This can be whatever you want, as long as it's relatively short andport
- The port that Antidote should use to access the container for this Presentation.type
- This controls the type of presentation being offered. Currently supported options are ssh
and http
.presentations
attribute is plural form, and provided as a YAML list. This is because you can have multiple Presentations to the same Endpoint:linux1-cli1
, linux1-cli2
, and linux1-web
.presentations
field entirely, but note that in this caseadditionalPorts
becomes a required field, and must specify at least one port.restapi
didn't have any presentations, we needed to ensure at least one port was provided in additionalPorts
. The learner can then access the linux1
endpoint and use the tooling in that Endpoint to access the REST API of restapi
.type
field that you should be aware of.type: ssh
antidote
and antidotepassword
, Antidote will take care of connecting it to the user on the front-end.type: http
http
type can be used. A tab will be opened for this Presentation, but instead of a terminal, the tab contents will show the web application you provide in the Endpoint (in an iframe
). A few considerations for this option: