From 5ec95bd251e8154cff09d90921d310935c7c572a Mon Sep 17 00:00:00 2001 From: Javier Eguiluz Date: Fri, 5 Jul 2019 16:39:19 +0200 Subject: [PATCH] [Encore] Added some comments about asset versioning and deployment --- frontend/encore/versioning.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/frontend/encore/versioning.rst b/frontend/encore/versioning.rst index eb8f5558f08..79d06fabf9c 100644 --- a/frontend/encore/versioning.rst +++ b/frontend/encore/versioning.rst @@ -69,6 +69,23 @@ like normal: +Troubleshooting +--------------- + +Asset Versioning and Deployment +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +When deploying a new version of your application, versioned assets will include +a new hash, making the previous assets no longer available. This is usually not +a problem when deploying applications using a rolling update, blue/green or +symlink strategies. + +However, even when applying those techniques, there could be a lapse of time +when some publicly/privately cached response requests the previous version of +the assets. If your application can't afford to serve any broken asset, the best +solution is to use a CDN (or custom made service) that keeps all the old assets +cached for some time. + Learn more ----------