On Thursday, February 20, 2020 at 8:52:31 AM UTC-8, Stephen J. Butler wrote: > > Django only serves up static files itself when run using runserver. This > is meant for development and not production use. When you run it through > gunicorn the Django framework won't serve up static files. That's why you > connections to :8000 (gunicorn directly, bypassing nginx) don't work right. > > For running in production/gunicorn you need to run "collectstatic" after > changes, and connect to nginx (probably port 80/443) so that the > "location/alias" block works as intended and you get your static files. > > >> I understand what you're saying but I don't understand specifically what >> it is that I'm doing wrong. Should I not start Gunicorn with ":8000"? Do >> I need to modify my Nginx configuration file? I don't quite see how all of >> these pieces work together and which piece (or pieces) are wrong. Thanks. > >
-- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f1cd8e78-17ae-47c0-91e8-732a52ccccc9%40googlegroups.com.
