ProjectTech4DevAI / ProjectTech4DevAI/kaapi-backend
Cleanup: Automate TTS/STT folder deletion
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 10
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem?
S3 cleanup is currently separate from DB cleanup. TTS/STT folders require manual deletion as only a few projects generate real traffic, leading to potential clutter.
Describe the solution you'd like
- Identify TTS/STT voice-note storage folders eligible for deletion.
- Delete folders recursively (manual console deletion is acceptable).
- Ensure this process is separate from the DB cron/migration path.
- Verify that evaluation processes do not reuse the same folder path prior to deletion.
Original issue
Context
S3 cleanup stays separate from DB cleanup. TTS/STT folders can be deleted recursively, possibly manually via console since only ~10–12 projects have real traffic.
Acceptance criteria
- Identify TTS/STT voice-note storage folders eligible for deletion.
- Delete recursively (manual console deletion acceptable given low project count).
- Keep this work out of the DB cron/migration path.
- Confirm evals does not reuse the same folder path before deletion.
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 existing S3 cleanup and DB cron or migration paths, then inspect TTS/STT voice-note folder naming and evaluation storage usage. Identify eligible folders, verify that evals will not reuse them, and keep deletion separate from DB cleanup; the acceptance criteria allow recursive deletion through the console.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100