2 Commits

Include renames

Author	SHA1	Message	Date
menzeljandClaude Opus 4.8	f65ec5f268	Fix: recognise a stack's own running ports on re-deploy (0.21.2) ... Port-conflict check now matches the stack's own containers via the compose project label instead of a fragile container-name prefix, so editing + deploying a running stack no longer reports false conflicts (explicit container_name or '_' name separator). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-08 16:31:52 +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