From d198cc0c681abc1857a5d239cac76e8cbe6c7747 Mon Sep 17 00:00:00 2001
From: Jim Lancaster <40281233+zoltan57@users.noreply.github.com>
Date: Thu, 27 Aug 2026 10:19:34 -0500
Subject: [PATCH] Separate CLoudflare from transcribe

---
 docker-compose.production.yml | 15 ---------------
 docs/roadmap_plan.md          | 26 ++++++++++++++++++++++++--
 2 files changed, 24 insertions(+), 17 deletions(-)

diff --git a/docker-compose.production.yml b/docker-compose.production.yml
index accbc1d..f64ae64 100644
--- a/docker-compose.production.yml
+++ b/docker-compose.production.yml
@@ -57,21 +57,6 @@ services:
       retries: 10
       start_period: 10s
 
-  cloudflared:
-    image: cloudflare/cloudflared:2026.8.0
-    env_file:
-      - .env.production
-    command: tunnel --no-autoupdate --protocol http2 --config /etc/cloudflared/config.yml run --token ${CLOUDFLARE_TUNNEL_TOKEN}
-    dns:
-      - 1.1.1.1
-      - 1.0.0.1
-    depends_on:
-      app:
-        condition: service_healthy
-    volumes:
-      - ./deploy/cloudflared/config.yml:/etc/cloudflared/config.yml:ro
-    restart: unless-stopped
-
 volumes:
   postgres_data:
   app_uploads:
diff --git a/docs/roadmap_plan.md b/docs/roadmap_plan.md
index 0ed5523..4fa6895 100644
--- a/docs/roadmap_plan.md
+++ b/docs/roadmap_plan.md
@@ -25,7 +25,29 @@ Detailed plan: [`v6_0_hosting_migration_plan.md`](v6_0_hosting_migration_plan.md
 - One end-to-end document -> source -> job workflow succeeds remotely.
 - Backup and restore procedure is tested.
 
-## V6.1 - Reporting Features
+## V6.1 - Testing and Refinement
+
+[*Potential app refinements:*
+* Create a **single “Maintenance Jobs” UI** backed by your existing async worker pattern, not direct shell execution from the page.
+  1. Add a `maintenance_run` table (`id`, `job_type`, `status`, `started_at`, `finished_at`, `triggered_by`, `summary`, `log_path`, `error_detail`).
+  2. In the UI, add two buttons: **Run Backup** and **Run Storage Reconciliation**; clicking creates a run row and enqueues worker execution.
+  3. Worker executes the existing scripts/commands, captures stdout/stderr to a timestamped log file, updates run status/summary.
+  4. UI shows a run history grid with live status, duration, summary, and “View Log”/“Download Log”.
+  5. Add optional schedule controls (daily/weekly) that create queued runs through the same path so manual and scheduled runs behave identically.
+
+* Consider a difference Sources for Document page
+  * Presenting the list of Document sources is not very useful.
+  * Consider presenting a thumbnail gallery instead. I think this would make it easier to select the single source file the user is looking for.
+  * This idea may be useful in other areas as well.
+
+* People detail page -> LINKED DOCUMENTS:
+  * How to handle long list of identically named documents (e.g., "Hig postcard to Zenna")? The table shown is not useful, but there isn't enough real estate in the column to add something like the document date, I don't think.
+
+* Start reviewing what the UI looks like on a smart phone. How do those cards arrange themselves on a phone?
+
+]
+
+## V6.2 - Reporting Features
 
 [ *More thoughts on additional features:*
 * *Ability to search within a document to find potential users to add to the People table.*
@@ -48,7 +70,7 @@ Objective: improve research value with person-centric outputs.
 - Narrative generation is traceable to source records and prompts.
 - Reports can be reviewed without modifying archival source data.
 
-## V6.2 - Access Control and Multi-User Readiness
+## V6.3 - Access Control and Multi-User Readiness
 
 [ *More thoughts on user accounts:*
 * *Create a generic "view only" user that does not have the rights to alter any of the data*