| May | JUN | Jul |
| 11 | ||
| 2017 | 2018 | 2019 |
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
Fetching latest commit…
Cannot retrieve the latest commit at this time.
| Failed to load latest commit information. | |||
|
bin | ||
|
|
src | ||
|
|
test | ||
|
|
.eslintignore | ||
|
|
.eslintrc | ||
|
|
.gitignore | ||
|
|
.gitreview | ||
|
|
.zuul.yaml | ||
|
|
Gruntfile.js | ||
|
|
LICENSE | ||
|
|
README.md | ||
|
|
bindep.txt | ||
|
|
karma.conf.js | ||
|
|
package.json | ||
|
|
protractor-integration.conf.js | ||
|
|
protractor.conf.js | ||
|
|
tox.ini | ||
|
|
yarn.lock | ||
tox -evenv
●Source the new path containing grunt:
source .tox/venv/bin/activate
●Now you can launch the grunt tasks of storyboard-webclient, by default run
the development server with the following command: grunt serve
npm run lint: Runs a linter on the javascript sources files of the
project, this will help us keeping style consistency across our files and
can reduce the risk of bugs.
●npm run clean: Erases the temporary folders created by various grunt
tasks, such as reports, cover and dist.
●npm run build: Compile and packages our code.
●npm run serve: Development server - runs a build and sets up concurrent
watchers that will automatically lint, test, and refresh the code when a
change is detected.
●npm run test-unit: This command will create a clean build against which
our unit tests will be run. For more information, please see
karma-unit.conf.js
●npm run test-integration: This command will create a clean build against
which our functional tests will be run. For more information, please see
protractor-integration.conf.js
●npm run test-functional: This command will create a clean build against
which our functional tests will be run. For more information, please see
protractor.conf.js
npm install -g grunt.
●compile: Compiles all of our sources in the dist directory.
●package: Built code into a release package.
●serve:dist: This task performs a full build of our application,
and then runs that source in a local web server. It does no watching,
it simply hosts the files.
●serve:prod: This task is identical to 'server:dist',
with the exception that it will proxy the API requests against the production
API. USE WITH CAUTION
●© 2018 GitHub, Inc.
●Terms
●Privacy
●Security
●Status
●Help
●Contact GitHub
●API
●Training
●Shop
●Blog
●About
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.