things-to-check - A presently-defunct web service providing troubleshooting prompts

	Commit message (Collapse)	Author	Age
*	(cargo-release) start next development iteration 0.4.2-alpha.0	Owen Jacobson	2020-06-16
\|
*	(cargo-release) version 0.4.1	Owen Jacobson	2020-06-16
\|
*	(cargo-release) start next development iteration 0.4.1-alpha.0	Owen Jacobson	2020-06-05
\|
*	(cargo-release) version 0.4.0	Owen Jacobson	2020-06-05
\|
*	(cargo-release) start next development iteration 0.3.1-alpha.0	Owen Jacobson	2020-06-04
\|
*	(cargo-release) version 0.3.0	Owen Jacobson	2020-06-04
\|
*	(cargo-release) start next development iteration 0.2.1-alpha.0	Owen Jacobson	2020-06-04
\|
*	(cargo-release) version 0.2.0	Owen Jacobson	2020-06-04
\|
*	Markdown support.	Owen Jacobson	2020-06-04
\| \| \| \| \| \| \| \|	This accomplishes two things: 1. The og cards and page title no longer contain half-baked markup. Instead, they show the markdown equivalent, which is generally pretty friendly. In other words, the page title is "Have you checked `resolv.conf`?" and not "Have you checked <code>resolve.conf</code>?" 2. Phrases can now start with terms other than "Have you checked".
*	Port things-to-check to Rust as a learning exercise.	Owen Jacobson	2020-06-03
	This is somewhat overengineered in places, but does the job and exposes broadly the same interfaces as the Python version. Builds with emk/rust.