Difference between revisions of "ArchiveTeam Warrior"

From Archiveteam
Jump to: navigation, search
(Projects)
m (I need to disconnect my internet / reboot my PC but I don't want to loose work)
Line 46: Line 46:
  
  
=== I need to disconnect my internet / reboot my PC but I don't want to loose work ===
+
=== I need to disconnect my internet / reboot my PC but I don't want to lose work ===
  
 
If you pause/suspend the warrior instance, most projects will allow resuming of work in progress when you unsuspend the warrior instance.
 
If you pause/suspend the warrior instance, most projects will allow resuming of work in progress when you unsuspend the warrior instance.
 
  
 
=== I told the warrior to shutdown from the interface but nothing has changed! what gives? ===
 
=== I told the warrior to shutdown from the interface but nothing has changed! what gives? ===

Revision as of 09:12, 16 May 2013

Archive team.png
Warrior-vm-screenshot.png
Warrior-web-screenshot.png

The ArchiveTeam Warrior is a virtual archiving appliance. You can run it to help with the ArchiveTeam archiving efforts. It will download sites and upload them to our archive — and it’s really easy to do!

The warrior is a virtual machine, so there is no risk to your computer. The warrior will only use your bandwidth and some of your disk space. It will get tasks from and report progress to the Tracker.

The warrior runs on Windows, OS X and Linux. You’ll need VirtualBox (recommended), VMware or a similar program to run the virtual machine.

Instructions for VirtualBox:

  1. Download the appliance (174MB).
  2. In VirtualBox, click File > Import Appliance and open the file.
  3. Start the virtual machine. It will fetch the latest updates and will eventually tell you to start your web browser.

Once you’ve started your warrior:

  1. Go to http://localhost:8001/ and check the Settings page.
  2. Choose a username — we’ll show your progress on the leaderboard.
  3. Go to the All projects tab and pick a project to work on. Even better: select ArchiveTeam’s Choice to let your warrior work on the most urgent project.





Warrior FAQ

Help! The warrior is eating all my bandwidth!

You can limit the warriors bandwidth quite easily for virtualbox as long as you are running a relatively recent version.

VBoxManage bandwidthctl archiveteam-warrior-2 --name Limit --add network --limit 3

will limit the warrior instance called archiveteam-warrior-2 (The default name of the warrior vm currently) to 3Mb/s. Adjust as needed.

In the latest version of VirtualBox on Windows, the syntax appears to have changed. The correct command now seems to be:

VBoxManage bandwidthctl archiveteam-warrior-2 add netlimit --type network --limit 3

I turned my warrior off, will those tasks be lost?

If you've killed your warrior instances then the work your warrior did has been lost, however the tasks will be returned to the pool after a period of time. If you want you can alert the admins via IRC of whats happened, and they can clear the claims your username may of made however this isn't very important on most projects.


I need to disconnect my internet / reboot my PC but I don't want to lose work

If you pause/suspend the warrior instance, most projects will allow resuming of work in progress when you unsuspend the warrior instance.

I told the warrior to shutdown from the interface but nothing has changed! what gives?

The warrior will attempt to finish the current running tasks before shutting down. If you need to shut down right away; go ahead, your progress will be lost however the jobs will eventually cycle out to another user.

Projects

Previous and current warrior projects:

Project Status Began Finished Result Archive Location
MobileMe Archive Posted April 3, 2012 Aug 8, 2012 Success

archive index user lookup

Fortune City Archive Posted April 4, 2012 April 11, 2012 Partial Success archive user lookup
Tabblo Archive Posted May 23, 2012 May 26, 2012 Success archive user lookup
PicPlz Archive Posted June 3, 2012 June 15, 2012 archive index user lookup
Tumblr (test project) Archive Posted August 9, 2012 August 19, 2012 archive (tar) archive (warc)
Cinch.FM Archive Posted August 20, 2012 August 22, 2012 Success archive
City Of Heroes Archive Posted September 3, 2012 December 1, 2012 Success www forums 1 2 3 4 5
Webshots Archive Posted October 4, 2012 November 18, 2012 index
BT Internet Archive Posted October 10, 2012 November 2, 2012 Success archive
Daily Booth Archive Posted November 19, 2012 December 29, 2012 archive lookup
Github Archive Posted December 13, 2012 December 17, 2012 Success archive index
Yahoo Blogs (Vietnamese) Archive Posted January 8, 2013 January 19, 2013 archive
weblog.nl Archive Posted January 19, 2013 February 2, 2013 archive lookup
URLTeam Active latest
Punchfork Archive Posted January 11, 2013 March 6, 2013 archive user lookup
Xanga Downloads Paused January 22, 2013 February 16, 2013 archive user lookup user list
Posterous Active February 23, 2013 archive
Storylane Downloads Finished March 8, 2013 March 15, 2013
Yahoo! Messages Downloads Finished March 20, 2013 March 31, 2013 archive
Formspring Active March 24, 2013 archive
Yahoo Upcoming Archive Posted April 20, 2013 April 25, 2013 archive
Streetfiles.org Downloads Finished April 28, 2013 April 30, 2013 Partial archive

Status

In Development 
a future project
Active 
start up a Warrior and join the fun; this one is in progress right now
Downloads Finished 
we've finished downloading the data
Archived 
the collected data has been properly archived
Archive Posted 
the archive is available for download

Result

Success 
downloaded all of the data and posted the archive publicly
Qualified Success 
either we couldn't get all of the data, or the archive can't be made public
Failure 
the site closed before we could download anything

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 production branch to the master branch.

  1. Start the warrior.
  2. Press Alt+F2 and log in with username root and password archiveteam.
  3. cd /home/warrior/warrior-code
  4. sudo -u warrior git checkout master
  5. reboot

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