MyST theme currently has two modes for rendering CDN content:
- Via CDN URLs that the frontend knows nothing about.
- Via statically served
/build/ content that is copied into static build public tree.
(1) requires a publicly visible CDN for theme users. (2) requires a post-rendering step to populate public.
In #595 (comment) I proposed actually adding routes to handle the /build/ path in the theme. This would immediately make running MyST Theme behind a proxy slightly easier, as one would only need to proxy one server, not two (plus specifying the CDN).
However, with static builds driven by the theme itself (see #925), there are some advantages to simply defining a /build/* → CDN/* route that we can then use the pre-rendering mechanism for.
MyST theme currently has two modes for rendering CDN content:
/build/content that is copied into static build public tree.(1) requires a publicly visible CDN for theme users. (2) requires a post-rendering step to populate public.
In #595 (comment) I proposed actually adding routes to handle the
/build/path in the theme. This would immediately make running MyST Theme behind a proxy slightly easier, as one would only need to proxy one server, not two (plus specifying the CDN).However, with static builds driven by the theme itself (see #925), there are some advantages to simply defining a
/build/* → CDN/*route that we can then use the pre-rendering mechanism for.