2👍
I got the answer to my question(as mentioned in my comment).I is was reviewing my stalkoverflow profile and I saw this question unanswered and unclosed.So have pasted the link as an answer once again.
0👍
Yes, because you need to tell Django where to the browser can find those files that are being served by Apache.
- [Answered ]-Django IntegrityError Duplicate entry on Foreignkey
- [Answered ]-How to get the MAC address of client
- [Answered ]-How to seamlessly maintain code of django celery in a multi node environment
- [Answered ]-Django: RecursionError when initialize a object
- [Answered ]-Get Records from Referenced Table "Minus" All The Records referenced from the Referencing Table
0👍
difference is MEDIA_ROOT indicates where you should put your static files, and MEDIA_URL is the relative path where those are being served.
in a production environement, MEDIA_* paths are (commonly, but it’s not strict to follow) used to store application related static files (css, imgs and javascripts). For user uploaded content, it’s good practice (but again, it’s not a rule) to save them inside the STATIC path, so you can move/delete/dostuff with them without compromising your app
so basically, to answer your question (didn’t see any question mark in your post, btw) MEDIA_ROOT is the absolute path on the server where the static files have to be stored.
- [Answered ]-Django six 1.10.0 no module named http_client error
- [Answered ]-Javascript post django form gives csrf error
- [Answered ]-Django forms – rendering form and redirecting
- [Answered ]-How to test a Django class-based view receives correct arguments?