itsgoingd / itsgoingd/clockwork
Insane stroage folder size (5gb)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 6k
- Forks
- 333
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
I kept running out of space, so I happened to be hunting around for ways to clear up my macbook, then I discovered this haha
There were something like 90k files. I haven't actually used clockwork in a few months, but clearly it's collecting a lot of data behind the scenes.
Nothing else I'm using came close - maybe it should/could perodically clean itself? Hook into migrate:fresh or some other hook that other packages must be using?
Feel free to close if this is just clutter - I just figured maybe no one is aware of it and there might be an easy fix.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is named. Start by reproducing the storage growth and tracing where Clockwork persists its data, then review the suggested periodic cleanup or migrate:fresh hook. Done means the retention behavior is defined and the storage no longer grows indefinitely during normal use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- laravel, php
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100