You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exported files are stored on the server (for now a zipfile each) – those should not stay there indefinitely, we should introduce expiry and a clean up job.
The expiry should also be communicated to the user.
Also, intermediate files in .converting should be cleaned up periodically
The question is where to store the expiry timestamps (they need to survive backend restarts). Redis again? Or directly on disk in filenames/additional files?
We could also use modified timestamps from the filesystem.
The text was updated successfully, but these errors were encountered:
Exported files are stored on the server (for now a zipfile each) – those should not stay there indefinitely, we should introduce expiry and a clean up job.
The expiry should also be communicated to the user.
Also, intermediate files in
.converting
should be cleaned up periodicallyThe question is where to store the expiry timestamps (they need to survive backend restarts). Redis again? Or directly on disk in filenames/additional files?
We could also use modified timestamps from the filesystem.
The text was updated successfully, but these errors were encountered: