Commands for testing solution
active
$ checkio-cli active
Mission: empire2
Interpreter: python_3
is showing currently active status. In this examples user is solving mission empire2 using python_3 interpreter
$ checkio-cli active crystal-row
$ checkio-cli active
Mission: crystal-row
Interpreter: python_3
is changing active mission. Active mission will be change when you are usign mission slug in any other way, like checkio-cli check crystal-row
$ checkio-cli active crystal-row python_2
$ checkio-cli active
Mission: crystal-row
Interpreter: python_2
is changing both, mission and envieroument
get-git
download a new mission from git repository
$ checkio-cli get-git https://github.com/Checkio-Game-Missions/checkio-empire-striped-words striped-words
- checkout a mission into your missions_folder . If folder for this mission is exist already user will be asked about remove this folder first
- collect all sources in one folder from all parents
- build a docker image if parameter --wihtout-container wasn't added
- add a solution file for current interpreter in solutions_folder
- Build a native envieroument for refery and checkio_cli interface
- set this mission as a currently active
run and check
both commands run and check have the same interface
$ checkio-cli check striped-words
TEST: striped_words(My name is ...)
INCOMPLETE
checks mission striped-words using a solution from folder solutions_folder
$ checkio-cli check
TEST: striped_words(My name is ...)
INCOMPLETE
checks a currently active mission.
$ checkio-cli check --without-container
TEST: striped_words(My name is ...)
INCOMPLETE
check by using local envieroument for referee not a docker container. For simple mission it works faster and for mission creation process it is an easier way to debug a referee
Commands for creation mission
create-mission
$ checkio-cli create-mission summi
Congratulation!!!
You have new mission created with slug summi
create a simple mission from template "simpleio" and do all the steps than git-get is doing in order to preate a mission for checking on your local computer
$ checkio-cli create-mission summi --without-container
creates mission without container
$ checkio-cli create-mission summi --template=newone
Template "newone"" wasn't found in folder(s) "/media/sf_host/www/checkio/mission-design/checkio-cli/checkio_cli/templates"
creates a mission by using not a default template "simpleio" but "newone".
Addition folders for searching a mission template can be added in checkio_cli.yaml templates
$ checkio-cli create-mission summi git@github.com:oduvan/checkio-summi.git
creates a mission and push it on git repository
git-link-mission
a git repository can be added after creating mission
$ checkio-cli create-mission summi --without-container
$ checkio-cli git-link-mission summi git@github.com:oduvan/checkio-summi.git
compile-mission
if new files was added during process of creation of new mission recompilation should be done
$ checkio-cli compile-mission summi
it also rebuild a netive envieroument
build-native-env
if requirements for docker or for checkio_cli interface was changed and native envieroument is using it should be rebuild
$ checkio-cli build-native-env summi
build-mission
if docker is testing insted of native env and requirements for referee or requirements for any executer were changed rebuildig docker image should be done
OR if you get a mission without docker and decided to start use it now
$ checkio-cli build-mission summi
init
creates a file with an initial code
$ checkio-cli init summi
creates a file in solutions_foilder
$ checkio-cli init sumi /tmp/summi.py
creates a file with initial code not in solutions_foilder folder but in passed path
after creation such a file it can be runned by
$ /tmp/summi.py
and tested by
$ /tmp/summi.py --check
$ /tmp/summi.py --check --without-container
Config
$ cat ~/.checkio_cli.yaml
main_folder: /home/oduvan/checkio
missions_folder: /home/oduvan/www/checkio/mission-design/missions
solutions_folder: /home/oduvan/www/checkio/mission-design/solutions
main_folder - basic folder for all missions, compiled missions, prepared envierouments missions_folder - where missions sources is stored solutions_folder - where users solutions is stored
$ cat ~/.active_checkio_cli.yaml
interpreter: python_3
mission: null
user can get the same information by command active and can change this file using the same command.