#Evolution of cache volumes
1 messages · Page 1 of 1 (latest)
The other day I was developing a module for a real-world use case (exporting data from our discord server), and struggled with cache volumes
I needed something like cache volumes, but struggled to use them in a useful way because their lifecycle is so different
I wonder if we could decouple the features of a cache volume, to get some parts without the others?
Specifically could we have a directory with regular mounting behavior, incorporated in the layers with digest etc, but with persistent changes somehow?
maybe an evolution of the new env lifecycle @drowsy juniper ?
my use case was reusing a download directory across several discord data exports