4 Commits

Include renames

Author	SHA1	Message	Date
menzeljandClaude Opus 5	ee98d0da6d	Show live progress while pruning networks, and ask first (0.63.0) ... The network prune joins the image and volume prunes on the shared PruneJob: it runs in the background, the Networks page shows a progress bar and a toast with the outcome, and the button now asks before deleting instead of pruning on click. Docker has no -a for networks and they hold no data, so there is no option and no space figure. Candidates are stricter than docker network prune, which goes by active endpoints and so removes a stopped container's network, after which that container fails to start ("network not found"). A network any container, running or stopped, is attached to (by name or id) is kept, as are bridge/host/none, ingress/docker_gwbridge and swarm-scoped networks. Removal is per network, so one the daemon refuses does not stop the rest. - POST /api/networks/prune takes background=; without it it still waits and returns {NetworksDeleted}. GET /api/networks/prune-status is admin-only and registered before /{network_id}, which would otherwise take "prune-status" for an id. - The long-timeout test for network prune in test_docker_timeouts.py is superseded by test_network_prune.py. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-18 10:49:29 +02:00
menzeljandClaude Opus 5	f766ded528	Stop long prunes failing with a bare 500 (0.60.1) ... A prune that deletes a lot of data (image prune -a in particular) easily runs past docker-py's 60s read timeout. requests' ReadTimeout is not a DockerException, so it slipped past safe_call and the UI only showed "Request failed with status code 500". Prunes now use a client with a 540s timeout (below nginx's 600s proxy_read_timeout), and safe_call turns transport timeouts and connection errors into DockerError, so they surface as a 502 with a message. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-09-18 09:39:47 +02:00
menzeljandClaude Opus 4.8	1931500c24	Phase 11: remote UX & network attach (0.11.0) ... - Live remote-stack logs over a WebSocket proxied through the central app to the agent (/ws/agent-logs/{agent}/{stack}); agent gains a WS log endpoint. - Deploy to a remote host from the UI: host selector in the New Stack editor and template dialog; templates instantiate onto an agent via the proxy. - Network attach/detach: expandable inspect view per network with connect/disconnect + container picker; GET /{id}/containers, POST connect/disconnect. - Remove dead pages/Placeholder.tsx. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-08 07:49:20 +00:00
menzeljandClaude Opus 4.8	a4e26f880a	Phase 9: network management + stack delete in UI (0.9.0) ... - Networks: network_service (list w/ subnet/containers/in-use/owning-stack, create bridge/macvlan/ipvlan/overlay + optional subnet/gateway/internal, delete with default-network guard, prune) + routers/networks.py; real Networks page replaces the placeholder. - Fix: local stacks can now be deleted from the UI — Delete button on stack detail (with optional keep-files-on-disk) and a trash action on stack cards, via a shared ConfirmDialog. (Backend DELETE existed; no UI surfaced it.) Verified: py_compile, frontend tsc build, live network list smoke test (defaults flagged, compose nets + in-use detected); main 104 routes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2026-06-07 22:37:30 +00:00