-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
I have various scripts for periodic cleanup operations:
- brew-clean
- nix-clean
- clean-sstate
- etc
And other potential ones, like docker system prune and the like. Consolidate them into a wrapper structure of some sort, and integrate that with periodic cleanup operation services and launchd agents.
I'm leaning toward a clean or cleanup wrapper script which looks for scripts in a clean.d or cleanup.d folder by the script, but also git-like looks for clean-* or cleanup-* subscripts in the PATH to run. We can add commented header metadata to script files to use in service generation, if they have differing scheduling preferences, if worthwhile.
Metadata
Metadata
Assignees
Labels
No labels