minor #11897 [Frontend] Added some comments about asset versioning and deployment (javiereguiluz)

javiereguiluz · javiereguiluz · commit 9d042fc6b620 · 2019-07-12T10:57:29.000+02:00
This PR was merged into the 3.4 branch. Discussion ---------- [Frontend] Added some comments about asset versioning and deployment Fixes #8075. Commits ------- 5ec95bd [Encore] Added some comments about asset versioning and deployment
diff --git a/frontend/encore/versioning.rst b/frontend/encore/versioning.rst
@@ -69,6 +69,23 @@ like normal:
 
     <img src="{{ asset('build/images/logo.png') }}">
 
+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
 ----------
 
