In Acquia Cloud, uploaded files are separate from the Drupal database and your code repository. Acquia Cloud deployment code creates a symbolic link to your website's
/files directory. If you use Drupal's multisite feature, Acquia Cloud creates a separate
/files directory for each
settings.php file in the
On Acquia Cloud, you manage your Drupal codebase (including Drupal core, contributed modules, and custom code) using either the Git or Subversion (SVN) version control system. Git and SVN can manage text files full of code, but is not suitable for large collections of user-uploaded objects. Acquia Cloud stores your website's
/files directories outside of your repository and manages them for you. This simplifies your workflow and makes your repository smaller and more manageable. To access your website's
/files directories, use the
An Acquia Cloud Enterprise website runs on several redundant web nodes (servers) simultaneously. If the website used local file storage on the web notes, files uploaded to one web node would not be available on another. Acquia Cloud Enterprise uses shared file systems to ensure that data your code writes to a
/files directory is accessible on all web nodes running your website's code.
When you import or create your Drupal codebase, Acquia Cloud creates symbolic links to your public file directory. Every Drupal multisite website in your account has its own
To ensure its privacy, the
/files-private directory is not symbolically linked to your website's
[docroot]. For private handling, you can either use the absolute path to
[docroot] or a relative path under
../acquia-files. For more information, see Setting the private file directory on Acquia Cloud.
Handling large files
Using very large files can cause problems on your website. For example, large images can increase page load times, causing a perceived performance issue for your website visitors. Additional problems can include having files that are too large for your website's Varnish cache, and that uploading large files through Drupal can fail due to timeouts at various levels of the stack.
If, however, you need to use very large files, consider these resources and factors:
- If you find that uploads of large files to Acquia Cloud Enterprise are timing out or otherwise failing, see Correcting broken uploads on Acquia Cloud Enterprise.
- If you need to upload files greater than 280 MB in size, contact Acquia Support to discuss having your website configured to allow larger uploads.
- Read Handling large files for best practices about image processing, file organization, and storage.
Downloading large files
Drupal websites on Acquia Cloud support downloads of files of any size. However, large downloads require a correct
Content-Length header in the HTTP response in order to succeed. For any static file, the Apache web server in the Acquia Cloud stack will provide the correct header. If the download is large (1 GB or greater) and is dynamically generated (for example, generated by a PHP script), the download is likely to fail unless a
Content-Length header is explicitly provided.
Large numbers of files
If you maintain a very large number of files on your website, it can have a substantial negative effect on performance and stability, especially if they are all contained in the same directory. We have found that over 2,500 files in any single directory in the files structure can seriously impact your server's performance and potentially its stability. If your website requires a large number of files, maintain them in multiple directories. For more information about files and performance, see Improving website performance, Proactively organizing files in subfolders, and Optimizing file paths: Organizing files in subfolders, which includes scripts for migrating files into subdirectories in your file system.
You should also consider using an external storage solution, such as Amazon S3. For more information, see Using external storage for files.
File execution restrictions
Files in your website's file storage are not executable by Acquia Cloud PHP processes.