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

Appearance settings

Commit 5bb90ba

Browse filesBrowse files
committed
minor #15539 Update advanced-config.rst (iampedropiedade)
This PR was submitted for the 5.3 branch but it was merged into the 4.4 branch instead. Discussion ---------- Update advanced-config.rst I think the documentation is missing the manifest definition step. Commits ------- 32e6088 Update advanced-config.rst
2 parents 1a75f29 + 32e6088 commit 5bb90ba
Copy full SHA for 5bb90ba

File tree

Expand file treeCollapse file tree

1 file changed

+15
-0
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+15
-0
lines changed

‎frontend/encore/advanced-config.rst

Copy file name to clipboardExpand all lines: frontend/encore/advanced-config.rst
+15Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -122,6 +122,21 @@ Next, define the output directories of each build:
122122
firstConfig: '%kernel.project_dir%/public/first_build'
123123
secondConfig: '%kernel.project_dir%/public/second_build'
124124
125+
126+
Also define the asset manifests for each build:
127+
128+
.. code-block:: yaml
129+
130+
# config/packages/assets.yaml
131+
framework:
132+
assets:
133+
packages:
134+
first_build:
135+
json_manifest_path: '%kernel.project_dir%/public/first_build/manifest.json'
136+
second_build:
137+
json_manifest_path: '%kernel.project_dir%/public/second_build/manifest.json'
138+
139+
125140
Finally, use the third optional parameter of the ``encore_entry_*_tags()``
126141
functions to specify which build to use:
127142

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.