Cached directories

# How it works

During most deployments, the build commands include composer install or npm install. These processes download dependencies and populate the vendor and node_modules folders. Cached directories preserve folders that can be re-used without downloading all dependencies with each deployment. The first deployment may take a few minutes, but successive deployments will be much faster.

Note that this is a setting that happens on the deploy service, not on the environment, see the deployment intro.

# Default settings

vendor
node_modules

In most cases the default setting is what you want. To disable cached directories, save an empty value.

# Purging cached directories

It can be helpful to purge the cached directories. Purging the cached directories, as the title suggests, will delete all files and folders, so next time during deployment a new cache will be created.

There is a button in the dashboard to purge the cache. Saving the cached directories setting will also purge the cache.