Update to PoC||GTFO rsync mirror sync script
So I made some changes to the script we use to update the mirror:
- It’s now cross-platform! Yay! (Sorry, Windows pythoners; I get lazy and tend to just use var1/var2 paths instead of os.path.join’s. That’s been fixed. No idea if it actually works on Windows, though.)
- I changed to the alchemistowl mirror as it was the only one that didn’t seem to lag ages behind on getting 0×15 out (It was released today! Yay!)
- It now uses a sqlite3 backend. I know, I know, but it means the data about issues is available to other future applications.
And I guess I never explained what each of the files were. Here’s a sexy table.
|FILE||WHAT IT DO|
|index.html||The index.html upstream|
|ISSUES||An “Index” of current issues in a format easily visually parsed, with curl, etc.|
|md5sums.bsd||The MD5 hash checksums of the issues in BSD’s native format|
|md5sums.gnu||The MD5 hash checksums of the issues in GNU’s native format|
|pocogtfo.sqlite3||The SQLite3 DB of issues|
|pocorgtfo##.pdf||The actual issues|
|README||Some notes from me (this mirror’s maintainer)|
|sha256sums.bsd||The SHA256 hash checksums of the issues in BSD’s native format|
|sha256sums.gnu||The SHA256 hash checksums of the issues in GNU’s native format|
|update.py||The script that parses the upstream mirror and downloads any new/missing issues|
So yes, you can start from a totally empty directory and run update.py and it will generate/download all the above for you (except for the README file – you have to write that yourself!).
If you want to mirror from us, however, please just use rsync – it’ll be easier on both our network connections. :) (DID YOU KNOW THAT we’re the only PoC||GTFO rsync mirror?? It’s true!)