I have an app that periodically downloads a ~1GB zip file, then unzips it to a CSV that is 10x bigger (~10GB), then does some processing with it. After that, the files (both zip and csv) are not needed and can be deleted.
We used to run this on Heroku where we did the processing in /tmp. I attempted to do the same now on fly.io and we’re running into disk space issues.
From reading various threads (e.g. Tmp storage and small volumes), I gather that /tmp is part of the root volume, which is limited to 8GB. Is that correct?
Is there a way to extend that volume?
I found documentation for how to create a volume, allow it to grow, and associate it with an app:
But I haven’t found a specific way to extend the root volume. Is that possible?
If not, then I guess I’ll proceed with creating a new volume. Ideally I’d want it to operate like /tmp, meaning that everything is throwaway and gets cleaned up whenever we deploy. Is there a standard configuration for that kind of behavior?