From 0bf1a99179dfe2c2e4fb6564c3d5d05389ec5943 Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi
Date: Wed, 12 Mar 2025 09:39:26 -0500
Subject: Replace Redis with SQLite: New issue.

---
 issues/gn-uploader/replace-redis-with-sqlite3.gmi | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 issues/gn-uploader/replace-redis-with-sqlite3.gmi

(limited to 'issues/gn-uploader/replace-redis-with-sqlite3.gmi')

diff --git a/issues/gn-uploader/replace-redis-with-sqlite3.gmi b/issues/gn-uploader/replace-redis-with-sqlite3.gmi
new file mode 100644
index 0000000..3e5020a
--- /dev/null
+++ b/issues/gn-uploader/replace-redis-with-sqlite3.gmi
@@ -0,0 +1,17 @@
+# Replace Redis with SQL
+
+## Tags
+
+* status: open
+* priority: low
+* assigned: fredm
+* type: feature, feature-request, feature request
+* keywords: gn-uploader, uploader, redis, sqlite, sqlite3
+
+## Description
+
+We currently (as of 2024-06-27) use Redis for tracking any asynchronous jobs (e.g. QC on uploaded files).
+
+A lot of what we use redis for, we can do in one of the many SQL databases (we'll probably use SQLite3 anyway), which are more standardised, and easier to migrate data from and to. It has the added advantage that we can open multiple connections to the database, enabling the different processes to update the status and metadata of the same job consistently.
+
+Changes done here can then be migrated to the other systems, i.e. GN2, GN3, and gn-auth, as necessary.
-- 
cgit v1.2.3