Exactly, instead of the path to localhost:8080 or localhost:8000 it would call for django:8000 or vuejs:8080, being those the container names, important also to share volumes, default network could be used, and also container up link order is important.
I will update this article and write it up, just been hard to find the time.
Yes, I am writing the follow up for development in docker first as it will change deployment… yes, nginx is the right way to do it in production… with docker you won’t have the problems that you mention… and it will remove the need for two terminals in development also… and nginx can also be put in a container and wrapped up in docker-compose for production… i am also using redis for cache…
Could be a few things… You can check your ALLOWED_HOSTS configuration on django… but actually looks like the VueJS Dev Server is not allowing cross-origin requests, do you have the line:
on your vue.config.js file?
What is the GET 403 code description on the the server?
It will bundle in one js file for each “route” or “page”, but that would be the case if it were just a Vue application also. And you really just use the real time bundle rendering for development, in production you should build and minimize your vue app. So that webpack won´t need to be rendering a bundle in realtime. VueJs is just a frontend…