thank yous

• Olve Maudal, Mike Long, Johannes Brodwall, Emily Bache, and Seb Rose have been enthusiastic about cyber-dojo from the very early days. Big thanks also to Mike Sutton, Michel Grootjans, James Grenning, Byran Wills-Heath, Bob Allen.
• Olve, Mike, Johannes, Emily, Seb, Mike, Michel, James, Byran, Bob - I really appreciate all your help and encouragement.
• Jerry Weinberg showed me the power of experiential learning on all of his conferences and courses, notably Problem Solving Leaderhip (PSL) which strongly influenced the way I designed cyber-dojo. Thank you Jerry.

overview of how cyber-dojo uses git

This blog entry has been commented out.
cyber-dojo no longer uses git in its storer service or its runner service.

pulling the latest cyber-dojo github repo

This page is for an old version of cyber-dojo.
Start from here.

overview of how cyber-dojo's language docker-containers work

When you set up your cyber-dojo cyber-dojo will only offer entries whose languages/ subfolder's manifest.json file has an image_name entry that exists. For example, if cyber-dojo/languages/Java/JUnit/manifest.json contains this...

{ "image_name": "cyberdojofoundation/java_junit" "display_name": "Java, JUnit", ... }

then [Java, JUnit] will only be offered if the docker image cyberdojofoundation/java_junit exists on the server, as determined by running

$ docker images

cyber-dojo will start a container from the docker image_name to execute an animals cyber-dojo.sh file each time the animal presses the [test] button.

cyber-dojo language's manifest.json entries explained

This page is for an old version of cyber-dojo.
This is the page you're looking for.

setting up your own self-hosted cyber-dojo server

• On Linux
• On a Mac
• On Windows

adding a new language and unit-test-framework to cyber-dojo

This page is for an old version of cyber-dojo.
This is the page you're looking for.