summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFrederick Muriuki Muriithi2025-03-12 09:39:26 -0500
committerFrederick Muriuki Muriithi2025-03-12 09:39:26 -0500
commit0bf1a99179dfe2c2e4fb6564c3d5d05389ec5943 (patch)
treee3dd4d30ffd3724151482fc5a95af69cd7b9dc9b
parent923b5bd2cda3f6cb9395a04cfbc3ab119f9651ab (diff)
downloadgn-gemtext-0bf1a99179dfe2c2e4fb6564c3d5d05389ec5943.tar.gz
Replace Redis with SQLite: New issue.
-rw-r--r--issues/gn-uploader/replace-redis-with-sqlite3.gmi17
1 files changed, 17 insertions, 0 deletions
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.