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.
This collection is a set of Github repository archives from two major sets: A panic grab upon the acquisition by Microsoft, and a larger, ongoing set of Pretty Much Everything.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20180612214458/https://github.com/vyakymenko/angular-seed-express
Extensible, reliable and modular starter project for Angular 6 with statically typed build AoT compilation, Express server and PM2 Daemon.
https://github.com/vyakymenko/angular…
git clone --depth 1 https://github.com/vyakymenko/angular-seed-express.git
cd angular-seed-express
# install the project dependencies
$ npm install
# watches your files and uses livereload by default
$ npm start
# api document for the app# $ npm run build.docs# dev build
$ npm run build.dev
# prod build
$ npm run build.prod
# prod build using different base path
$ npm run build.prod -- --base "/foo/bar/"# run Redis
$ src/redis-server
# stop Redis
$ src/redis-cli
$ shutdown SAVE
# run Express server (keep in touch, only after `npm run build.prod` )
$ node app.server.prod.js
# run server in daemon mode
$ pm2 start app.server.prod.js
Express Server
Express server run for prod build.
# run Express server (keep in touch, only after `npm run build.prod` )# keep in mind that prod build will be builded with prod env flag
$ node app.server.prod.js
Daemonize Server
For daemonize your server I propose to uze PM2.
# before daemonize production server `npm run build.prod`
$ pm2 start app.server.prod.js
# restart only your project
$ pm restart <id># restart all project on daemon
$ pm2 restart all
# in cluster mode ( example 4 workers )
$ pm2 start app.server.prod.js -i 4
// Configure server Port ( keep in mind that this important if you will use reverse-proxy)// Dev mode will give you only middleware.// WARNING! DEPEND ON YOUR Angular2 SEED PROJECT API CONFIG!/** * @ng2 Server Runner `Development`.*/require('./server')(9001, 'dev');
app.server.prod.js
// Configure server Port ( keep in mind that this important if you will use reverse-proxy)// Prod mode give you middleware + static.// WARNING! DEPEND ON YOUR Angular2 SEED PROJECT API CONFIG!/** * @ng2 Server Runner `Production`.*/require('./server')(9000);
Reverse Proxy NginX Config Example
server {
listen 80;
# App Web Adress Listener
server_name www.example.com example.com;
location / {
# Port where we have our daemon `pm2 start app.server.js`
proxy_pass http://example.com:9000;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
}