Okay, I'v'e been all over the docs, both Dokku and Heroku's, and I get that I can have multiple buildpacks for a given app:

• heroku/nodejs (build all the static assets, compile the typescript down to JS, etc.)
• heroku-community/nginx (host the built files behind a simple nginx instance.)

This setup makes sense for Heroku, where you still ultimately need SOME dyno to handle the plain http requests. But Dokku ships with an nginx proxy already and it seems silly to run TWO nginx proxies (one for the "assets" app, and one for dokku-centralized access across related apps) for a stack of plain HTML/CSS/JS files.

So is there a mechanism I'm missing for a Dokku app to JUST build the assets, then shut down and leave those assets to be directly hosted by the central dokku proxy? With no web service to keep running? Obviously docker volumes are involved so there isn't necessarily a centralized filesystem across everything. Just curious if there's something I'm overlooking, really. Thanks!