From 1d0fb32155864943dc7b6fa025b1510634b70cee Mon Sep 17 00:00:00 2001
From: Jordan Bancino <jordan@bancino.net>
Date: Fri, 12 Aug 2022 22:00:36 -0400
Subject: [PATCH] Add a run recipe.

---
 site/index.html | 7 +++++++
 tools/bin/td    | 8 ++++++++
 2 files changed, 15 insertions(+)

diff --git a/site/index.html b/site/index.html
index 07b453f..461de2f 100644
--- a/site/index.html
+++ b/site/index.html
@@ -898,6 +898,13 @@ to <code>PROG</code>.</li>
 binary, but it is primarily used for generating releases.
 </li>
 <li>
+<code>run</code>: Run a built <b>Telodendria</b> binary with the
+development configuration in <code>contrib/</code>. This recipe can
+be used for quick testing during development. It is <i>not</i> the
+recommended way to run <b>Telodendria</b> in a production environment;
+it should be used only for development.
+</li>
+<li>
 <code>clean</code>: Remove the <code>build/</code> directory, which
 effectively cleans the source tree. Note that <code>build</code> does
 not place anything outside of <code>build/</code>, so this is
diff --git a/tools/bin/td b/tools/bin/td
index ec4d233..5f4a960 100644
--- a/tools/bin/td
+++ b/tools/bin/td
@@ -98,6 +98,14 @@ recipe_build() {
 	fi
 }
 
+recipe_run() {
+	if [ -f "build/$PROG" ]; then
+		"build/$PROG" -c contrib/development.conf
+	else
+		echo "build/$PROG does not exist; build it first."
+	fi
+}
+
 # Remove all build files, which can be regenerated by re-running the
 # build recipe.
 recipe_clean() {