Difference between revisions of "Dev/Warrior"

From Archiveteam
< 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

  1. Start the virtual machine
  2. Linux boots
  3. The user warrior is automatically logged in.
  4. /etc/inittab kicks off /home/warrior/warrior-code2/boot.sh.
    1. This will git pull https://github.com/ArchiveTeam/warrior-code2 into /home/warrior/warrior-code2/.
    2. /home/warrior/warrior-code2/warrior-runner.sh sets up a process which monitors /dev/shm/ready-for-warrior and launches run-warrior when the state changes.
  5. boot.sh launches /home/warrior/warrior-code/boot-part-2.sh
  6. boot-part-2.sh is a short script that does the following:
    1. ./warrior-install.sh
      1. install/update seesaw, check branch, version
      2. install framebuffer support, DNS caching
      3. sets up /data
    2. sudo ./make-data-disk.sh
      1. cleans up
      2. creates and prepares the partition
      3. mkdir -p /home/warrior/projects
    3. touch /dev/shm/ready-for-warrior
      1. triggers the launch of /usr/local/bin/run-warrior which launches /home/warrior/warrior-code2/src/seesaw/run-warrior
      2. contacts warriorhq.archiveteam.org and requests the projects.json file. This file contains the projects you see in the Available Projects page.
    4. ./say-hello.sh
      1. setup vmware port forwarding
      2. show splash screen
  7. 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.

  1. Start the warrior.
  2. Press Alt+F3 and log in as root , password archiveteam
  3. cd /home/warrior/warrior-code2
  4. sudo -u warrior git checkout development
  5. reboot

By the same route you can return your warrior to the master branch.


Developer Documentation