Periodic Staging Directory Cleanup
A tool or AYON service to delete staging directories after a set period, such as a 90-day timeout.
It can serve as an alternative to automatic deletions managed by cleanup plugins.
This is idea was mentioned in some old discussion on discord.
Just found it while I was cleaning up my notes.
Log in to comment and vote
Comments3
Roy Nieterau
I want to clarify that the worth here is really in tracking intermediate data in a way that:
It may survive the current publish (e.g. “intermediate work renders not getting deleted immediately”) but getting marked somewhere, e.g. in database that at site X file Y is marked intermediate at a specific datetime.
Then an automated processor or “action” can be run at a later date to e.g. say “Delete all intermediate files before date XYZ.” with potential filters like “for project B” or for entities “A, B and C” only.
By having a registry of ‘marked staging files’ we can build the surrounding tools like this - and also e.g. if we have an ‘archiving tool’ easily remove the staging files on archiving or just ignore them in the archiving process, etc.
This all would make it doable to have automated clean-ups for data in a few months time where you’re quite confident the intermediate files may not be important to you anymore.
Mustafa Zaky Jafar
I think such data should be saved in launcher cache per user.
Publish plugins can add to this cache and launcher can have some cleaning up process on start.
Alternatively, this cleaning up process can target the staging directires defined in the anatomy templates and delete any files that existed for some time.
Roy Nieterau
I think such a local cache is too short-lived and short-sighted actually. As an admin I may want to be in control of deleting these “old” stale files at a given time - even the files from other users and departments.