| Aug | SEP | Oct |
| 28 | ||
| 2019 | 2020 | 2021 |
COLLECTED BY
Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Collection: Archive Team: The Github Hitrub
docker pull docker.io/python/docker-bpo
(一)Clone roundup and switch to the bugs.python.org branch:
hg clone https://bitbucket.org/python/roundup
cd roundup
hg update bugs.python.org
(一)Clone the python-dev instance alongside with roundup:
hg clone https://bitbucket.org/python/tracker-cpython python-dev
(一)Setup configuration:
cd python-dev
mkdir db
cp config.ini.template config.ini
cp detectors/config.ini.template detectors/config.ini
(一)To run the b.p.o container, cdin the dir where you cloned both
roundup and python-dev and run:
docker run --rm -it -p 9999:9999 -v `pwd`:/opt/tracker docker.io/python/docker-bpo
This will launch the container in interactive mode, and mount the dir
with the clones to the container's /opt/tracker.
(一)Every time the container is run, the tracker is initialized and 3
users are created. You can then run the tracker with:
rd-start
(一)Your local instance of bugs.python.org should be available at
http://localhost:9999
On top of the two default users (admin and anonymous),
3 additional users are also available:
●user: a regular user
●developer: a developer (triager) that signed the cla
●coordinator: a coordinator and committer that signed the cla
You can login as any of these 3 users using pass as password.
rd-start and ctrl+c.
●When you register a new user, look in python-dev/debugmail.txt:
you will find a confirmation URL. Copy it in your broswer and
replace all the escaped =3D with =.
●You can edit the code in roundup and python-dev from outside
the container, since those dir are shared.
●If you edit the code, you'll need to restart the tracker.
Changes to the templates (the html dir) do not require a restart.
●See https://wiki.python.org/moin/TrackerDevelopment for more info.
/opt/tracker directory it means that SELinux
is causing the problem, append :Z which will apply appropriate SELinux context:
docker run --rm -it -p 9999:9999 -v `pwd`:/opt/tracker:Z docker.io/python/docker-bpo
On some systems (Fedora, Red Hat, Centos) due to security constraints docker
requires sudo to be run, make sure to update above commands appropriately in
that case.