Difference between revisions of "Dev/Warrior"
m (→Bootup: docker runs the runner) |
m (→Logging into the Warrior: typo) |
||
Line 33: | Line 33: | ||
# You are now logged in as root. | # You are now logged in as root. | ||
# Check the docker container with <code>docker ps</code>. This will give you docker container identifier, among others. | # Check the docker container with <code>docker ps</code>. This will give you docker container identifier, among others. | ||
# Enter the inside of the docker container with <code>docker exec -it ''identifier'' /bin/ | # Enter the inside of the docker container with <code>docker exec -it ''identifier'' /bin/bash</code> | ||
== Testing Core Warrior Code == | == Testing Core Warrior Code == | ||
Revision as of 20:52, 30 June 2018
The Warrior is a virtual machine appliance used by volunteers to participate in projects.
Packages
The Warrior image is built off Alpine Linux 3.6.2:
- kernel 4.9.32
- the virtual machine image is prepared using the
stage.sh
script and contains a pre-installed/root/boot.sh
script that downloads and boots the warrior.
The warrior itself runs in a docker container running Ubuntu 16.04 that contains
- Python 3.5.2, pip 8.1.1
- Perl v5.22.1
- gcc 5.4.0, make 4.1, bash 4.3.48
- curl 7.47.0
Bootup
The virtual machine is self-updating. It does the following:
- Start the virtual machine
- Linux boots
boot.sh
downloads and launches/root/startup.sh
startup.sh
prepares and runs a docker container with the warrior runner- Point your web browser to http://localhost:8001 and go.
Logging into the Warrior
To log into the warrior,
- Press Alt+F3 (or press Alt+Right).
- The username is
root
and the password isarchiveteam
- You are now logged in as root.
- Check the docker container with
docker ps
. This will give you docker container identifier, among others. - Enter the inside of the docker container with
docker exec -it identifier /bin/bash
Testing Core Warrior Code
Since the Warrior pulls from GitHub, it is important to commit only stable changes into the master
branch. Recommended Git branching practices use a development branch.
To test core Warrior code, you can switch from the master
branch to the development
branch. The Warrior will fetch the corresponding seesaw-kit repository branch.
To change branches,
- Log in as root
- Execute
cd /home/warrior/warrior-code2
- Execute
sudo -u warrior git checkout development
- Execute
reboot
By the same route you can return your warrior to the master
branch.
The code for each project is stored in /home/warrior/projects/<PROJECTNAME>/