Actions for services

[mpcref]

Describe the feature you would like to see

Right now Dozzle has stop and restart actions when the Hosts and Containers view is active. I would like to have those same actions but when the Services and Stacks view is active. This way I can easily restart or stop all instances of a service without needing to know which nodes they're running on.

Describe how you would like to see this feature implemented

In this mode stop should call docker service rm <service> and restart should call docker service update --force <service>.
I don't think it's necessary to introduce an additional env var for this: it can just respond to DOZZLE_ENABLE_ACTIONS.

Describe any alternatives you've considered

No response

[amir20]

I believe this feature request is more complicated. Once a service is removed with docker service rm, the configuration is lost and can only be created with docker stack. This would significantly change Dozzle, making it similar to https://github.com/louislam/dockge, where services and stacks can be created.

Personally, I wouldn't find this feature useful since I create all my services using the CLI.

PRs are welcomed. Will move this to discussion.

[mpcref]

Agreed. I was expecting this answer. I really only need the restart action which should be easy and I figured there should also be a stop action so both modes have the same actions. Maybe if Dozzle would show a warning dialog saying something like "The service can only be restarted by redeploying the stack! Are you sure?" Or name the action remove instead of stop to make it explicit.
But if you don't like that solution then I would be perfectly happy with just the restart action.
FYI I create my swarm services using compose.yaml.

[amir20]

I don't dislike the idea. It's worth implementing if you have the time. Personally, I'm very selective about what I work on because there are too many feature requests and not enough time.

[mpcref]

Understood. I'm not really a Go developer but I might give it a Go (pun intended) if no one else gets to it before I can find the time for it!

[amir20]

There isn't a lot of Go needed. Mostly UI work.