Best Practices for Serving Custom Fonts & Assets in Morpheus HA Environments

[JosephChukwudi]

Hi everyone — I’m running a 3-node Morpheus HA setup, with NFS-mounted storage across all nodes. I'm working on customizing the UI by changing the default font and adding branded assets.

To make the fonts and images available, I:

• Configured an S3 bucket and linked it to the Archive tab in Morpheus

• Uploaded all custom fonts and images there

• Generated public/private URLs through Morpheus for each asset

The problem is — these URLs behave like direct download links. Every time the browser references these assets (e.g. inside override.css for font-face or background image rules), it initiates a file download instead of rendering the assets like static content.

This leads to:

• Delayed rendering on every browser reload

• Fonts and images feeling non-persistent or non-cached

• A sub-optimal whitelabel experience

My Questions:

1. Is there a way to serve static assets directly from the Morpheus nodes, instead of relying on download-style links via the Archive tab?

2. Can I safely place fonts and images in a specific directory on the nodes, like /var/opt/morpheus/custom-ui/fonts/, and use that path in override.css?

3. In an HA setup with NFS-backed storage, how can I ensure these assets are served consistently across all nodes and exposed via /custom-ui/ URL paths without access issues (e.g. 403 errors)?

Any advice on best practices for font delivery, caching, or verified patterns from your own environments would be greatly appreciated.

Thanks!