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?

  • Container already stopped error on ECS
  • Docker containers on AWS
  • Why can't I `docker exec` after installing the official Django docker image?
  • Connecting Docker container to corporate LDAP server through SSL
  • Windows 10 Docker Host - Display GUI application from Linux Container
  • Docker container for Laravel: PHP 7.x on CentOS 7.x
  • 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?

  • Docker can not resolve names when building images
  • How to specify docker image's DNS?
  • Jenkins getting test results from docker slave
  • Docker-plugin on Jenkins fails to Test Connection
  • Is Docker or Vagrant a solution to safely “package” a web app?
  • Unable to change the working directory inside a docker container using python script
  • 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.