Compose stack management

[Lifailon]

Is it possible to implement bulk stack management (compose commands for starting, stopping, and viewing logs)?

I'm also wondering if it's possible to access the contents of a compose file, as is implemented in Dockge?

[theSoberSobber]

Hii @Lifailon , that should be good. I don't have any UI ideas for it though, let's discuss here so that anyone can add to our discussion, thanks!

[Lifailon]

I'd like to have common buttons to start or stop ALL containers in the system (but a warning dialog would be better for this), as well as buttons for all compose actions (start, stop, logs all stack). Dockge would be an example, but it lacks separate container management (which is what your app currently has). Regarding the layout, I'd add buttons directly below the stack list.

In an ideal world, I'd like to have access to the compose file and all related files so I can change application configurations or the Dockerfile without using a third-party interface (I've considered forking dockge for this reason) <<< I think this is the most important thing for me...

The hardest part is automatically pulling in current stack files (like in the Dockman #108, which I couldn't get to work). For this reason, it's best NOT to analyze files in child directories, as the Dockerfile, env, and configuration files are often located next to the compose file.

[theSoberSobber]

Hi @Lifailon , a bit too out of scope man ngl... we can do stop/start/restart in bulk but compose files is a bit too out of scope... what do you think?

[Lifailon]

So, if remote access is via SSH, the program already has access to files on the remote machine, and the path to the compose file can be obtained using the compose command. There are many Docker management programs, but its cross-platform stack management approach adds appeal and sets it apart from the crowd.

[theSoberSobber]

I'm wondering if it's right to have UI for this or should this be left to the user to do via the shell. I can understand start/stop/restart as quick operations. But files/docker compose etc. seems like it's too free form and making a UI for it too niche of a use case. The connection is via SSH correct, so it has access to everything, that is not a problem. I'm just trying to figure out where the line between shell and UI is.

[Lifailon]

I would base my analysis on the capabilities of the Dockge project, but it has a number of features that are missing, and in my opinion, they would be easy to implement if support had not been suspended...

Regarding the narrow direction, I don’t think so (for comparison, you can use the popularity of the Dockge or Komodo projects with dozens of other analogues). For me, compose is the basis for container management, but here it’s up to you as a developer to decide.

[theSoberSobber]

Do you think we could remove the dark/light mode toggle from app bar, add a filesystem icon there instead and use SFTP to be able to show a filesystem tree? Will that work for your requirements? I'm actually onboard with SFTP support for the app.
Start/Stop/Restart make sense for docker compose as previously mentioned.

[theSoberSobber]

By Filesystem tree, I mean a file manager like UI for the host

[theSoberSobber]

I think I might be misunderstanding this requirement, you only wanna see host's files right? Since you mentioned docker compose and env files

[theSoberSobber]

What do you think of this UI?

I am thinking this can be opt in from settings disabled by default.

[theSoberSobber]

You can try it out from here: https://github.com/theSoberSobber/Docker-Manager/actions/runs/19833350855/job/56824620773?pr=71

[Lifailon]

By Filesystem tree, I mean a file manager like UI for the host

I didn't mean a full-fledged file manager with access to all files, but a point one with partial access to files within the stack.

I think I might be misunderstanding this requirement, you only wanna see host's files right? Since you mentioned docker compose and env files

Yes ;)