Thibault RICHARD

> update that section: warming the cache (≠ build) is less important than before Well `cache:warmup` is in fact mostly creating files in buildDir like the compiled container (the name...

> OK the 1st section (cache:warmup) isn't obsolete, but it will now be a required step, right? Yes, using buildDir would make this required > OK and for the second...

Caching with the filesystem adapter (`cache.adapter.filesystem`) will write cache to the cacheDir which is writable (located in `/tmp`). But this is already the case for the current implementation. And IMHO,...

> 3. some files are generated on warmup in the cacheDir so they would be ignored I noticed the cache warmup does generate router files (url_matching_routes.php and url_generating_routes.php) in the...

@shouze well this is the approach taken by this bridge at the moment. The var/cache directory is deployed warm then its content is copied/symlinked to /tmp/cache at runtime during the...

@shouze not sure its linked to your issue but while trying this approach myself I stumbled upon a similar issue and fixed it by adding `var/build/prod/**` to my `package.include` and...

Already thought about adding a Flex recipe in the original issue > I'm also wondering how/if this repository could benefit from Flex or being a bundle to automate even more...

Hi everyone ! I've been thinking over and over again about Symfony cache on lambda and how to make it work with the ephemeral filesystems. This seems like an deep...

The `.legacy` extension lead me to think the cache you uploaded to lambda is not "fresh" and so Symfony tries to generate a new one. Did you include your `var/cache/prod`...

oh interesting, thanks for getting back to us with what you found ! Indeed the bridge is intended for production use and assumes you're running a `APP_ENV=prod` and `APP_DEBUG=false` because...