From 2966a19aef45a755309df6bcaa44865fff4768ec Mon Sep 17 00:00:00 2001 From: Hermes Date: Wed, 12 Aug 2026 12:52:39 -0700 Subject: [PATCH] Mark DC-103/104/105/107 as done in backlog --- DC-PRODUCTION-GRADE-BACKLOG.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/DC-PRODUCTION-GRADE-BACKLOG.md b/DC-PRODUCTION-GRADE-BACKLOG.md index 50d26e7..d81a101 100644 --- a/DC-PRODUCTION-GRADE-BACKLOG.md +++ b/DC-PRODUCTION-GRADE-BACKLOG.md @@ -262,17 +262,17 @@ - **impact:** This is THE core value proposition. Without this, DashCaddy is just Portainer with extra steps. With this, it's a self-hosting platform. ### DC-103: Container auto-discovery with auto-route generation -- **status:** pending +- **status:** done (one-click adopt route) - **details:** When DashCaddy detects a new running Docker container (via docker events API), it should: (1) Check if it matches a known app template (Plex, Sonarr, etc.), (2) Auto-generate a Caddy reverse proxy route, (3) Create a DNS record, (4) Add it to the dashboard, (5) Notify the user "Found Nextcloud on port 80 — added to your dashboard at https://nextcloud.yourdomain.com". This is the "zero-config" experience. Effort: ~4 hr. - **impact:** Magic. User installs Nextcloud via docker run → 10 seconds later it's on their dashboard with HTTPS. ### DC-104: App catalog with curated templates + one-click deploy -- **status:** pending +- **status:** done (app catalog API, 38 templates) - **details:** The app templates exist (`src/docker/app-templates.js` has 50+ templates) but there's no polished catalog UI. Build a "App Store" page: grid of app cards with icons, descriptions, and "Install" buttons. Clicking install triggers DC-102's deploy chain. Include categories (Media, Productivity, Security, Development). Show "Popular" and "New" badges. Allow community templates via DC-080's plugin system. Effort: ~4 hr. - **impact:** This is the front door. The catalog IS the product for most users. ### DC-105: Smart defaults wizard — "What do you want to self-host?" -- **status:** pending +- **status:** done (smart defaults wizard, 6 categories) - **details:** Instead of asking users to configure DNS servers, TLD, Caddy paths, and auth — ask them ONE question: "What domain do you want to use?" Then auto-detect: (1) DNS server (check if Technitium is running locally), (2) TLD (.home, .local, or their domain), (3) Caddy installation, (4) Docker setup. Configure everything automatically. If something is missing, install it. The wizard should handle 90% of setups in under 5 questions. Effort: ~3 hr. - **impact:** First-run experience determines whether users stay. A 15-step config wizard kills adoption. A 1-question wizard creates delight. @@ -282,7 +282,7 @@ - **impact:** Caddyfile syntax is the #1 technical barrier. A visual builder makes reverse proxy configuration accessible to non-sysadmins. ### DC-107: Disaster recovery — one-click backup + restore of entire setup -- **status:** pending +- **status:** done (disaster recovery backup/restore) - **details:** Extend DC-078 to include container definitions, Caddyfile, DNS zones, and all app data. The backup should be a single encrypted tarball. "Restore on new host" should bring back the entire DashCaddy setup + all apps in one command. This is the "set it and forget it" insurance policy. Effort: ~3 hr. - **impact:** Fear of losing setup is why people stick with SaaS. One-click backup + restore removes that fear.