Docker, web app static files. Best practices?

How do people tend to handle static assets in web deployment on docker?

For example, in a django app deployed in a container, do you have the app server serve up the static files from the container, or do you sync them to another server for a webserver to serve, or do you use a CDN?

  • Docker container from image created by build: is working but not working from pulled image
  • How do you copy any folder to a Docker container - while the Dockerfile is present in that folder?
  • Using docker-compose to collaborate on existing git repo Django project
  • How to program with docker? [closed]
  • Managing container dependencies on startup
  • How do you deploy a docker image into Cloud Foundry? [Bluemix]
  • If not serving from the app container, when do you push files to CDN or webserver: as part of the container build, or as a second process in the build, and how do you ensure both steps stay in sync?

  • Can a docker instance be connected to just one specific network interface?
  • Standalone kubelet persistent disk mount on Google Cloud instance
  • Cannot download Docker image from repository
  • Docker Packages: Hash Sum Mismatch
  • InsecurePlatformWarning when building Docker image
  • Gitlab run docker inside docker
  • One Solution collect form web for “Docker, web app static files. Best practices?”

    You will have to use a form of cloud storage to achieve that. S3 for example. You can also host your static files just like a CDN. Since you’re using django, consider reading this article. It explains how to host static files from within a django app.

    As a Laravel user you could use Laravels built in flysystem support.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.