Configuring static files can be a headache. I personally use Whitenoise <http://whitenoise.evans.io/en/stable/> to serve my static files. It is self contained and can be configured in Django settings after installation.
A couple of advantages of Whitenoise: 1. During development you can override the Django's static file server by putting 'whitenoise.runserver_nostatic' in Installed Apps. This way you can have the same behaviour on your local machine as you'll have on your hosted server. 2. You don't have to mess with Apache or Nginx settings. On Saturday, May 11, 2019 at 12:23:11 AM UTC-5, Rookies DJ wrote: > > I apologise, I'm a hardware engineer, I'm not very familiar with coding; > I'm only on Django for the past 5 months. (under my boss order) > > I had managed to develop and establish a Django App, and manage to upload > it to remote server *NameCheap*. There on the server, the issue is unable > to locate the static files. Even when we directed the path to static files > folder. > > This static files, infrequently work and load the static, that's how we > concluded the static error was caused by the misdirection of the path. > > But reading over the Django documentary multiple time didn't help resolve > > Please help our team had been trying resolve this issue for past 2months > -- 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 post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/c73ff13e-4328-4a08-87c3-41a9e44db6bc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
