From 7dee32c6320b98d56a7fa72f5d252d6ae7068f6e Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Fri, 14 Apr 2023 15:07:14 +0100
Subject: issues: Indicate incompatibility between state and web server.

* issues/incompatibility-between-state-and-web-server.gmi: New issue.
---
 issues/incompatibility-between-state-and-web-server.gmi | 11 +++++++++++
 1 file changed, 11 insertions(+)
 create mode 100644 issues/incompatibility-between-state-and-web-server.gmi

(limited to 'issues')

diff --git a/issues/incompatibility-between-state-and-web-server.gmi b/issues/incompatibility-between-state-and-web-server.gmi
new file mode 100644
index 0000000..2b991bf
--- /dev/null
+++ b/issues/incompatibility-between-state-and-web-server.gmi
@@ -0,0 +1,11 @@
+# Incompatibility between state and web server
+
+* tags: bug, enhancement
+
+During upgrades, the new version of the tissue web server may be incompatible with the tissue state (specifically the xapian index—the document data, the slots used, etc.) built by an older version of tissue pull. At present, this will cause tissue to crash.
+
+At the very least, tissue should produce an error message or warning so that the user can manually run a tissue pull and rebuild the state. This error message should probably appear when the tissue web server is started so that the user can take action before visitors go to a web page and find it crashed.
+
+More ideally, it would be nice to transparently and automatically rebuild the state without the user having to know anything. But, this may be much harder to do and add more complexity. We need to decide if this additional complexity is worth it.
+
+To implement either of these solutions, tissue must record some kind of version number in the xapian index so that it can know what version of tissue was used to build a specific index.
-- 
cgit v1.2.3