Difference between revisions of "Dev/Warrior"
< Dev
Jump to navigation
Jump to search
(Created page with "The warrior image is built off Debian 6.0.5 (squeeze). Here are the basics: * kernel 2.6.32-5-686 (released 2009-03-12) * Python 2.6.6, pip 1.1 * Perl v5.10.1, cpan 1.9402 (s...") |
m (add devnav) |
||
Line 49: | Line 49: | ||
By the same route you can return your warrior to the <code>master</code> branch. | By the same route you can return your warrior to the <code>master</code> branch. | ||
{{devnav}} |
Revision as of 03:56, 3 December 2013
The warrior image is built off Debian 6.0.5 (squeeze). Here are the basics:
- kernel 2.6.32-5-686 (released 2009-03-12)
- Python 2.6.6, pip 1.1
- Perl v5.10.1, cpan 1.9402 (still needs config)
- gcc 4.4.5, make 3.81, bash 4.1.5
- nano 2.2.4 with color syntax highlighting
- curl 7.21.0
Bootup
- Start the virtual machine
- Linux boots
- The user
warrior
is automatically logged in. /etc/inittab
kicks off/home/warrior/warrior-code2/boot.sh
.- This will
git pull https://github.com/ArchiveTeam/warrior-code2
into/home/warrior/warrior-code2/
. /home/warrior/warrior-code2/warrior-runner.sh
sets up a process which monitors/dev/shm/ready-for-warrior
and launchesrun-warrior
when the state changes.
- This will
boot.sh
launches/home/warrior/warrior-code/boot-part-2.sh
boot-part-2.sh
is a short script that does the following:./warrior-install.sh
- install/update seesaw, check branch, version
- install framebuffer support, DNS caching
- sets up
/data
sudo ./make-data-disk.sh
- cleans up
- creates and prepares the partition
mkdir -p /home/warrior/projects
touch /dev/shm/ready-for-warrior
- triggers the launch of
/usr/local/bin/run-warrior
which launches/home/warrior/warrior-code2/src/seesaw/run-warrior
- contacts warriorhq.archiveteam.org and requests the
projects.json
file. This file contains the projects you see in the Available Projects page.
- triggers the launch of
./say-hello.sh
- setup vmware port forwarding
- show splash screen
- Point your web browser to http://localhost:8001 and go.
The code for each project is stored in /home/warrior/projects/<PROJECTNAME>/
Testing pre-production code
(Don't do this unless you really need or want to.) If you are developing a warrior script, you can test it by switching your warrior from the master
branch to the development
branch or create another branch. The warrior will fetch the corresponding seesaw repo branch.
- Start the warrior.
- Press Alt+F3 and log in as
root
, passwordarchiveteam
cd /home/warrior/warrior-code2
sudo -u warrior git checkout development
reboot
By the same route you can return your warrior to the master
branch.