Oct
NOV
Dec
01
2019
2020
2021
About this capture
Organization:
Archive Team 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.
T h e W a y b a c k M a c h i n e - h t t p : / / w e b . a r c h i v e . o r g / w e b / 2 0 2 0 1 1 0 1 0 0 1 8 4 2 / h t t p s : / / g i t h u b . c o m / e n t e r p r i s e
S k i p t o c o n t e n t
S i g n up
●
F e a t u r e s → ● C o d e r e v i e w ● P r o j e c t m a n a g e m e n t ● I n t e g r a t i o n s ● A c t i o n s ● P a c k a g e s ● S e c u r i t y ● T e a m m a n a g e m e n t ● H o s t i n g ● M o b i l e
● C u s t o m e r s t o r i e s → ● S e c u r i t y →
●
●
●
● E x p l o r e G i t H u b →
L e a r n & c o n t r i b u t e ● T o p i c s ● C o l l e c t i o n s ● T r e n d i n g ● L e a r n i n g L a b ● O p e n s o u r c e g u i d e s
C o n n e c t w i t h o t h e r s ● E v e n t s ● C o m m u n i t y f o r u m ● G i t H u b E d u c a t i o n ● G i t H u b S t a r s p r o g r a m
●
●
P l a n s → ● C o m p a r e p l a n s ● C o n t a c t S a l e s
● N o n p r o f i t → ● E d u c a t i o n →
Search
All GitHub
↵
Jump to
↵
No suggested jump to results
{ { m e s s a g e } }
G i t H u b f o r e n t e r p r i s e s B u i l d l i k e t h e b e s t I n c r e a s e d e v e l o p e r v e l o c i t y . S e c u r e e v e r y s t e p . A u t o m a t e e n t i r e w o r k f l o w s . R e d e f i n e c o l l a b o r a t i o n . T r u s t e d b y o v e r 5 0 m i l l i o n d e v e l o p e r s .
C o n t a c t S a l e s
S t a r t a f r e e t r i a l
E m p o w e r y o u r t e a m . T r a n s f o r m y o u r b u s i n e s s . D e v O p s i s j u s t t h e s t a r t . T o p o r g a n i z a t i o n s k n o w t h a t t r a n s f o r m a t i o n a l s o d e p e n d s o n t e c h n o l o g y , t a l e n t , c u l t u r e , a n d p r o c e s s . G i t H u b h e l p s e n t e r p r i s e s p u t t h e m a l l t o w o r k — i n o n e p l a c e .
Secure your supply chain
Keep open source components secure and compliant.
Secure your code
Find and fix code vulnerabilities as part of your workflows.
Secure your software lifecycle
Create and enforce security and compliance policies as code.
Accelerate delivery
Automate every step of your pipeline, including powerful, flexible CI/CD native to GitHub.
Using rake 12.3.3
Using Ascii85 1.0.3
Using RedCloth 4.3.2
Using multipart-post 2.1.1
Using faraday 0.17.3
Using acme-client 0.6.1
Using concurrent-ruby 1.0.5
Using i18n 1.7.0
Using minitest 5.13.0
Using thread_safe 0.3.5.c8158c9
Using tzinfo 1.2.6
Using zeitwerk 2.2.2
Using activesupport 6.0.2.2.5665d0867b
Using builder 3.2.3
Using erubi 1.8.0
Using mini_portile2 2.4.0
Using nokogiri 1.10.9
Using rails-dom-testing 2.0.3
Using crass 1.0.6
Using loofah 2.4.0
Using rails-html-sanitizer 1.1.0
Using actionview 6.0.2.2.5665d0867b
Using rack 2.1.2
Using rack-test 0.6.3
Using actionpack 6.0.2.2.5665d0867b
Using nio4r 2.3.1
Using websocket-extensions 0.1.3
Using websocket-driver 0.7.0
Using actioncable 6.0.2.2.5665d0867b
Using globalid 0.4.2
Using activejob 6.0.2.2.5665d0867b
Using activemodel 6.0.2.2.5665d0867b
Using activerecord 6.0.2.2.5665d0867b
Using mimemagic 0.3.3
Using marcel 0.3.3
Using activestorage 6.0.2.2.5665d0867b
Using mini_mime 1.0.2
Using mail 2.7.1
Using actionmailbox 6.0.2.2.5665d0867b
Using actionmailer 6.0.2.2.5665d0867b
Using actiontext 6.0.2.2.5665d0867b
Using active_record_has_many_split_through 0.1.0.g561c960
Using public_suffix 4.0.3
Using addressable 2.7.0
Using afm 0.2.2
Using google-protobuf 3.9.1 (x86_64-linux)
Using twirp 1.1.0
Using aleph-client 2.1.0.gdf2a805d
Using allocation_sampler 1.0.0
Using aqueduct-client 0.1.0.g2ab5e8c
Using arca 2.1.3
Using asciidoctor 2.0.7
Using ast 2.4.0
Using metaclass 0.0.4
Using mocha 1.1.0
Using resilient 0.4.0
Using authzd-client 0.9.2.rec861528
Using aws-eventstream 1.0.3
Using aws-partitions 1.284.0
Using aws-sigv4 1.1.1
Using jmespath 1.4.0
Using aws-sdk-core 3.91.1
Using aws-sdk-kms 1.30.0
Using aws-sdk-s3 1.61.1
Using badge-ruler 0.0.1
Using bcrypt 3.1.13
Using benchmark-ips 2.7.2
Using mochilo 1.3.5.g70afb07
Using bert 1.1.10.45.gf6727fc
Using bertrpc 1.3.1.pre.github9
Using html_tokenizer 0.0.7
Using parser 2.6.4.0
Using smart_properties 1.13.1
Using better_html 1.0.11
Using bindata 2.4.6
Using msgpack 1.3.0
Using bootsnap 1.4.4
Using braintree 2.95.0
Using browser 3.0.2
Using bundler 2.0.2
Using byebug 9.0.3
Using regexp_parser 1.7.0
Using xpath 3.2.0
Using capybara 3.31.0
Using cbor 0.5.9.6
Using charlock_holmes 0.7.6
Using method_source 0.9.2
Using thor 0.19.4
Using railties 6.0.2.2.5665d0867b
Using sprockets 3.7.2
Using sprockets-rails 3.2.1
Using rails 6.0.2.2.5665d0867b
Build on best practices
Use and adapt workflows built by industry leaders and the open source community.
Scale secure automation
Consistently apply and scale policies across your organization, with traceability from source to deploy.
error-pages
GET /
✓ should respond with page list
Accept: text/html
GET /403
✓ should respond with 403
GET /404
✓ should respond with 404
GET /500
✓ should respond with 500
Accept: application/json
GET /403
✓ should respond with 403
GET /404
✓ should respond with 404
GET /500
✓ should respond with 500
Accept: text/plain
GET /403
✓ should respond with 403
GET /404
✓ should respond with 404
GET /500
✓ should respond with 500
error
GET /
✓ should respond with 500
GET /next
✓ should respond with 500
GET /missing
✓ should respond with 404
markdown
GET /
✓ should respond with html
GET /fail
✓ should respond with an error
multi-router
GET /
✓ should respond with root handler
GET /api/v1/
✓ should respond with APIv1 root handler
GET /api/v1/users
✓ should respond with users from APIv1
GET /api/v2/
✓ should respond with APIv2 root handler
GET /api/v2/users
✓ should respond with users from APIv2
mvc
GET /
✓ should redirect to /users
GET /pet/0
✓ should get pet
GET /pet/0/edit
✓ should get pet edit page
PUT /pet/2
✓ should update the pet
GET /users
✓ should display a list of users (70ms)
GET /user/:id
when present
✓ should display the user
✓ should display the users pets
when not present
✓ should 404
GET /user/:id/edit
✓ should display the edit form
PUT /user/:id
✓ should 500 on error
✓ should update the user
POST /user/:id/pet
✓ should create a pet for user (19ms)
params
GET /
✓ should respond with instructions
GET /user/0
✓ should respond with a user
GET /user/9
✓ should fail to find user
GET /users/0-2
✓ should respond with three users
GET /users/foo-bar
✓ should fail integer parsing
resource
GET /
✓ should respond with instructions
GET /users
✓ should respond with all users
GET /users/1
✓ should respond with user 1
GET /users/9
✓ should respond with error
GET /users/1..3
✓ should respond with users 1 through 3
DELETE /users/1
✓ should delete user 1
DELETE /users/9
✓ should fail
GET /users/1..3.json
✓ should respond with users 2 and 3 as json
route-map
GET /users
✓ should respond with users
DELETE /users
✓ should delete users
GET /users/:id
✓ should get a user
GET /users/:id/pets
✓ should get a users pets
GET /users/:id/pets/:pid
✓ should get a users pet
route-separation
GET /
✓ should respond with index
GET /users
✓ should list users
GET /user/:id
✓ should get a user
✓ should 404 on missing user
GET /user/:id/view
✓ should get a user
✓ should 404 on missing user (13ms)
GET /user/:id/edit
✓ should get a user to edit
PUT /user/:id/edit
✓ should edit a user
POST /user/:id/edit?_method=PUT
✓ should edit a user
GET /posts
✓ should get a list of posts
vhost
example.com
GET /
✓ should say hello
GET /foo
✓ should say foo
foo.example.com
GET /
✓ should redirect to /foo
bar.example.com
GET /
✓ should redirect to /bar
web-service
GET /api/users
without an api key
✓ should respond with 400 bad request
with an invalid api key
✓ should respond with 401 unauthorized
with a valid api key
✓ should respond users json
GET /api/repos
without an api key
✓ should respond with 400 bad request
with an invalid api key
✓ should respond with 401 unauthorized
with a valid api key
✓ should respond repos json
GET /api/user/:name/repos
without an api key
✓ should respond with 400 bad request
with an invalid api key
✓ should respond with 401 unauthorized
with a valid api key
✓ should respond user repos json
✓ should 404 with unknown user
when requesting an invalid route
✓ should respond with 404 json
1123 passing (4s)
=============================================================================
Writing coverage object [/home/runner/build/expressjs/express/coverage/coverage.json]
Writing coverage reports at [/home/runner/build/expressjs/express/coverage]
=============================================================================
=============================== Coverage summary ===============================
Statements : 98.81% ( 1916/1939 ), 38 ignored
Branches : 94.58% ( 751/794 ), 22 ignored
Functions : 100% ( 267/267 )
Lines : 100% ( 1872/1872 )
================================================================================
The command "npm run test-ci" exited with 0.
$ npm run lint
> express@4.17.1 lint /home/runner/build/expressjs/express
> eslint .
The command "npm run lint" exited with 0.
store build cache
$ # Upload coverage to coveralls
Done. Your build exited with 0.
Build as one team
Work seamlessly across your organization on a platform designed for collaboration.
Transform your culture
Embrace innersource, iterate faster, and ship more frequently using best practices from open source teams.
Learn as you build
Get insight into how your team builds today with community-backed KPIs.
Get connected
Find the experts you need, then make them feel at home with the platform and processes they know and love.
Meet our community
Stay connected
Raise your profile as an open source leader—and help your team to work on the open source code they care about.
Check out GitHub Connect
Developer-led learning
Help your team level up their skills in the same place they code.
Explore Learning Lab
40%
Reduction in developer onboarding time *
639%
Return on investment over 3 years *
45 Minutes saved per developer, per day *
* Results based on a composite organization of 1,800 developers using GitHub over three years.
100M+
Private and public repositories
1000s
Open source communities
60%
Fortune 500 companies
GitHub Enterprise
Essential security, automation, and collaboration for your teams.
$21
Per user / per month
Free for public repositories
Free for public repositories
Start a free trial
New
GitHub One
The definitive platform for
Contact Sales
See all our plans and features
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session.
You signed out in another tab or window. Reload to refresh your session.
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Learn more .
Accept
Reject
We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products.
Cookie Preferences at the bottom of the page.
For more information, see our Privacy Statement .
Essential cookies
We use essential cookies to perform essential website functions, e.g. they're used to log you in.
Learn more
Always active
Analytics cookies
We use analytics cookies to understand how you use our websites so we can make them better, e.g. they're used to gather information about the pages you visit and how many clicks you need to accomplish a task.
Learn more
Save preferences
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.
