Merge #1010

1010: Readme rendering - only rerender older than a date, only rerender for a crate r=carols10cents

Only rerender in a `Box<T>`, only rerender in Firefox :)

These changes add some arguments to the render-readmes script to make it easier to restart a failed run only with those readmes that have not been rendered since a particular date, and to rerender one particular crate's readmes.

By default, the render-readmes script still rerenders all readmes of all versions. But if the script is killed partway through, it doesn't need to be completely restarted-- you can grab the time that the script printed out that it started, then rerun with `--older-than thattime`, and it'll only try and render the ones it hasn't gotten to yet!

Another thing I've wanted is the ability to render one particular crate's readmes, so that I don't have to scroll through all the logs to see why a particular crate failed. So I added the `--crate` argument too.

I'd like to get this into the same deploy as #981 since that requires rerendering everything again.

@kureuil, could you look over this and see if it looks like I might be breaking anything?

Author: bors-voyager[bot]

Cargo.lock

@@ -50,6 +50,8 @@ clippy = { version = "=0.0.142", optional = true }
 chrono = "0.4.0"
 comrak = { version = "0.1.8", default-features = false }
 ammonia = "0.5.0"
+docopt = "0.8.1"
+itertools = "0.6.0"
 
 conduit = "0.8"
 conduit-conditional-get = "0.8"

Cargo.toml

@@ -0,0 +1 @@
+DROP TABLE readme_rendering;

migrations/20170820180453_readme_rendering_tracking/down.sql

@@ -0,0 +1,10 @@
+CREATE TABLE readme_rendering (
+    version_id INTEGER NOT NULL PRIMARY KEY,
+    rendered_at TIMESTAMP WITHOUT TIME ZONE
+);
+
+ALTER TABLE readme_rendering
+ADD CONSTRAINT "fk_readme_rendering_version_id"
+FOREIGN KEY (version_id)
+REFERENCES versions(id)
+ON DELETE CASCADE;