2 Commits

Include renames

Author	SHA1	Message	Date
menzeljandClaude Fable 5	1609b8bcc3	Phase 25: templates as stack folders (0.31.0) ... Templates are now stack-shaped folders (compose.yaml + .env.example + template.json) instead of DB rows + manifest.json + {{VAR}} rendering. Pull copies the folder into a new stack; custom templates persist under DATA_DIR/templates. Adds POST /api/templates/from-stack and a one-time startup migration for pre-0.31 DB templates (drops the template table). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-06-12 07:29:54 +00:00
menzeljandClaude Opus 4.8	22d9864436	Phase 3: env masking, image updates, port conflicts, resources, templates (0.3.0) ... Backend: - update_service: registry manifest digest check (Docker Hub/ghcr/lscr/private v2 token auth) vs local RepoDigests; in-memory cache + background loop - port_service: parse compose ports, check /proc/net/tcp[6] + docker bindings - template_service + bundled templates (jellyfin/vaultwarden/uptime-kuma/ paperless-ngx/gitea) with {{VAR}} placeholders; custom templates in DB - compose_edit set_resources (deploy.resources.limits/reservations) - routers: images, ports, templates, editor/set-resources - Template model; background update task wired into lifespan Frontend: - EnvEditor (table + raw, sensitive masking, quick-insert) - Images page + UpdateBadge + dashboard 'updates available' banner - PortConflictDialog pre-deploy check on Deploy - ResourcePanel (CPU/RAM sliders) as editor Limits tab - Templates page with per-variable instantiate form Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-07 16:49:38 +00:00