[1.x] Prevents running route:cache on build

[joedixon]

Running route:cache during the build step of an application can cause an issue.

Routes will be serialized when running this command using the app key set in the build envrionment (local machine, CI, etc) as the signature.

If the same key is not set in production, an error will occur when attempting to deserialize after the app is deployed.

[imrodrigoalves]

Hey @joedixon, is there any performance hit from not allowing to cache the routes anymore?

[joedixon]

Hey @imrodrigoalves our tests haven't shown any tangible performance hit, but let me know if you run into any issues.

[Spharian]

Hey @joedixon,

I'm building an application with only with the basic resource methods (index, update, store,...) in my Controllers, which is great for code simplicity/readability but I end up with a lot of controllers and routes (almost 200 routes at the moment). I've read some tests talking about 20ms performance hit per request at this number of routes and my app will require more routes in the future. I'm pretty scared about adding routes and impacting performances too much as we can't cache routes in Laravel Vapor.

Is there any solution to allow routes caching?