<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=521347) </details> <!--IssueSummary end--> This is a follow-up from https://gitlab.com/gitlab-org/gitlab/-/merge_requests/182705#note_2367820021. Direct Transfer currently uses `Dir.mktmpdir` to create temporary folders for downloading and extracting tarballs for Direct Transfer. The actual location here is usually `/tmp`, but this can be configured using the `$TMPDIR` environment variable. However, this would change the behaviour of the entire instance, so may trigger unexpected behaviour. We could allow instance admins to configure the location used for extracting the export tarballs. This could be useful when trying to extract larger files on instances where the `/tmp` directory is mounted to a smaller volume, or using [`tmpfs`](https://en.wikipedia.org/wiki/Tmpfs), which has a default size of half of the system memory.