Introduction
When connecting to the AWS training environment via SSH, students will be interacting with a Bash shell. If you are not familiar, the shell is a dollar-sign prompt you can type commands at (e.g. [student@ip ~]$) . The only commands you really need to know for the Grouper Training Environment (GTE) are listed below. Before you can go to your Grouper instance for a course, you need to "run the course" (below).
| Purpose | Command | Description | Example |
|---|---|---|---|
| List courses | ./gte | List all available courses to run. For most courses, 2 docker images exist-- A starting image named COURSE.1, and an image that is in the expected end state called COURSE.end. E.g. "201.1.1" and "201.1.end". Normally, you are not expected to start and stop containers between exercises. | [student@ip ~]$ ./gte 101.1.1 etc |
| Run a course | ./gte <course> | This will stop all GTE docker containers running, and will start the one specified. It will also stop/start the rabbitmq messaging container. Only one course can run at a time due to network port requirements. | [student@ip ~]$ ./gte 101.1.1 |
| See what is running | docker ps | If a course is running, or other docker containers, this will display | [student@ip ~]$ docker ps |
| Shell into running container | ./gte-shell | A container is a virtual operating system that you can go into and investigate, look around, troubleshoot. Note, this will not work if you are not running a container. Start a container before shelling in. Note, containers are ephemeral, if you change the contents in a container they will be lost when the container stops. | [student@ip ~]$ ./gte-shell |
| GSH into a container | ./gte-gsh | GSH or Grouper Shell is a command line Java interface into Grouper. It is useful to run commands or to script multiple commands. It is only available for Grouper admins. Note, this will not work if you are not running a container. Start a container before GSH'ing in. | [student@ip ~]$ ./gte-gsh |
| View logs of a running container | ./gte-logs | Note, this will not work if you are not running a container. Start a container before viewing logs. Once a container is stopped in the GTE the logs are gone. | [student@ip ~]$ ./gte-logs |