You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.rst
+79Lines changed: 79 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -489,6 +489,71 @@ For instance:
489
489
Refer to the `patch catalog <#template-patch-catalog>`_ below for more details.
490
490
491
491
492
+
Hosting extra static files
493
+
~~~~~~~~~~~~~~~~~~~~~~~~~~
494
+
495
+
The MFE plugin allows other plugins to serve extra static files through the MFE service. This enables hosting custom assets (CSS, images, JavaScript, themes, etc.) directly alongside MFE applications, without rebuilding the core MFE image. Assets are exposed via a dedicated volume, so updates can be deployed dynamically via simple pushes to that volume, speeding up tests and updates without full-image builds.
496
+
497
+
To enable this functionality, set``MFE_HOST_EXTRA_FILES`` to ``true``:
498
+
499
+
.. code-block:: bash
500
+
501
+
tutor config save --setMFE_HOST_EXTRA_FILES=true
502
+
503
+
When this setting is enabled, the configured volume patches (explained below) will be applied inall environments so that extra files can be served. In development mode it will additionally expose port ``8002`` on the ``mfe`` service, allowing direct access to those files. In production deployments, port mapping isnot required since files are served through Caddy.
504
+
505
+
Then add your static files using volume patches. For local deployments, use the ``mfe-volumes`` patch:
0 commit comments