1π
I finally figured out the issue, I had connected my heroku app to a github repository where one of my apps folder was missing some folder and files; so if by any chance you run into any problem of this kind in the future and your build is successful please try to check if you have any missing files and also remember to check your server logs, thankyou so much -Chris for suggesting that I check my logs. Happy Coding π
0π
In your urls.py file you have mentioned media root path but actually itβs not defined in your settings.py file.
You can define it as shown below.
Base url to serve media files
MEDIA_URL = '/media/'
# Path where media is stored
MEDIA_ROOT = os.path.join(BASE_DIR, 'media/')
- [Answered ]-Variable table name in Django
- [Answered ]-Django registration opens other template
- [Answered ]-Why won't my Angular front-end pass correct $http.get parameters to Django back-end?
0π
I had this same issue after modifying my models.py and deleting previous migration files (not advisable). My database worked well locally but showed Internal Server Error (500) after deployment to Heroku.
I fixed it by simply removing the Heroku Postgres addon and attaching it back. This is because I added a new field to my models, it reflected locally but wasnβt provisioned on the Heroku Server. Note that you may lose your existing data if you use this approach.
For managing addons (attaching/removing) on Heroku, see here https://devcenter.heroku.com/articles/managing-add-ons
- [Answered ]-Django.db.utils.ProgrammingError: type "int4range" does not exist
- [Answered ]-Understanding where to put the IPN reciever function in django-paypal