# What command/process builds the included assets?

**URL:** <https://meta.discourse.org/t/what-command-process-builds-the-included-assets/242335>\
**Category:** Self-hosting\
**Tags:** unsupported-install, docker\
**Created:** [October 19, 2022, 10:04am UTC](https://meta.discourse.org/t/what-command-process-builds-the-included-assets/242335 "2022-10-19T10:04:45Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [October 19, 2022, 4:46pm UTC](https://meta.discourse.org/t/what-command-process-builds-the-included-assets/242335/6 "2022-10-19T16:46:00Z")

</div>

> [@david](#):
>
> Compiled-on-demand assets (e.g. stylesheets, theme-javascripts, svg-sprites) are not uploaded to S3. They are fetched directly from the application (or via the CDN\_URL, if configured).

I see; that helps explain why some stuff is served by the application. If there are multiple containers running (say, behind a load balancer), each of them will generate those on demand.

---

_[View the full topic](https://meta.discourse.org/t/what-command-process-builds-the-included-assets/242335)._