Skip to content

[Frontend] Added some comments about asset versioning and deployment #11897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 12, 2019
Merged

[Frontend] Added some comments about asset versioning and deployment #11897

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions frontend/encore/versioning.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
----------

Expand Down