The temporary files directory in Drupal is the location on your infrastructure where Drupal core and contributed modules upload files for processing.
Acquia’s require line in your website’s settings.php file configures the location of your temporary files directory to /mnt/tmp/[sitename].[env], where [sitename] is your application name and [env] is the environment. This location is available as an environment variable.
Important considerations
- If you cannot locate temporary files, you can create a custom directory on the shared file system to store temporary files. In addition, ensure that you provide an already existing path to the
file_temp_path parameter to prevent issues with temporary files. - If you modify the value of the
file_temp_path parameter in Drupal's settings.php file, you might face issues. In such a case, ensure that you run Drupal cron to collect any old and garbage temporary files. In addition, you must set a low value for the file_temporary_max_age parameter in Drupal's settings.php file. This ensures that temporary garbage files are deleted sooner. - If you use Cloud Classic, do not set the temporary directory to
/tmp. The size of the /tmp directory is lesser than the size of the /mnt/tmp/[sitename].[env] directory. Therefore, it might run out of space in a short time, and might be purged quickly. - If you use Cloud Next, the default value of
file_temp_path parameter is /tmp.
Modules and the temporary directory
Drupal modules that write to temporary directories may require additional configuration to function properly in environments with multiple infrastructures, such as production environments for Cloud Platform Enterprise and Cloud Platform Site Factory. For more information, see Additional module issues and the following lists of modules:
More information
Temporary files
The temporary files directory in Drupal is the location on your infrastructure where Drupal core and contributed modules upload files for processing.
Acquia’s require line in your website’s settings.php file configures the location of your temporary files directory to /mnt/tmp/[sitename].[env], where [sitename] is your application name and [env] is the environment. This location is available as an environment variable.
Important considerations
- If you cannot locate temporary files, you can create a custom directory on the shared file system to store temporary files. In addition, ensure that you provide an already existing path to the
file_temp_path parameter to prevent issues with temporary files. - If you modify the value of the
file_temp_path parameter in Drupal's settings.php file, you might face issues. In such a case, ensure that you run Drupal cron to collect any old and garbage temporary files. In addition, you must set a low value for the file_temporary_max_age parameter in Drupal's settings.php file. This ensures that temporary garbage files are deleted sooner. - If you use Cloud Classic, do not set the temporary directory to
/tmp. The size of the /tmp directory is lesser than the size of the /mnt/tmp/[sitename].[env] directory. Therefore, it might run out of space in a short time, and might be purged quickly. - If you use Cloud Next, the default value of
file_temp_path parameter is /tmp.
Modules and the temporary directory
Drupal modules that write to temporary directories may require additional configuration to function properly in environments with multiple infrastructures, such as production environments for Cloud Platform Enterprise and Cloud Platform Site Factory. For more information, see Additional module issues and the following lists of modules:
More information
Cloud Platform