CodeMirror/ArchiveBox
1
0
Fork 0
mirror of synced 2024-06-28 02:50:24 +12:00
Code Issues Projects Releases Wiki Activity

Update README.md

Browse source
This commit is contained in:
Nick Sweeting 2017-05-05 07:11:43 -04:00 committed by GitHub
parent d50aec9329
commit 07bdedb875
1 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -18,9 +18,7 @@ Those numbers are from running it signle-threaded on my i5 machine with 50mbps d
```bash ```bash
brew install Caskroom/versions/google-chrome-canary brew install Caskroom/versions/google-chrome-canary
brew install wget python3 brew install wget python3
# OR on linux # OR on linux
wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add -
sudo sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list' sudo sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google-chrome.list'
apt update; apt install google-chrome-canary python3 wget apt update; apt install google-chrome-canary python3 wget
@ -62,8 +60,10 @@ Just stick this in your nginx config to properly serve the wget-archived sites:
```nginx ```nginx
location /pocket/ { location /pocket/ {
alias /var/www/pocket/; alias /var/www/pocket/;
try_files $uri $uri/ $uri.html =404; index index.html;
autoindex on;
try_files $uri $uri/ $uri.html =404;
} }
``` ```
@ -85,8 +85,8 @@ My published archive as an example: [sweeting.me/pocket](https://home.sweeting.m
## Security WARNING ## Security WARNING
Hosting other people's site content has security implications for your domain, make sure you understand Hosting other people's site content has security implications for your domain, make sure you understand
the dangers of hosting other people's CSS & JS files on your domain. It's best to put this on a domain the dangers of hosting other people's CSS & JS files [on your domain](https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy). It's best to put this on a domain
of its own to slightly mitigate CSRF attacks. of its own to slightly mitigate [CSRF attacks](https://en.wikipedia.org/wiki/Cross-site_request_forgery).
It might also be prudent to blacklist your archive in your `robots.txt` so that search engines dont index It might also be prudent to blacklist your archive in your `robots.txt` so that search engines dont index
the content on your domain. the content on your domain.