CODEWITHSUNDEEP
djangodevelopment-environmentdjango-staticfilesdeploying
SilentDev
SilentDev

Reputation: 22747

Django - recommended way to serve static files without having to change too much code when deploying?

This link: https://docs.djangoproject.com/en/1.8/howto/static-files/ starts off by explaining a "grossly inefficient and probably insecure, unsuitable for production" way of serving files. It also explains how to use

 django.contrib.staticfiles.views.serve()

which is "not suitable for production use!". I don't want to have to code an entire Django project, finish it and then end up having to change a lot of code right before deploying because the current code is "grossly inefficient and probably insecure, unsuitable for production".

With that said, what's the best approach (the approach which doesn't require a lot of extra work just to move my app from development to production) to take when serving static files? I'm asking because I've never been through the process of deploying a Django app before and when deploying, I don't want to end up saying to myself "wow, I should have done it that way rather than this way".

Upvotes: 0

Views: 977

Answers (1)

Daniel Roseman
Daniel Roseman

Reputation: 599480

You don't change any code, because it's not your code that serves static files. You need to configure your web server to do it; which is fine, because you're configuring your web server anyway for deployment.

The whole point of the staticfiles app in Django is just that, that it manages files for you in development and puts them in a single place for deployment so you can point your web server at them.

Upvotes: 1

Related Questions