Specify additional directories to cache after build
Anurag Goel
Render already caches well known paths for all native language environments. No other directories are cached.
Users can also copy and restore extra data they'd like to cache to the directory specified by the
$XDG_CACHE_HOME
environment variable.But there are other custom directories or files that would benefit from automatic caching without needing to copy and restore files from
$XDG_CACHE_HOME
. For example, a .node_modules
directory in a non-root directory.Enable specification of additional cache directories relative to the root of the project.
Log In
A
Ali Kamalizade
I'm actually interested in the opposite: I'd like to control what is being cached. In a Node.js project we use
npm ci
which means we are discarding the node_modules
folder anyway. Would this be covered by this feature request as well? I'm asking since downloading the cache for deployment takes around 2 minutes in our case.J
J Pratt
This would be great for rust projects (if .cargo isn't already being cached, not sure how to test that)
m
marysonthego
I am migrating from Heroku. To keep my node server separate from the react app it is hosting, I have the server installed in the top level project directory and the app one level down. This means I have 2 node_modules dirs - one at each level - that contain very different pkgs. I'm hoping you will have a solution which allows me to npm start the server, then "cd dashboard && npm run build". Or, even better, start the server and run the dashboard in dev mode. Am I asking for too much? Thanks :)
K
Karl Horky
This would also enable things like build caching from Next.js (or Gatsby), which is already supported by a number of other providers: