[QoL] Turn off docker containers and start them manually as well
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
The inability to turn off a specific docker container in a compose service for temporary or prolonged maintenance to that specific docker container.
Describe the solution you'd like
Potentially adding in a separate button to stop/start the container so it can be taken offline as needed.
Describe alternatives you've considered
Opening a terminal and shutting down the container or similar actions by 3rd party software.
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the compose-service container controls and the existing deployment UI or API actions; done means a user can independently stop and start one container without taking down the rest of the service.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100