Re: Is it a good practice to store all static data dynamically in database rather?

There are already servers that are very good at handling static files, such as nginx, apache, or amazon S3. Django will never be better at handling static files compared to those servers, as on production, Django will always be put behind those web servers. Putting static files on database, means

Re: Is it a good practice to store all static data dynamically in database rather?

Hello there! The images you mentioned you can store in the static folder of your Django project. This is the "default" location.Things such logo image, icons, JS and CSS files are placed in this folder, you can separete them by types. https://docs.djangoproject.com/pt-br/2.2/howto/static-files/

Is it a good practice to store all static data dynamically in database rather?

Hey! I'm making a static website (showcasing a hobby club of my college) using Django. I have used database for storing most of the content like photos, or events since they have multiple instances. Will it also be okay to save all the rest of the content which does not necessarily have more th