> Unfortunately, Heroku’s guide on using Django and static files has no actual details on how you should configure Django to serve static files This is of cour

> Unfortunately, Heroku’s guide on using Django and static files has no actual details on how you should configure Django to serve static files This is of course because Django should not be used for serving static files in production. It is has to be handled before it reaches the Application layer i.e. by the web server. Before Amazon S3 and CloudFront, it used to be the job of Apache or Nginx to serve static content but now that we have cloud based solutions they would be more robust. So it makes sense not to include such production deployment details from Django docs. But it is incredibly useful to have a stand-in functionality while you are in development.