5 Commits

Include renames

Author	SHA1	Message	Date
Sami	7ef99ec42b	fix(dns): correct provider-dns.js require path after dns-providers/ move to src/dns/	2026-06-29 00:48:50 -07:00
Hermes	7bc2a207f3	DC-005: Fix all 138 broken test paths after src/ refactor ... After the DC-005 module reorganization (41 files moved into src/ subdirs), 138 test suites failed because the refactor script's path-rewrite logic missed three categories: 1. Files inside src/ doing 'require("./src/...")' — should be 'require("../...")' 2. Files in src/X/Y/ doing 'require("../../../src/...")' — should be 'require("../../...")' 3. Test files in __tests__/ with leftover 'require("../../../src/...")' paths Root cause: the original refactor script ran before all files were moved, so it computed relative paths against stale filesystem state. Result: - 30/30 test suites pass - 879/879 tests pass (was: 18/30 suites, 614/687 tests) Also fixed: - routes/apps/restore.js: wrong responses import path - routes/*/*.js: '../../src/utilities/X' → '../src/utilities/X' (depth 2 routes)	2026-06-13 12:16:56 -07:00
Hermes	6025f68b22	DC-004: Fix all 19 ESLint warnings (zero remaining) ... Removed unused imports (path, validateStartupConfig, platformPaths), renamed unused destructures (_timeout, _logEntry), replaced nested ternaries with lookup tables, added eslint-disable comments on require-await functions that are intentionally async for API stability, and extracted helper functions to reduce max-depth and complexity in app.js, dns.js, provider-dns.js, and site.js. All 879 tests pass.	2026-06-13 11:53:18 -07:00
Hermes	2d394d882d	Standardize response shapes and fix dead fetchT timeout keys ... Three small cleanups for v1.14.0: 1. /caddy/cas now uses standard success envelope Was: { status: 'success', data: { cas: caList } } Now: { success: true, cas: caList } Updated frontend service-infrastructure.js to match. 2. /api/health/ca now uses standard envelope + meaningful HTTP codes Was: { status, message, daysUntilExpiration } with 200 on every error Now: { success, caStatus, message|error, daysUntilExpiration } with 200 / 404 / 500 as appropriate caStatus field preserves the original 'healthy'/'warning'/'critical'/'error' semantic so any future consumer of the CA-health state still has it. Tests updated to match. 3. Dead timeout: keys in fetchT opts are now a warning, not a silent strip src/utils/http.js:41 used to do without telling anyone. Callers that wrote fetchT(url, { timeout: 5000 }) got the default 5s timeout with no indication that their explicit value was ignored. Now it logs a warning naming the call site, then strips the key. Fixed 4 call sites that had stale timeout: keys: - src/context/caddy.js - src/context/dns.js - src/context/provider-dns.js - routes/dns.js (2 places)	2026-06-10 21:52:33 -07:00
Hermes	2de72ed506	feat: DNS provider abstraction — Technitium, Cloudflare, RFC 2136, Manual ... - dns-providers/: adapter base class + registry with auto-discovery - technitium.js: wraps existing Technitium API calls into adapter interface - cloudflare.js: Cloudflare API v4 adapter (zones, records, credentials) - rfc2136.js: RFC 2136 dynamic DNS via nsupdate (BIND, PowerDNS, etc.) - manual.js: no-op adapter for external DNS management with instructions - provider-dns.js: provider-aware DNS context, resolves active adapter from config - Universal helper methods: universalCreateRecord/Delete/ResolveRecord - All 7 route files updated to use universal methods instead of raw dns.call() - Setup wizard: provider dropdown (Technitium, Cloudflare, RFC 2136, Manual) - DNS template selector: added Cloudflare and External/Manual options - Config schema: validates dns.provider field - Capability gating on Technitium-specific endpoints (logs, restart, update) - Backward compatible: no provider set = auto-detect (technitium if dns.ip exists)	2026-06-10 15:06:41 -07:00