Does it work?

Here's an example that breaks up the backend and frontend:https://github.com/nickjj/docker-node-example

It uses Node but the rest of the Docker bits are the same as this Django example. But it demonstrates 1 way of splitting things up into different directories if that's the path you want to take.

Yep, it works,
ah, haven't seen this one.
Will check the repo tomorrow and do check against my code.

nginx running on the host is what I do and really like it. There is a volume mount set up by default with this project to get the assets on the host (it only volume mounts the public_collected directory which are your finalized assets).

hmmm, I swapped build tool from esbuild to quasar-cli like this:

RUN if [ "${NODE_ENV}" != "development" ]; then \  ../run yarn:build:quasar; else mkdir -p /app/public; fi

function yarn:build:quasar {  # Build quasar assets, this is meant to be run from within the assets container  mkdir -p ../public/  quasar build -m spa  cp -r dist/spa/* ../public}

But the artifacts don't seem to show up on host. Any clues?
They show up fine with original esbuild method.
I'm checking on production env.

You might want to bring that over to the Quasar's issue tracker or discussion board. Not trying to dismiss you here but I have no experience with it and the esbuild build is working (along with using Webpacker before that). I don't see anything off the bat that might cause issues but I also know nothing about how Quasar works.

ok ok, I understand, appreciate your attention spent on this. I don't think it's quasar issue, I think I might be misunderstanding some things about the stack here (docker volume related). Because the quasar build files seem to be created fine.

I went through bunch of your posts and I'm learning something new on every run here. Thanks for all you do.

It sounds like you might need to configure Quasar to use the existing assets input directory and output public directory. I would first check to make sure your final collected assets end up in public_collected (bundled and md5 tagged from Django) in the Docker image without volumes in production mode, likewise the /public directory too which is where they would get built in the assets Docker stage (which is what the app Docker stage will copy in when it's ready to run a collect static in production mode).

No problem, glad you got it working in the end without a ton of changes.