Skip to content
This repository was archived by the owner on Jul 12, 2026. It is now read-only.

Adding Docker Compose Manager - #19

Closed
fernandoescolar wants to merge 7 commits into
chabad360:mainfrom
fernandoescolar:main
Closed

fernandoescolar wants to merge 7 commits into
chabad360:mainfrom
fernandoescolar:main

Conversation

@fernandoescolar

Copy link
Copy Markdown

This PR delivers a broad Compose UX and architecture upgrade in cockpit-docker, moving from a dense, hard-to-scan interface to a clearer, progressive workflow while also improving reliability, security handling, and maintainability.

Main Improvements

  • Container name normalization was moved to the API layer so names starting with "/" are cleaned once at source and remain consistent across the UI.
  • A full Compose management flow was added, including stack discovery, lifecycle actions, service operations, file editing, diff, and history.
  • Sensitive runtime environment variables for Compose actions are now handled through encrypted storage on disk (per stack),
  • The previous monolithic Compose page was refactored into smaller components plus a dedicated state/actions hook for easier maintenance and future extension.
  • Compose-related modules were reorganized under a compose-focused structure for cleaner ownership and clearer boundaries.

@chabad360

Copy link
Copy Markdown
Owner

Hey, thanks for this. I'll be upfront, I'm not going to merge this for two reasons:

  1. This is very explicitly meant to be a fork of cockpit-podman that was basically Ctrl-R cockpit with docker, so this would be a very large departure from that.
  2. I'm not maintaining this anymore, so I can't -in good conscience- merge this (tbh, I should mark this archived).

@chabad360 chabad360 closed this Jul 12, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants