Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitb55c5cb

Browse files
committed
Reword
1 parentb8f15f5 commitb55c5cb

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

‎frontend/asset_mapper.rst

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,7 @@ Serving Assets in dev vs prod
8181
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
8282

8383
In the ``dev`` environment, the URL ``/assets/images/duck-3c16d9220694c0e56d8648f25e6035e9.png``
84-
is handled and returned by your Symfony app - but only if ``public/assets/`` is empty (see below).
84+
is handled and returned by your Symfony app.
8585

8686
For the ``prod`` environment, before deploy, you should run:
8787

@@ -95,8 +95,10 @@ See :ref:`Deployment <asset-mapper-deployment>` for more details.
9595

9696
..caution::
9797

98-
If you compiled your assets on your development machine, you need to delete them again,
99-
in order to make Symfony serve the current versions from ``assets/`` again.
98+
If you run the ``asset-map:compile`` command on your development machine,
99+
you won't see any changes made to your assets when reloading the page.
100+
To resolve this, delete the contents of the ``public/assets/`` directory.
101+
This will allow your Symfony application to serve those assets dynamically again.
100102

101103
..tip::
102104

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp