Incomplete cleaning of associated data
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?
When the container service is completely deleted, the associated /etc/dokploy/applications deployment folder should be deleted as well.
Describe the solution you'd like
The associated folder data should be cleaned up.
Describe alternatives you've considered
no
Additional context
No response
Will you send a PR to implement it?
Yes
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
Start by locating the container service deletion handler and references to /etc/dokploy/applications. Verify the cleanup path when a container service is completely deleted, and consider the work done when the associated deployment folder is removed without affecting other data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, typescript
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100