| Aug | SEP | Oct |
| 11 | ||
| 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
$ npm install --save-dev webpack-dev-server $ npm install --save-dev webpack-config-githubwebpack.config.js
module.exports = require('webpack-config-github')src/index.js
document.body.innerHTML = '<h1>Hello, World!</h1>'Start development server
$ webpack-dev-server --open
my-app
├── package.json
├── Dockerfile
├── config
│ └── nginx.conf
├── .graphqlconfig
├── data
│ └── schema.graphql
├── node_modules
├── public
│ └── favicon.ico
│ └── robots.txt
└── src
└── index.js
└── components
└── App.js
└── Layout.js
└── Sidebar.js
Dockerfile.
config/nginx.conf
This example nginx.conf aligns the static serving with the webpack-dev-server.
.graphqlconfig
Specifies the location of the GraphQL schema and target endpoints.
Here is an example configuration file when targeting the GitHub GraphQL API.
{
"schemaPath": "data/schema.graphql",
"extensions": {
"endpoints": {
"production": {
"url": "https://api.github.com/graphql",
"headers": {
"Authorization": "Bearer ${env:API_TOKEN}"
}
}
}
}
}
See the GraphQL Configuration Format for
more information.
data/schema.graphql
When using Relay, a copy of the GraphQL schema should be checked in at this location. Checking the schema in ensures
linting and build tools can be consistently ran offline and in CI.
public/
The public/ directory contains static assets that will be exposed as is. This is useful for well known static assets
that need to be served at a specific root path like favicon.ico and robots.txt.
src/
Contains source JavaScript, CSS and other assets that will be compiled via webpack.
src/index.js
Is the main entry point for bootstrapping the application.
When using React, this file should render the root application component.
import React from 'react' import ReactDOM from 'react-dom' import App from './components/App' ReactDOM.render(<App />, document.getElementById('root'))